PageSpeed Matters
    Speed Audit
    Let's Talk
    PageSpeed Matters
    Book a Call
    Tools & Data Sources · Glossary

    Google PageSpeed Insights (PSI) · Definition & Explanation 2026

    Google PageSpeed Insights (PSI) is the most authoritative free performance testing tool available because it uniquely combines two data sources in a single view: real-user field data from the Chrome User Experience Report (CrUX) and simulated lab data from Lighthouse.

    The field data section shows how actual Chrome users experience your page — this is the same data Google uses for ranking decisions. The lab data section provides a Lighthouse performance score with specific optimization recommendations. Together, they answer both 'How does Google see my page?' and 'What should I fix?'

    PSI tests both mobile and desktop, defaulting to mobile (which is typically harder to pass and reflects Google's mobile-first indexing). The tool is available at pagespeed.web.dev and via the PageSpeed Insights API for programmatic access.

    In 2026, PSI remains the single most important performance tool for SEO professionals and web developers. A page that passes all CWV in the PSI field data section is receiving the 'good page experience' signal in Google Search.

    Updated 2026-02-28
    M
    By Matt Suffoletto

    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:

    1. 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.
    2. 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:

    1. 1Field data failing, lab data passing — Real users on slow devices/networks experience worse performance than the lab simulation.
    2. 2No field data available — Page doesn't have enough Chrome traffic for CrUX. Google falls back to origin-level data.
    3. 3Low Lighthouse score — Same causes as Lighthouse: large JS, unoptimized images, render-blocking resources.
    4. 4Mobile much worse than desktop — Common when sites aren't optimized for mobile-first.
    5. 5Origin-level CWV failing — A few slow pages drag down the entire domain's CWV assessment.

    Frequently Asked Questions

    The Lighthouse score (lab data) does not directly affect rankings. The CrUX field data (CWV pass/fail) does affect rankings as part of the Page Experience signal.

    Mobile simulation uses a mid-tier phone on throttled 4G. Desktop uses unthrottled broadband. Mobile scores are typically 20–30 points lower. Google uses mobile for mobile-first indexing.

    The page doesn't have enough Chrome traffic for CrUX (needs sufficient pageviews over 28 days). PSI falls back to origin-level data. New or low-traffic pages often lack URL-level data.

    CrUX uses a rolling 28-day window. After deploying fixes, improvements take up to 28 days to fully reflect in field data.

    Field data is more important for rankings. However, improving Lighthouse scores typically improves field data over time. Use Lighthouse for diagnosis, field data for measuring real impact.

    PSI cannot test authenticated pages. Use Lighthouse in Chrome DevTools (where you're logged in) for authenticated testing.

    PSI includes both CrUX field data AND Lighthouse lab data. Running Lighthouse locally gives only lab data. PSI is more comprehensive; local Lighthouse is faster for iteration.

    The API (v5) returns JSON with both field and lab data. Free with rate limits. Use it for monitoring dashboards and CI/CD integration. Documentation at developers.google.com/speed/docs/insights/v5.

    Struggling with PSI?

    Request a free speed audit and we'll identify exactly what's holding your scores back.

    Request An Audit