PageSpeed Overview
PSI Overview shows the latest PageSpeed Insights performance score for each tracked URL, on both mobile and desktop. PSI scores summarise lab measurements (Lighthouse) into a single 0–100 number per device class, and are the fastest way to spot which URLs are at risk of failing Google's Core Web Vitals expectations or losing rankings to faster competitors.
What it measures
- URL — the tracked landing page.
- Performance score (mobile / desktop) — the headline 0–100 Lighthouse number, weighted from LCP, CLS, INP / TBT, FCP and Speed Index.
- Capture date — when the latest measurement ran.
How we compute it
- Each tracked URL is run through the PageSpeed Insights API on a recurring schedule, once for a mobile profile and once for desktop.
- The API returns a Lighthouse audit; we capture the headline performance score plus the underlying field-data Core Web Vitals where available.
- The latest run per URL × device is shown in this overview; older runs are visible in PSI History.
Interpreting the score
- 90–100 — fast. Treat as healthy; small regressions still worth watching.
- 50–89 — needs improvement. Mid-band; competitive sites usually live here.
- 0–49 — slow. High risk of ranking dampening on speed-sensitive queries and of failing the field-data Core Web Vitals thresholds.
Scenarios you'll see
Almost universal. Mobile profiles use slower CPU and network; gaps of 20–40 points are normal. Focus optimisation on mobile.
A URL whose score dropped 20+ points since the last run. Almost always a recent deployment introduced a heavy script or render-blocking asset. Diagnose with the PSI report directly on google.com.
Score capped at 60–70 by LCP. Optimisation: next-gen image formats, preload the LCP image, lazy-load the rest, set explicit width/height.
CTAs, chat widgets, analytics, A/B-test scripts capping the score. Audit your tag manager — most sites can remove 30–50% of third-party JS.
Score climbed 15+ points after a release. Cross-check Rising Pages a few weeks later — speed wins often translate into ranking wins on competitive queries.
Score below 50 with the corresponding LCP/CLS/INP failing on field data; a known Google ranking signal. Prioritise immediately.
What to do with it
- Sort by mobile score ascending — the worst pages are the highest-ranking-impact pages.
- For each problem URL, run PSI against the live URL on google.com to see the specific opportunities and diagnostics.
- Re-check after a release; PSI Overview is your post-deploy regression check.
Caveats & limits
- The PSI score is computed against a simulated network and CPU profile; it can vary 5–10 points run-to-run. Read trends, not single readings.
- Lab data ≠ field data. The score is a proxy; the Core Web Vitals Distribution report shows what real users actually experience.
Related reports
- Core Web Vitals Distribution — field-data LCP/CLS/INP across your URLs.
- PSI History — historical runs for each URL.
- Falling Pages — to confirm whether a speed regression translated into ranking loss.