PageSpeed Score Explained: What It Means and How to Improve It
Google's PageSpeed score is one number between 0 and 100 — but what's actually behind it? This guide breaks down what the score measures, why it matters for SEO, and the most impactful ways to improve it.
What PageSpeed / Lighthouse actually measures
When you run PageSpeed Insights on any URL, you're running Google's Lighthouse tool — an open-source automated auditing engine. Lighthouse measures four separate categories, each scored 0–100:
- Performance — how fast the page loads and becomes interactive
- Accessibility — whether people with disabilities can use the page
- Best Practices — security, modern web standards, deprecated APIs
- SEO — crawlability, meta tags, mobile-friendliness
Most people focus on the Performance score, since it directly affects user experience and is a confirmed Google ranking signal. The "PageSpeed score" colloquially refers to this Performance number.
The scoring system — why 90+ matters
Lighthouse uses a logarithmic scale for scoring. The thresholds are:
- 0–49 (red) — poor performance, likely affecting users and rankings significantly
- 50–89 (orange) — needs improvement
- 90–100 (green) — good
The logarithmic scale means it gets progressively harder to improve as you approach 100. Going from 30 to 60 is much easier than going from 85 to 95. For most websites, targeting 85+ on mobile is a practical and meaningful goal; 90+ puts you ahead of the vast majority of sites.
An important nuance: Lighthouse tests with lab conditions (a simulated device in a specific network environment). Google's Core Web Vitals data, by contrast, comes from real users via the Chrome User Experience Report (CrUX). A high Lighthouse score doesn't guarantee a good field data experience — but it's a very strong indicator.
Core Web Vitals: LCP, FCP, CLS explained simply
Core Web Vitals are the most important sub-metrics within the Performance score. They measure real user experience directly:
- LCP (Largest Contentful Paint) — how long until the largest visible element (usually a hero image or main heading) is fully loaded. Good: under 2.5s.
- FCP (First Contentful Paint) — when the first piece of content appears on screen. Good: under 1.8s.
- CLS (Cumulative Layout Shift) — measures unexpected layout shifts — elements jumping around as the page loads. Good: under 0.1.
- INP (Interaction to Next Paint) — measures responsiveness: how quickly the page responds to clicks and taps. Replaced FID in 2024. Good: under 200ms.
Most common reasons for a low PageSpeed score
The majority of poor scores come from a small set of recurring issues:
- Large, unoptimized images — a 3MB JPEG where a 150KB WebP would do the same job
- Render-blocking JavaScript — scripts in
<head>that delay page rendering - No browser caching — static assets without appropriate cache headers are re-downloaded on every visit
- Unused CSS and JavaScript — loading entire libraries when only a fraction is needed
- No CDN — serving assets from a single server far from many of your users
- Slow server response (TTFB) — a database that takes 2s to respond before the page even starts loading
Quick wins vs. deeper fixes
Quick wins (usually achievable without code changes):
- Convert images to WebP format and compress them — often the single biggest gain
- Add
loading="lazy"to images below the fold - Enable GZIP/Brotli compression on your server
- Set long cache-control headers for static assets
Deeper fixes (require development work):
- Move to a CDN for global asset delivery
- Defer or async-load non-critical JavaScript
- Implement proper font loading strategy (font-display: swap)
- Optimize database queries to reduce TTFB
- Consider server-side rendering or static generation for complex single-page apps
Track your PageSpeed score over time with Sitekeeper
Sitekeeper runs Lighthouse checks daily and shows you score trends so you can see whether your changes are actually improving performance. 30-day free trial.
Start free trial →Frequently asked questions
Is PageSpeed score a direct Google ranking factor?
Core Web Vitals (which contribute heavily to the Performance score) are confirmed Google ranking signals introduced in 2021. The exact weight varies, but poor performance — especially on mobile — can reduce your rankings relative to competitors with faster pages.
Why does my PageSpeed score vary between runs?
Lighthouse tests in a simulated environment, but network conditions, server load and the order in which resources load can vary slightly between runs. A 3–5 point variation is normal. For more stable measurements, take an average of several runs or monitor trends over time.
Should I focus on mobile or desktop PageSpeed score?
Mobile. Google uses mobile-first indexing, meaning it crawls and ranks based on the mobile version of your site. Mobile scores are also typically 20–30 points lower than desktop due to the simulated slower device. Improving mobile performance usually improves desktop too.
What is a realistic PageSpeed target for a WordPress site?
With proper optimization (good hosting, image optimization, caching plugin, minimal plugins), most WordPress sites can reach 75–90 on mobile. Scores above 90 are achievable but often require more significant technical investment.
How often should I check my PageSpeed score?
Automated daily monitoring is ideal — it catches regressions immediately after deployments, plugin updates or content changes. Checking manually once a month is better than never, but it's easy to miss a slow gradual decline.