What your Google PageSpeed score actually means

Short answer: the 0–100 number is a lab test of how fast one page loads on a simulated mid-range phone. 90 and above is what Google calls good, 50–89 needs improvement, and below 50 is poor. It is a useful to-do list, not a measure of your business or your Google ranking.

PageSpeed Insights is Google's free tool for checking how a page performs. You put in a URL, and it hands back a performance score from 0 to 100, plus a list of specific things slowing the page down. It is genuinely useful. It is also routinely misread. You'll actually see four scores: Performance, Accessibility, Best Practices and SEO. This article is about Performance, the one people usually mean. The "SEO" score is a basic checklist (page titles, descriptions, links), not a prediction of where you rank.

The report contains two different kinds of data

This is the part most people miss, and it explains most of the confusion.

• Lab data. Google loads your page in a controlled test environment, on a simulated mid-range phone over a mobile connection (or a desktop on a wired connection, if you pick Desktop). That is why the mobile score is often noticeably lower than the desktop one for the same page. This is where the 0 to 100 performance score comes from. Because it is a simulation, the number can move a few points between runs on an unchanged page — it is a diagnostic, not a certificate.
• Field data. Measurements from real Chrome users who actually visited your page. This is the more meaningful signal, but Google only shows it when it has enough real traffic data for your URL or your site. Plenty of small-business sites simply do not have enough visitors for it to appear at all, which is normal and is not a finding about your site.

Both are described in Google's own documentation: About PageSpeed Insights, developers.google.com. Worth reading if you want the primary source rather than someone's summary of it — including ours.

"Passed" or "Failed": the Core Web Vitals line

If Google has enough real-visitor data for your site, the top of the report shows a Core Web Vitals assessment instead of a score. It is based on three measurements from real Chrome users over the previous 28 days:

• Largest Contentful Paint (LCP): how long the main content takes to appear. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much things jump around while the page loads. Good is 0.1 or less.

If that section is missing, Google simply doesn't have enough visitor data for your site yet (see above).

What counts as a good PageSpeed score

Google groups the performance score into three ranges: 0–49 is "poor," 50–89 is "needs improvement," and 90–100 is "good." Those labels are Google's wording, not ours.

A score in the middle band is a normal result, not a crisis. It means there is measurable room to improve, and the report will tell you specifically where.

Two things the score is not

It is not a revenue figure. You will see people convert a score into lost customers or lost dollars. Nothing in Google's documentation supports that arithmetic, and we are not going to invent it. Speed matters to people trying to use your site — that is a reasonable thing to believe on its own, without a fabricated number attached to it.

It is not your Google ranking. Google says Core Web Vitals, the real-visitor measurements above, are used by its ranking systems. The 0–100 lab score is not. Google also says it "always seeks to show the most relevant content, even if the page experience is sub-par" (Understanding page experience, developers.google.com). A site can score 95 and rank poorly because it has no content anyone searched for, and a site can score 60 and rank first because it is the most relevant result. Speed is one factor among many.

What to actually do with the report

Scroll past the number. The report's insights and diagnostics identify specific files and elements worth investigating — a large hero image, a font loading late, or a chat widget loading extra code. Follow the measured findings rather than treating every suggestion as equally important.

Test the pages people actually land on, not only your homepage. Check both mobile and desktop results: the mobile test helps expose problems on slower devices and connections. If your site has analytics (Google Analytics, for example), it can show which pages people land on and which devices they use.

A real set of numbers, and what they do not prove

When we were building our own site, we ran mobile PageSpeed Insights against the homepages of six web-design and marketing agencies, on 23 September 2026. The scores were 98, 77, 72, 63, 60 and 60 — an average of roughly 72.

To be exact about what that is: six agency homepages, measured once, on one day. It is a snapshot of one small peer group, and we are not claiming it describes small-business websites generally — we have not measured a sample that would support that. We mention it because it is our own data and it is the honest version of "a lot of professionally built sites land in the middle band too."