PageSpeed Insights(PSI)

Long definition

PSI is the merge of two systems most teams confuse. The top half of every PSI report is field data — pulled from the Chrome User Experience Report (CrUX) — showing the 75th percentile of real users' LCP, CLS, INP, FCP, and TTFB over a 28-day rolling window. The bottom half is lab data — a single Lighthouse run on Google's infrastructure with throttled network and CPU.

The two halves often disagree, and that's the point. Lab is repeatable and diagnostic; field is what users actually experience and what Google ranks on. A page can ship a Lighthouse score of 95 and still fail Core Web Vitals because real users hit it on slow devices over flaky networks. Conversely, a 60 in Lighthouse can pass Core Web Vitals if real-world conditions happen to be kinder than the lab simulation.

Field data appears only when CrUX has enough samples for the URL or origin. Below the threshold (roughly 1,000+ Chrome user-page-loads in 28 days), you get origin-level data instead of URL-level, or no field data at all. Brand-new pages and low-traffic URLs default to lab-only.

PSI is also accessible programmatically via the PSI API, which most monitoring tools (DebugBear, SpeedCurve, Calibre) use to ingest results into dashboards. The web UI at pagespeed.web.dev is the human entry point; the API is what scales.

The single most useful PSI workflow: check field data first to see what users experience, then check lab data to diagnose why. Optimizing Lighthouse without verifying CrUX moves often produces the score-up-but-rankings-flat outcome.

Common misconceptions

• "PSI score is my Core Web Vitals pass/fail." The Lighthouse performance score (0-100) at the bottom of PSI is not the Core Web Vitals signal. Pass/fail is determined by the field data section at the top — LCP, CLS, INP each at the "Good" 75th percentile.
• "PSI lab and field should match." They almost never match exactly. Lab is one synthetic run; field is millions of real loads averaged. They measure overlapping but different things — disagreement is normal and informative.
• "No field data means my page is too new." Sometimes. It also means traffic is too low for CrUX to publish URL-level data. Origin-level CrUX usually covers larger sites; small sites may never get URL-level data at all.
• "Mobile PSI scores apply to desktop." PSI shows separate mobile and desktop reports because they use different throttling and different CrUX device segments. Pass mobile, pass desktop are independent.