The quickest way to check website speed is Google’s free PageSpeed Insights tool. Go to pagespeed.web.dev, paste in your web address, and within a minute or so you’ll see how your site does on mobile and desktop, plus a list of things slowing it down. For most small business WordPress sites, the usual culprits are oversized photos, too many plugins, heavy sliders or videos at the top of the page, and hosting that responds slowly.
Key takeaways
- PageSpeed Insights (pagespeed.web.dev) is free. Test your home page and your busiest page, on the Mobile tab first.
- Real visitor data (field data) matters more than the lab score. The lab score is for finding problems.
- Google’s “good” marks: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
- Speed is one thing Google looks at, not a shortcut to the top. Google says it always seeks to show the most relevant content.
How to check website speed in 2 minutes
- Go to pagespeed.web.dev.
- Paste in your full web address, for example your home page, and run the test.
- Look at the Mobile tab first, then Desktop. Google tests the two separately, and if your customers mostly find you on their phones, that’s the one that counts.
- Repeat for the page that matters most to you: your services page, your booking page, your menu.
You don’t need an account, and the test doesn’t change anything on your site.
Mobile and desktop tabs: why they differ
For the lab test, Google simulates a mid-range phone on a mobile network for the Mobile tab, and a computer on a wired connection for Desktop. So the mobile score is usually lower. That’s normal.
Field data vs lab data: which one to trust
The page shows two different sets of results.
Field data comes from real visitors using Chrome, collected through Google’s Chrome User Experience Report over the previous 28 days. It’s what people actually got on their own phones and connections.
Lab data (the big score out of 100) is a single simulated test run by Google’s Lighthouse tool at that moment. Google’s scale: 90 or above is good, 50 to 89 needs improvement, below 50 is poor.
Because one is many real visits and the other is one simulated test, Google notes that “the values may differ”. Use the field data to judge how your site really feels to customers, and the lab data to find what to fix.
If a page doesn’t have enough real-user data, PageSpeed Insights shows data for your whole site instead, and if there isn’t enough of that either, it shows none. That’s common for small sites. Just work from the lab results.
Core Web Vitals explained: LCP, INP and CLS
Core Web Vitals are three measurements of how a page feels to use. Here they are in plain words, with Google’s thresholds from web.dev.
| Measure | What it means | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the biggest thing at the top of the page (usually a photo, video or big heading) appears | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page reacts when someone taps, clicks or types | 200 milliseconds or less | Over 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the page jumps about while loading, like a button moving just as you tap it | 0.1 or less | Over 0.25 |
Anything between “good” and “poor” is marked as needing improvement. Google measures these at the 75th percentile of visits, which roughly means three out of four visits should hit the “good” mark. A page passes the Core Web Vitals assessment in PageSpeed Insights when all three are good. (INP replaced an older measure, First Input Delay, and became a stable Core Web Vital in 2024, so older articles may still mention FID.)
Does website speed affect your Google ranking?
It can play a part, but Google is careful about how much. Google’s page experience guidance says “Core Web Vitals are used by our ranking systems”. It also says “There is no single signal” and that “Google Search always seeks to show the most relevant content, even if the page experience is sub-par.”
Where there are lots of equally helpful pages for a search, Google says: “Having a great page experience can contribute to success in Search, in such cases.” And it recommends site owners “achieve good Core Web Vitals for success with Search and to ensure a great user experience generally.”
So a faster site won’t lift you above a competitor with more useful pages. The better reason to fix a slow site is your visitors: a page that drags on a phone is an easy one to leave.
How to check website speed across your whole site
PageSpeed Insights tests one page at a time. If your site is set up in Google Search Console, open its Core Web Vitals report to see your whole site at once. (Not set up yet? Our guide to getting your website on Google with Search Console walks you through it.)
The report uses real visitor data, groups similar pages together and marks each group Good, Need improvement or Poor based on its worst measure, with mobile and desktop shown separately. It only includes pages Google has indexed and leaves out pages without enough data, so a small site may see little or nothing there. It links to PageSpeed Insights for testing an example page.
Once you’ve fixed a problem, you can ask Search Console to check it. It then watches your pages over a 28-day period to see whether the issue has gone.
What to fix: the usual suspects on a small WordPress site
Scroll down PageSpeed Insights to the diagnostics list. It’ll name specific problems. On small business sites, these come up again and again.
1. Photos that are far too big
A photo straight off a phone or camera is often far larger than the space it fills on screen. Google’s web.dev guide to LCP recommends compressing images and using modern formats such as WebP or AVIF, and WordPress’s own performance guide says to “make sure all image files are optimized”.
WordPress helps a bit: since version 5.3 it automatically scales down any uploaded image wider or taller than 2,560 pixels. That’s still far bigger than most spaces on a page, so resize photos to roughly the size they’ll be shown before you upload them, and save them as compressed JPG or WebP.
2. Too many plugins
Each plugin can add code that loads on every page. WordPress’s performance guide puts it plainly: the number of plugins and how well they’re built “will also have a huge impact on your site’s performance”. It also says “deactivating and deleting unnecessary plugins is a significant way to improve performance.”
Go to Plugins in your dashboard and ask of each one: do I still use this? If not, deactivate it and delete it. Take a backup first, and check the site after each change.
3. Sliders and videos at the top of the page
A big rotating slider or background video at the top is often the “largest thing” that LCP measures. Google’s own advice on carousels notes that large, above-the-fold carousels “often contain the page’s LCP element” and simply says “Don’t use autoplay”, which can also make the page jump about. A single well-sized photo with a clear headline and a phone button is a lighter alternative.
4. Hosting that responds slowly
Before anything can show on screen, your hosting has to send the first bit of the page. Google’s web.dev puts it this way: “Nothing can happen on the frontend until the backend delivers that first byte.” PageSpeed Insights measures this as Time to First Byte (TTFB). If it’s consistently slow even on a simple page, the hosting plan may be the bottleneck. Ask your host what they can do, and whether your site runs on a current PHP version (WordPress notes newer versions usually perform better).
5. Things that jump about
If your CLS is poor, look for images or videos without a set size and embedded widgets that resize as they load. Also look for content that appears above what’s already on screen and pushes it down, and fonts that swap in late. Google’s CLS guide lists these as common causes.
Common questions
Do I need a score of 100? No. Google treats a lab score of 90 or above as good, and its Core Web Vitals assessment is based on real visitors, not the lab score.
Will fixing speed get me more customers? It removes a reason people leave. It won’t make up for a site that doesn’t clearly say what you do, where, and how to contact you. Our tradesperson website checklist covers those basics.
Free help
- What is SSL, and why does my website say “Not secure”?
- Website accessibility in the UK: a plain-English first step
- Website running costs for a UK small business: hosting, domain and email
- How to update WordPress safely and keep your site in good shape
- Add photos to WordPress without slowing your site
- Does your website look abandoned? 7 quick fixes
If you’re starting again
At Hintling Studio, every package includes SEO basics and Google Search Console set up. After launch the site is yours to run, and the checks in this guide are ones you can do yourself. See what’s included on our prices page, or get in touch with a question.
Hintling Studio is not connected with Google.
