I once had a client whose PageSpeed score was 98, glowing green in every audit, while their real users complained the site crawled. Another client's Lighthouse was an anxious red while their field data showed they were crushing every threshold. Both were running the same Core Web Vitals and getting opposite answers.
This isn't a software bug. It's lab data and field data describing two different universes, and until you can tell them apart, you'll keep "fixing" problems that aren't real and ignoring the ones that are.
The two universes
Lab data is a controlled experiment. Lighthouse loads your page on a fixed, fast connection, in a clean browser, and measures how it behaves. It's great for one thing: isolating a specific cause. Is the LCP image too heavy? Is a script blocking render? Lab testing isolates it cleanly.
Field data is the messy truth. It comes from the Chrome User Experience Report — the actual conditions of millions of real users on their real phones, real networks, moving trains, and congested coffee shops. It's a distribution, not a single number, and it's slow to update.
When they disagree, the field wins
Here's the ranking truth most people find uncomfortable: Google ranks on field data. It has no choice — it can't run Lighthouse on every page every minute. It looks at real user experience. So when Lighthouse says "fast" and field data says "slow," your users are experiencing slow, and adding caching won't help until you believe them.
Conversely, a low Lighthouse score on a page with great field data isn't always an emergency — it might mean the test environment is pessimistic relative to your real audience. Don't go chasing a perfect lab score if your users aren't complaining.
How to actually diagnose
Stop asking "am I fast?" and start asking "which one is right here."
- Confirm with field data first. Check CrUX for your actual pages and your actual user distribution. This decides whether there's a real-user problem at all.
- Use lab data to find the cause. Once you've confirmed users are slow, Lighthouse (and the waterfall) tells you which resource or render issue to fix.
- Watch for the trend. Field data updates on a rolling window, so a recent deployment may not show for weeks. Account for that lag before declaring victory or panic.
The practical habit
Treat the two as a pair, never as competitors. Field data tells you the real user experience and what Google measures. Lab data tells you the mechanism behind it. You need both, in that order: confirm the problem in reality, then diagnose it in the lab.
The clients who get fast are the ones who stop trusting a single green score and start asking which of the two universes is telling the truth about their users. Usually, it's the messy one.
If your scores tell two different stories and you're not sure which to trust, our teardown reconciles them — we check your real user data, then isolate what's actually driving it in the lab. Book a free website teardown and we'll cut through the contradiction.