Measuring Core Web Vitals in the Real World

Core Web Vitals can look very different in a local Lighthouse run versus production traffic. Lab tools are still essential for debugging, but field data is what tells you how your site performs for real users on real devices and networks.

PageSpeed Insights

PageSpeed Insights is the fastest way to combine both views in one place:

• Lab data from Lighthouse, useful for repeatable tests and diagnosing specific render issues.
• Field data from the Chrome User Experience Report (CRuX), useful for seeing how users actually experience your pages over time.

Start with PageSpeed Insights to identify your biggest bottlenecks, then use these practical fixes:

• PageSpeed Insights Performance Issues
• Critical Render Path

You can also inspect a live example report:

Chrome User Experience Report (CRuX)

CRuX is Google’s public dataset of real-user experience. It aggregates anonymized Chrome usage telemetry and reports metrics like LCP, INP, and CLS at the 75th percentile, which is the pass/fail threshold Google uses for “good” Core Web Vitals.

Important context when reading CRuX:

• Results use a 28-day rolling window, not real-time measurements.
• Data is typically aggregated at the origin level (scheme + host + port).
• New or low-traffic sites may not have enough data to appear in reports.

The easiest way to view this data without writing queries is:

Querying CRuX programmatically

Use CRuX programmatic access when you need to automate reporting, compare multiple origins, or track trends over time.

• CRuX BigQuery dataset: best for historical analysis, large-scale comparisons, and custom dashboards.
• CRuX API: best for lightweight lookups in scripts, CI checks, or app backends.

Further reading

• Web Vitals overview on web.dev
• Why lab and field data can differ on web.dev
• CRuX documentation on developer.chrome.com