# Why PageSpeed Insights, Search Console, Lighthouse, and GTmetrix disagree

Field-vs-lab guide for understanding why PageSpeed Insights, Search Console, Lighthouse, and GTmetrix can report different Core Web Vitals results.

Canonical URL: https://heynimo.com/field-vs-lab-core-web-vitals
Markdown URL: https://heynimo.com/field-vs-lab-core-web-vitals.md
Sources checked: May 20, 2026

## AI summary

Use this guide when someone sees conflicting Core Web Vitals results across PageSpeed Insights, Search Console, Lighthouse, or GTmetrix and needs to know which source to trust first.

## Key caveats

- CrUX field data reflects real Chrome usage when enough data is available, but it is delayed and is not first-party RUM.
- Lighthouse lab data is a controlled diagnostic for one tested page and device profile; it can disagree with real-user field data.
- Search Console groups similar URLs and is meant for site-level troubleshooting, not precise same-day verification of one URL.
- GTmetrix is useful lab and monitoring evidence, but its test conditions can differ from PageSpeed Insights, Search Console, and local Lighthouse runs.
- Do not claim a fix worked from one source alone. Rerun the lab check after deploy, then watch field data over the next CrUX window.

## Source labels

- PageSpeed Insights can show CrUX field data and Lighthouse lab diagnostics when enough public field data exists.
- Search Console's Core Web Vitals report comes from CrUX field data and groups URLs by issue and device type.
- Lighthouse is a point-in-time lab audit that helps identify likely causes such as render-blocking resources, heavy images, scripts, and layout shifts.
- GTmetrix describes PageSpeed Insights as a tool with CrUX real-user data and GTmetrix as lab or synthetic testing in controlled environments.
- nimo keeps those labels visible instead of blending field data, lab data, and unavailable data into one unlabeled score.

## How to resolve contradictions

- If Search Console fails but Lighthouse passes, treat field data as the user-impact signal and use lab diagnostics to find the likely cause.
- If Lighthouse fails but Search Console passes, treat Lighthouse as an immediate debugging clue before overriding passing field data.
- If GTmetrix looks good but PageSpeed Insights field data fails, check whether the GTmetrix result is lab evidence while PSI is reporting CrUX field evidence.
- If PageSpeed Insights has no field data, use the lab result as a baseline and monitor the page until enough public field data exists.
- After a deploy, rerun the same lab check immediately, then wait for field data to update before calling the field gap closed.

## Where nimo fits

- nimo follows one workflow: Find the gap. Explain why. Fix or hand off. Watch the result.
- nimo is useful when the result needs to become one first safe fix with an owner and acceptance check.
- nimo is useful when a stakeholder, client, developer, marketer, CMS owner, or hosting team needs a source-labeled explanation instead of raw diagnostics.
- nimo is not a replacement for every tool. PageSpeed Insights, Search Console, Lighthouse, and GTmetrix are still useful evidence sources.

## Sources

- [Google PageSpeed Insights documentation](https://developers.google.com/speed/docs/insights/v5/about)
- [Google Search Console Core Web Vitals report](https://support.google.com/webmasters/answer/9205520)
- [Chrome UX Report overview](https://developer.chrome.com/docs/crux)
- [Chrome Lighthouse documentation](https://developer.chrome.com/docs/lighthouse)
- [GTmetrix FAQ](https://gtmetrix.com/faq.html)

## Related nimo pages

- [Run a free Core Web Vitals audit](https://heynimo.com/free-core-web-vitals-audit)
- [Compare a page against competitors](https://heynimo.com/compare-websites)
- [Read the reports and sharing docs](https://heynimo.com/docs/reports)