Google PageSpeed Insights is a free Google tool that measures a page’s speed and experience on mobile and desktop, giving a score from 0 to 100 and a list of improvements. Just open pagespeed.web.dev, paste the page address and click “Analyze”. In this guide we explain how to read the report and what to do to improve your score.
Google PageSpeed Insights guide: what the score means, how to read LCP, INP and CLS, and 6 practical ways to make your website faster.
Table of Contents(18 sections)
- How to Use Google PageSpeed Insights
- Field Data vs Lab Data: The Difference
- What the Score Means
- Core Web Vitals Explained
- How to Improve Your PageSpeed Insights Score
- The Most Common Diagnostics and How to Fix Them
- Core Web Vitals on WordPress
- Example: Reading a Report Step by Step
- Tracking in Google Search Console
- Speed and Business Results
- Quick Wins You Can Do Today
- How Often to Test
- Mobile vs Desktop Scores
- What a Good Report Looks Like
- Common Mistakes When Reading the Report
- Frequently Asked Questions
- Key Takeaways
- Conclusion
How to Use Google PageSpeed Insights
- Go to pagespeed.web.dev.
- Paste the full page address (for example, your homepage or a service page).
- Click Analyze and wait about 30 seconds.
- Look at the Mobile tab first — it matters most to Google and to your customers.
Test several pages, not just the homepage. A service page with many images can give very different results.
Field Data vs Lab Data: The Difference
Field data (real users)
The “Discover what your real users are experiencing” section uses data from real Chrome visitors collected over the last 28 days. This is the data Google uses to assess Core Web Vitals. Low-traffic websites may not have enough data.
Lab data (simulation)
The 0–100 score comes from a simulated test (Lighthouse) using a mid-range phone and a slow mobile network. It’s used to diagnose problems and varies slightly between tests.
What the Score Means
90 to 100 — Good
The page is fast. Keep an eye on it whenever you add images, plugins or scripts.
50 to 89 — Needs improvement
There are clear optimisations to make. Most small business websites fall in this range.
0 to 49 — Poor
Slowness is already driving visitors away. Start with the recommendations that have the biggest estimated savings.
The score is made up of five metrics: Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), First Contentful Paint (10%) and Speed Index (10%).
Core Web Vitals Explained
LCP — Loading
Time until the largest visible element appears (usually the main image or heading). Good: up to 2.5 s. Poor: over 4 s.
INP — Interactivity
How quickly the page responds to clicks and taps. Good: up to 200 ms. Poor: over 500 ms. It replaced FID in March 2024.
CLS — Stability
How much elements “jump” while the page loads. Good: up to 0.1. Poor: over 0.25.
To pass the assessment, at least 75% of visits must fall in the “Good” range for each metric. We explain each one in detail in our complete Core Web Vitals guide.
How to Improve Your PageSpeed Insights Score
1. Optimise images
Convert images to WebP or AVIF, resize them to the size they’re displayed at and lazy-load the ones below the fold. Don’t lazy-load the main image at the top — it delays LCP.
2. Use caching and good hosting
A caching plugin (or server-side caching) and fast hosting lower server response time, which is the foundation for every other metric.
3. Reduce JavaScript
Chat scripts, ad pixels, sliders and too many plugins increase Total Blocking Time and hurt INP. Remove what you don’t use and defer what isn’t essential.
4. Book space for images and ads
Set width and height on images, videos and banners. That way the page doesn’t “jump” while loading and CLS stays low.
5. Optimise fonts
Use few font families and weights, host fonts on your own server and use font-display: swap so text appears straight away.
6. Prioritise above-the-fold content
Tell the browser which image is the main one (for example, with fetchpriority=”high”) and load the CSS needed for the visible part of the page first.
The Most Common Diagnostics and How to Fix Them
The “Diagnose performance issues” section lists recommendations with estimated savings. The most frequent:
Eliminate render-blocking resources
CSS and JavaScript files the browser must load before showing the page. Fix: defer non-essential scripts and load critical CSS first.
Reduce unused JavaScript
Plugin, chat or pixel scripts loaded on pages where they are not used. Fix: disable what you don’t use and load the rest only where needed.
Properly size images
Images larger than the size they are displayed at. Fix: resize them and use responsive images (srcset).
Serve images in next-gen formats
Heavy JPG or PNG images. Fix: convert to WebP or AVIF.
Reduce initial server response time
The server is slow to respond. Fix: page caching, faster hosting and an up-to-date PHP version.
Avoid large layout shifts
Elements pushing content around while loading. Fix: fixed dimensions on images, ads and banners.
Minimise main-thread work
The browser is busy processing JavaScript. Fix: fewer plugins, fewer effects and deferred scripts.
Serve static assets with an efficient cache policy
Files without a cache lifetime. Fix: caching rules on the server or in your caching plugin.
Core Web Vitals on WordPress
On a WordPress site, most improvements come from configuration, not code:
- Caching plugin: enable page caching, CSS and JavaScript minification and script deferral. Test the site after each option.
- Image optimisation: automatic WebP conversion and lazy loading, except for the main image at the top.
- Lightweight theme: effect-heavy themes and bulky page builders are the most common cause of low scores.
- Fewer plugins: each plugin can add CSS and JavaScript to every page. Deactivate what you don’t use.
- Fonts: self-host fonts and limit the number of weights.
- Hosting: a server with built-in caching (LiteSpeed or Nginx) and current PHP lowers response time.
To go further, see our WordPress SEO service.
Example: Reading a Report Step by Step
Imagine a service page scoring 54 on mobile. An organised reading would be:
- Field data: real-user LCP is 3.4 s (needs improvement); INP and CLS are good. The main issue is loading.
- LCP element: the report shows the largest element is the hero image.
- Diagnostics: the image is a 1.8 MB JPG and is lazy-loaded.
- Action: convert it to WebP, resize it to its display size and remove lazy loading from that image.
- Check: run a new PageSpeed test and follow the real-user data over the next weeks.
Always start with the worst metric and the element the report flags as responsible.
Tracking in Google Search Console
PageSpeed Insights analyses one page at a time. To see the whole website, use the Core Web Vitals report in Google Search Console: it groups pages with similar issues, separates mobile and desktop and shows the trend over time. Once you fix a group of pages, you can request validation of the fix in the report itself.
Speed and Business Results
A fast website isn’t just for Google. Slow pages make visitors give up before they see your offer, especially on mobile networks. In online stores and campaign landing pages, every second saved tends to show up as more leads and sales — and as more profitable ads, because fewer paid clicks are lost waiting for the page to load.
Quick Wins You Can Do Today
- Compress and convert your five heaviest images to WebP.
- Deactivate plugins you no longer use.
- Remove sliders and autoplay videos from the top of the homepage.
- Turn on page caching in your hosting panel or caching plugin.
- Check that the main image at the top is not lazy-loaded.
How Often to Test
Test whenever you install a new plugin, change theme, add advertising or chat scripts, or launch important pages. On top of that, review the Core Web Vitals report in Search Console once a month — it shows issues a one-off test may miss.
Mobile vs Desktop Scores
It’s normal for the mobile score to be noticeably lower than the desktop score. The mobile test simulates a mid-range phone on a slower network, so heavy images and JavaScript weigh much more. Since most visits now come from mobile, focus your effort there first; desktop usually improves along with it.
What a Good Report Looks Like
A healthy page typically shows “Passed” in the Core Web Vitals assessment for real users, a mobile score in the green or high orange range, an LCP element that is an optimised image or heading, very few layout shifts and only a handful of third-party scripts. If your report looks like this, focus on content and conversion rather than squeezing out the last few points.
Low score and not sure where to start? Our technical SEO team optimises speed and Core Web Vitals, and the websites we build launch with scores above 90. From €350+VAT.
Common Mistakes When Reading the Report
- Only looking at desktop — the mobile version is almost always slower and matters most.
- Chasing 100 — going from 92 to 100 rarely brings more customers. Focus on getting Core Web Vitals into the green.
- Confusing lab and field data — the simulated score can be low while real users have a good experience, or the other way round.
- Testing only once — results vary. Run two or three tests and compare.
Frequently Asked Questions
Is Google PageSpeed Insights free?
Yes. It’s a free Google tool, with no sign-up, and it can analyse any public page — including your competitors’.
Does the PageSpeed score affect Google rankings?
Not directly. Google uses Core Web Vitals measured on real users as one of its page experience signals. The 0–100 score is a diagnostic, but improving it usually improves those signals too.
Why does the score change between tests?
Lab tests depend on server load, network conditions and third-party scripts at the time of the test. Variations of a few points are normal.
Why is there no real-user data?
Field data only appears when the page has enough visits from Chrome users in the last 28 days. On small websites, use the lab data and Google Search Console.
What’s a good score for a business website?
Above 90 on mobile is excellent. More important than the number is having LCP, INP and CLS in the “Good” range for real users.
Does Google PageSpeed work for WordPress sites?
Yes. It works with any public page, whatever the platform. On WordPress, the recommendations are usually solved with caching, image optimisation and fewer plugins.
What is the difference between PageSpeed Insights and Lighthouse?
PageSpeed Insights uses Lighthouse for lab data and adds real-user data from Chrome. Lighthouse in Chrome only runs the lab test on your own computer.
Do caching plugins fix everything?
They help a lot, but they don’t fix heavy images, slow themes or plugin overload. Treat caching as one piece of the solution, not the only one.
Does PageSpeed Insights keep a history of my tests?
No. To track progress, note your results or use the Core Web Vitals report in Search Console, which shows the trend over time.
Can I test pages that require login?
No. PageSpeed Insights only analyses public pages. For pages behind a login, run Lighthouse from Chrome DevTools while logged in.
Why is my score different in other speed tools?
Each tool uses different test locations, devices and network settings. Compare results from the same tool over time rather than across tools.
Should I use a CDN?
A CDN serves files from servers closer to your visitors and can speed up images and static assets, especially for international traffic. Many hosting providers include one; turn it on and test before and after.
Do Core Web Vitals matter for small local websites?
Yes, though they are only one ranking signal among many. For local businesses, a fast mobile experience also matters directly: people searching on their phones often call or leave within seconds.
Key Takeaways
- Google PageSpeed Insights is free and measures speed and experience on mobile and desktop.
- Real-user data (28 days) counts for Core Web Vitals; the 0–100 score is a diagnostic.
- LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1 are the “Good” thresholds.
- Images, hosting, caching and JavaScript are the most common causes of slowness.
- Use the Core Web Vitals report in Search Console to track the whole website.
Conclusion
Google PageSpeed Insights shows you in seconds what makes your website slow and where to start. Start with mobile, look at real-user data first and fix images, hosting and JavaScript. If you’d rather we took care of it, get in touch.