Google PageSpeed Insights is a free tool that scores your website’s performance from 0 to 100 and identifies specific technical issues slowing it down. This guide explains what the score means, how to read each section of the report, and which fixes have the most impact — starting with what actually matters for SEO.
What Is Google PageSpeed Insights & How It Works
The tool provides a detailed performance analysis for both mobile and desktop by fetching your URL with different user-agents. It evaluates critical aspects like loading speed, server response time, and page structure, generating a score from 0 to 100.
From Analysis to Action: Understanding Your Report
The report details “Opportunities” and “Diagnostics,” suggesting fixes like image optimization and browser caching. However, implementing these technical solutions often requires expert help. Simply knowing the problem isn’t the same as fixing it.
Why Your Score Matters: Core Web Vitals & SEO
Your PageSpeed Insights score is directly tied to Core Web Vitals—key user experience metrics (LCP, CLS, INP) that are official Google ranking factors. A poor score can suppress your search rankings and increase bounce rates, while a faster site improves user engagement and conversions.
Beyond the Basics: The Limitations of DIY Fixes
While the tool is excellent for diagnosis, its suggestions can be technically complex. Correctly optimizing server response, render-blocking resources, and caching requires precise implementation to avoid breaking your site. This is where professional PageSpeed Insights optimization becomes critical.
How to Use the Google Page Speed Insights Tool
Google PageSpeed Insights is a useful tool for website optimization, as it analyzes the performance and speed of your web pages. To use it effectively, follow these steps.
First, go to the PageSpeed Insights website. Once there, enter the URL of the webpage you want to analyze into the search bar. Click on the “Analyze” button.
After a few moments, the tool will generate a report that evaluates the performance of your webpage on both desktop and mobile devices. It provides an overall score, ranging from 0 to 100, indicating the page’s performance. A higher score indicates better performance.
The report also includes a section called “Opportunities” which highlights areas where you can improve your webpage’s speed and performance. It suggests specific optimizations like compressing images or leveraging browser caching.
In addition to the “Opportunities” section, the report also includes a “Diagnostics” section. This section identifies issues that may be affecting your webpage’s performance and provides recommendations on how to fix them.
By using Google PageSpeed Insights regularly, you can identify areas for improvement and optimize your web pages for better performance. Implementing the suggested optimizations can result in faster loading times and ultimately improve the user experience on your website.
Understanding the Page Speed Insights Report
Understanding the PageSpeed Insights report is crucial for website owners. This report, developed by Google, analyzes the performance of web pages on desktop and mobile devices. By understanding the report, website owners can identify and resolve issues that may be impacting the loading speed of their pages.
What the score ranges mean (0–49, 50–89, 90–100)
Google uses three colour-coded bands to classify your score. Red (0–49) means Poor — the page has significant performance issues that are likely affecting both user experience and rankings. Orange (50–89) means Needs Improvement — performance is acceptable but there are gains available. Green (90–100) means Good. These thresholds apply to both the overall score and to each individual Core Web Vital. Note that Google evaluates desktop and mobile separately — most sites score 15–25 points lower on mobile than desktop because mobile tests simulate a slower device and network.
Lab data vs field data — why your score changes
Google PageSpeed Insights combines two different types of data in a single report, and understanding the difference explains why your score varies between tests.
Lab data is collected by running Lighthouse in a controlled environment each time you test. It simulates a mid-range mobile device on a throttled 4G connection. Because it runs fresh each time, small variations in server response time, network conditions at the moment of testing, and third-party script loading will cause the score to fluctuate by 5–15 points between runs. This is normal.
Field data (labelled “Discover what your real users are experiencing”) comes from the Chrome User Experience Report (CrUX) — anonymised performance data collected from real Chrome users visiting your site over the past 28 days. This data only appears if enough real users have visited your site. Field data is what Google actually uses as a ranking signal, not the lab score. If your field data shows Good Core Web Vitals but your lab score is 65, your rankings will not be penalised.
Practical implication: do not chase the lab score in isolation. If your field data shows LCP as “Needs Improvement” and your lab score is 72, fix the LCP first — that is what affects rankings. If your lab score drops to 58 after a test but field data still shows Good, do not panic.
The Four Core Web Vitals
Core Web Vitals Assessment is a tool used to measure and analyze the performance of a website. It focuses on four main aspects that play a critical role in user experience: loading speed, interactivity, and visual stability.
LCP — Largest Contentful Paint
Google’s Core Web Vitals are three specific metrics — LCP, CLS, and INP — that are official ranking signals. This section also covers FCP (First Contentful Paint), which is not a Core Web Vital but appears prominently in the PageSpeed Insights report and is closely related to LCP. Understanding all four helps you read your report accurately.
CLS — Cumulative Layout Shift
Visual stability is assessed using the Cumulative Layout Shift (CLS) metric. It measures how stable a webpage’s visual elements are while it loads. Websites with a low CLS score have fewer unexpected layout shifts, which helps users avoid accidentally clicking on the wrong elements. A good CLS score is under 0.1. Needs Improvement is 0.1–0.25. Anything above 0.25 is Poor.
INP — Interaction to Next Paint
Interactivity is measured using INP (Interaction to Next Paint), which replaced FID as an official Core Web Vital in March 2024. INP measures the time from any user interaction — click, tap, or keyboard press — to the next visual response from the page. A good INP score is under 200ms. Unlike FID, which only measured the delay before the browser started responding, INP measures the full response time, making it a more accurate reflection of how responsive a page feels in real use.
FCP — First Contentful Paint
FCP (First Contentful Paint) measures the time from when the page starts loading to when any text, image, or canvas element first appears on screen. A good FCP score is under 1.8 seconds. The most common causes of slow FCP are slow server response time (TTFB), render-blocking CSS or JavaScript in the , and the absence of resource preloading for critical assets. FCP is a leading indicator — if it is slow, LCP will almost certainly be slow too.
Reading Your Report: Opportunities vs Diagnostics
Opportunities
The Opportunities section lists specific changes Google recommends to improve your score. Each item shows an estimated time saving — for example “Eliminate render-blocking resources: potential savings of 1.2s”. These are prioritized fixes, not a to-do list to work through randomly.
Focus on the items with the highest estimated savings first. Common opportunities you will see on WordPress sites include: serve images in next-gen formats (WebP/AVIF), eliminate render-blocking resources (usually JavaScript loaded in the ), reduce unused JavaScript, and defer off-screen images. Note that some opportunities appear on every site and have minimal real-world impact — “Properly size images” for example often shows a saving that disappears when tested against real user connections.
Diagnostics
The Diagnostics section provides additional technical information about your page but does not directly contribute to your score and does not show estimated time savings. Think of it as context rather than action items. Common diagnostics include: “Ensure text remains visible during webfont load”, “Avoid an excessive DOM size”, and “Minimize main-thread work”. These inform you about underlying structural issues — for example, a large DOM size explains why your INP score is poor — but fixing them requires understanding the root cause rather than following a simple checklist. Address Opportunities first to move your score; use Diagnostics to understand why a particular metric is struggling.
PageSpeed Insights vs Other Speed Tools
Tool | Data source | Mobile/Desktop | Free | Best for |
PageSpeed Insights | Lab + CrUX field data | Both | Yes | Official Google benchmark, ranking signal check |
Lighthouse (in Chrome) | Lab only | Both | Yes | Developer debugging, instant local testing |
WebPageTest | Lab, real browsers | Both | Yes (basic) | Detailed waterfall, filmstrip view |
GTmetrix | Lab (Lighthouse) | Both | Yes (basic) | Easy-to-read reports, historical tracking |
For SEO purposes, PageSpeed Insights is the only tool that shows field data from real users and is the closest proxy to what Google measures for rankings. Use the other tools to diagnose and fix specific issues, then validate the fix in PageSpeed Insights.
Google classifies PageSpeed Insights scores as follows: 90–100 is Good, 50–89 Needs Improvement, and 0–49 is Poor. On mobile, a score of 75–85 is realistic for most functional WordPress sites without sacrificing features. Chasing 100 often means removing functionality that benefits real users — a score in the 80s with Good Core Web Vitals field data will not disadvantage your rankings.
PageSpeed Insights runs a fresh Lighthouse test each time using a simulated mid-range mobile device on a throttled 4G connection. Small variations in server response time, third-party script loading, and network conditions at the moment of testing cause the score to fluctuate by 5–15 points between runs — this is normal. For a stable picture, run three tests and take the average. More importantly, the field data section (showing real user experiences from CrUX) does not change between tests and is what Google actually uses as a ranking signal.
The PageSpeed Insights score itself is not a direct Google ranking factor. However, the Core Web Vitals it measures — LCP, CLS, and INP — are confirmed ranking signals as part of Google’s Page Experience update. Improving your score typically improves the underlying Core Web Vitals, which can positively affect rankings, particularly on competitive queries where other ranking factors are similar between sites.
Opportunities are items with an estimated time saving — for example “Eliminate render-blocking resources: potential savings of 1.4s”. These directly affect your score and should be prioritised by highest estimated saving. Diagnostics provide additional context about your page’s performance but do not come with time savings estimates and do not directly contribute to your score. Fix Opportunities first; use Diagnostics to understand underlying issues.
FCP (First Contentful Paint) measures when the very first element — any text, image, or canvas — appears on screen. LCP (Largest Contentful Paint) measures when the main content of the page has finished loading, typically the hero image or largest text block. LCP is the more important ranking signal of the two because it reflects when a user can actually read or engage with the primary content. A good LCP is under 2.5 seconds; a good FCP is under 1.8 seconds.
The three highest-impact fixes for WordPress sites are: (1) compress and convert images to WebP format using a plugin such as ShortPixel or Imagify — images are the most common cause of poor LCP scores; (2) enable server-side caching via LiteSpeed Cache or WP Rocket, which dramatically reduces server response time and improves overall scores; (3) defer or delay non-critical JavaScript such as chat widgets, tag manager scripts, and tracking pixels, which block the browser from rendering the page. If you would rather have these fixed professionally, see our PageSpeed Insights optimisation service.
COMPLETE THE CONTACT FORM AND GET A FREE QUOTE
Getting your website to the top of Google requires the right strategy, the right expertise, and a partner who is accountable for results. If you are ready to invest in SEO that drives real business growth, we would like to hear from you.
Contact Solomon Designs today for a no-obligation SEO consultation. We will review your current search visibility, identify the most significant ranking opportunities for your business, and outline a clear strategy for getting your website on top of Google search for the terms that matter most to your customers.
Whether you are looking for a full SEO campaign, a website SEO audit, link building support, or ongoing SEO support services, our team is ready to help. Request your free quote and let us show you what expert SEO looks like in practice.
contact form
