The Score That Doesn't Tell the Whole Story

You run Google PageSpeed Insights on your website and get a 90. You breathe a sigh of relief. Your site is fast. Job done.

Except your bounce rate is still high. Customers still tell you the site feels slow. And your conversion rate hasn't budged.

What's going on? The problem is that PageSpeed's score is a lab measurement. It tests your site in a controlled environment — a specific device, a specific network, a clean browser with no other tabs open. Your actual customers don't live in that environment.

Lab Data vs. Field Data: The Key Distinction

Google actually measures website performance in two completely different ways, and most people only focus on one.

Lab data is what PageSpeed Insights shows you by default. It simulates a page load on a standardized device and network. It's useful for diagnosing specific problems, but it doesn't tell you what your actual visitors experience.

Field data (also called Real User Monitoring or RUM) is collected from real Chrome users visiting your site over the past 28 days. This is the data Google actually uses for rankings — and it's often very different from your lab score.

A site can score 90 in the lab and have terrible field data if:

Most of your visitors are on older, slower phones
Your audience is in a region with slower internet infrastructure
Your site loads fast on a fresh cache but slowly for first-time visitors
Dynamic content or user interactions cause slowdowns after the initial load

The Three Numbers That Actually Matter

Google's Core Web Vitals are the three real-user metrics that feed into both rankings and customer experience. Here's what they mean in plain English:

Largest Contentful Paint (LCP) — How long before the main thing on the page (usually a big image or heading) appears? Under 2.5 seconds is good. Over 4 seconds is a problem. This is the single most impactful metric for first impressions.

Interaction to Next Paint (INP) — When your visitor clicks a button or taps a link, how quickly does something visibly happen? Under 200ms feels instant. Over 500ms feels broken. Poor INP is why sites that "load fast" still feel sluggish to use.

Cumulative Layout Shift (CLS) — How much does the page visually jump around while loading? A score under 0.1 is good. Higher scores mean your visitors are accidentally tapping the wrong things and getting frustrated by a page that won't stay still.

Why a High Score Can Still Mean a Bad Experience

Here's a real-world example I see regularly. A business runs PageSpeed and gets an 85 score. They're happy. But looking at their field data in Google Search Console shows that 40% of their real mobile users are experiencing an LCP over 4 seconds.

Why the gap? The lab test uses a mid-range simulated phone. But a large chunk of their actual customers are using budget Android phones that are two or three years old. On those devices, JavaScript that runs fine in the lab takes three times as long to execute.

The score is misleading. The real-world experience is what's costing them customers.

How to See Your Real User Data

Google Search Console has a "Core Web Vitals" report under "Experience." This shows your actual field data — how real visitors on real devices are experiencing your site, broken down by URL.

This is the data that matters for rankings. If your URLs show "Poor" or "Needs Improvement" here, a good PageSpeed lab score isn't going to protect you.

You can also use the Chrome User Experience Report (CrUX) via PageSpeed Insights — just scroll down past the lab metrics to the "Discover what your real users are experiencing" section.

What This Means for Your Business

The practical takeaway: don't optimise for your PageSpeed score. Optimise for your real users' experience.

That means:

Check your field data in Search Console, not just PageSpeed scores
Test your site on a budget Android phone, not just a high-end device
Pay attention to INP, not just LCP — especially if you have interactive elements like forms or menus
Look at your CLS score if customers complain about "the page jumping around"

The Bottom Line

A PageSpeed score is a starting point, not an endpoint. The number that actually matters is whether your real customers — on their real devices, on their real internet connections — have a fast, stable, responsive experience.

That's what I measure when I audit a site. And that's what determines whether the work we do together actually moves the needle for your business.