TL;DR — Quick Summary
PageSpeed Insights combines CrUX field data (what Google uses for rankings) with Lighthouse lab data (actionable diagnostics) in one free tool. Field data shows real-user CWV pass/fail; lab data shows a 0–100 score with fix recommendations.
What is Google PageSpeed Insights (PSI)?
Google PageSpeed Insights (PSI) evaluates page performance using both field data (CrUX — real Chrome users over a 28-day rolling window) and lab data (Lighthouse — simulated mobile/desktop environment). It provides:
- •Field data section — CWV pass/fail (LCP, INP, CLS) plus FCP and TTFB at the 75th percentile. This is what Google uses for ranking.
- •Lab data section — Lighthouse performance score (0–100) with metric breakdowns.
- •Opportunities — Specific optimizations with estimated time savings.
- •Diagnostics — Additional analysis and context.
PSI tests both mobile and desktop. Mobile is the default and typically scores 20–30 points lower than desktop due to throttled simulation.
History & Evolution
Key milestones:
- •2010 — Google launches original PageSpeed Insights with a 0–100 scoring system.
- •2018 — PSI rebuilt to use Lighthouse for lab data and CrUX for field data.
- •2020 — Core Web Vitals section added, showing LCP, FID, CLS from CrUX.
- •2024 — INP replaces FID in the CWV section. Enhanced diagnostics.
- •2025–2026 — PSI remains the primary tool. API v5 provides programmatic access for monitoring dashboards.
How PSI is Measured
PSI runs tests by:
- 1Field data — Querying CrUX for the entered URL (or origin if URL-level data is insufficient). Shows 75th percentile metrics over a 28-day rolling window.
- 2Lab data — Running Lighthouse on Google's servers with standardized hardware and network throttling.
Results are available in 15–30 seconds. The API allows programmatic access with rate limits.
Key rule: Field data (CrUX) determines Google rankings. Lab data (Lighthouse, WebPageTest) is for debugging and iteration.
Common Causes of Poor PSI Scores
Common issues revealed by PSI:
- 1Field data failing, lab data passing — Real users on slow devices/networks experience worse performance than the lab simulation.
- 2No field data available — Page doesn't have enough Chrome traffic for CrUX. Google falls back to origin-level data.
- 3Low Lighthouse score — Same causes as Lighthouse: large JS, unoptimized images, render-blocking resources.
- 4Mobile much worse than desktop — Common when sites aren't optimized for mobile-first.
- 5Origin-level CWV failing — A few slow pages drag down the entire domain's CWV assessment.
Frequently Asked Questions
For step-by-step optimization, platform-specific fixes, code examples, and case studies, read our full guide:
The Ultimate Guide to Website Performance Measurement, Tools & Data: Lab, Field & Everything Between in 2026Struggling with PSI?
Request a free speed audit and we'll identify exactly what's holding your scores back.