2026-06-08 · en

How to read PageSpeed Insights: a practical guide

You run the test, you get a number, and then what? For most business owners, a Google PageSpeed Insights report is a wall of colours, percentages and technical jargon that raises more questions than it answers. A score of 38 in red feels alarming, but the report rarely makes it obvious what is actually wrong or what to do about it.

The good news is that you do not need to be a developer to read the report sensibly. You need to know where to look, which numbers genuinely matter, and how to separate the issues worth fixing from the noise.

What the report is actually telling you

PageSpeed Insights does two different things at once, and confusing them is the most common mistake. It runs a live test of your page right now, and it also reports how real visitors have experienced your page over the past four weeks. These are not the same data, and they often disagree.

Understanding that split is the key to reading the whole report. Everything else flows from knowing which section you are looking at.

Lab data versus field data

Field data sits at the top of the report, usually labelled as the Core Web Vitals assessment. It comes from real Chrome users visiting your site over the previous 28 days. This is the data Google uses to judge your page experience, so it is the part that affects your search rankings. If you only have time to look at one section, look at this one.

Lab data is a single simulated test run on Google's servers in a controlled environment. It is what produces the 0-100 performance score. Lab data is excellent for diagnosing problems and testing fixes, because it is repeatable and detailed, but it does not reflect your real audience.

A page can score 55 in the lab yet still pass its Core Web Vitals in the field, or the reverse. When they conflict, trust the field data for decisions about whether you have a problem, and use the lab data to work out how to solve it.

The three Core Web Vitals

Core Web Vitals are three metrics that measure real user experience. These are the numbers to anchor on. If you want the deeper background, our explainer on what Core Web Vitals are covers each in detail.

  • LCP (Largest Contentful Paint) measures how long the main content takes to appear. Good is under 2.5 seconds. This is usually your hero image, headline or main banner.
  • INP (Interaction to Next Paint) measures how quickly the page responds when someone taps or clicks. Good is under 200 milliseconds. Sluggish menus and slow form fields show up here.
  • CLS (Cumulative Layout Shift) measures unexpected movement as the page loads. Good is under 0.1. If buttons jump around while loading and people mis-tap, your CLS is too high.

Each metric is colour-coded: green is good, orange needs improvement, red is poor. Your goal is three greens in the field data, not a perfect lab score.

The performance score and what to ignore

The big 0-49, 50-89, 90-100 circle is the lab performance score. It is a weighted average of several lab metrics, useful for tracking progress and comparing pages, but it is not the metric Google ranks on. Do not panic over the exact number, and do not chase a perfect 100 — the final points cost far more effort than they return.

Run the test three or four times and take the median, because lab results naturally fluctuate between runs.

Opportunities and Diagnostics

Below the score, the report lists specific findings. Opportunities estimate how much time you could save by fixing each issue, ordered by potential impact. Common entries include oversized images, render-blocking resources, and unused JavaScript. Diagnostics explain underlying causes, such as excessive main-thread work or too many third-party scripts.

Read these as a prioritised to-do list. The estimated savings at the top of Opportunities are where the biggest wins usually live. For a step-by-step approach to acting on them, see our guide on how to improve website speed.

Mobile versus desktop

Always start with the mobile tab. PageSpeed Insights tests mobile on a throttled mid-range phone and a slower connection, which is far harsher than the desktop test. It is also where most of your visitors actually are. A great desktop score paired with a poor mobile score means the experience that matters most is the one failing.

What to fix first

Resist the urge to fix everything. Work in this order:

  • Pass your worst Core Web Vital first, especially if it is red in the field data, because that is what costs you rankings and conversions.
  • Tackle the top Opportunity by estimated savings, which is frequently unoptimised images or render-blocking scripts.
  • Fix any CLS issue, since layout shifts are usually cheap to solve and immediately improve how the site feels.
  • Leave the cosmetic last few points of the lab score alone unless everything else is already green.

If a finding requires changing the platform, theme or core code, that is the point to bring in technical help rather than patching around it.

At Lanoar, we read these reports every day and translate them into a clear plan that focuses on the fixes that move the business, not the vanity score. If you would like to see exactly where your site stands, run our free website audit and we will show you what to fix first.

FAQ

What is a good PageSpeed Insights score?

Google considers 90-100 good, 50-89 needs improvement, and 0-49 poor. The score is a weighted blend of lab metrics and is useful for comparison, but it is not the metric Google actually uses for ranking. Treat it as a thermometer, not the diagnosis.

What is the difference between lab data and field data?

Lab data is a single simulated test run on Google servers under controlled conditions, which produces the 0-100 score. Field data is real performance collected from actual Chrome users over the previous 28 days. Field data is what Google uses to assess Core Web Vitals, so it matters more for SEO.

Why is my mobile score so much lower than desktop?

PageSpeed Insights tests mobile on a throttled, mid-range device and a slower connection, which is far more demanding than a desktop with a fast connection. Most of your visitors are on mobile, so the mobile tab is the one that reflects reality and the one you should prioritise.

What are LCP, INP and CLS?

They are the three Core Web Vitals. LCP measures how long the main content takes to appear, INP measures how quickly the page responds to interactions, and CLS measures unexpected layout shifts. Good thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.

Should I aim for a perfect 100 score?

No. Chasing a perfect score has diminishing returns and can waste effort on changes users never notice. Aim to pass all three Core Web Vitals in the field data, which is what affects rankings and experience, and stop optimising once you are comfortably in the green.

My score changes every time I run the test, is that normal?

Yes. Lab data varies between runs because of network conditions, server load, and third-party scripts loading at different speeds. Run the test three or four times and look at the median rather than reacting to a single result. Field data is far more stable because it is averaged over many real users.