You ran your WordPress site through Google PageSpeed Insights and got a number. Now you're staring at it wondering: is this good? Is this bad? Does it even matter?
The answers are: it depends, probably bad, and yes — it matters more than most site owners realise.
This post explains exactly what the score means, what a genuinely good score looks like, how it affects your SEO and conversions, and — most importantly — why most WordPress sites never reach it.
What Is Google PageSpeed Insights?
Google PageSpeed Insights (PSI) is a free tool from Google that analyses the performance of your website and gives it a score from 0 to 100. It tests both your mobile and desktop versions separately.
Under the hood, it combines two types of data:
- Lab data — a simulated test run on your page by Google's Lighthouse tool, using a mid-tier device on a typical mobile network
- Field data — real-world measurements collected from Chrome users who have actually visited your site over the past 28 days
The score you see at the top is based on the lab data. But for SEO purposes, the field data — specifically your Core Web Vitals — is what actually affects your Google rankings.
What Do the Score Ranges Mean?
According to Google, the PageSpeed score breaks down into three ranges:
| Score | Rating | What it means |
|---|---|---|
| 0–49 | Poor (red) | Slow. Google considers this a problem. You are likely being penalised in rankings. |
| 50–89 | Needs Improvement (orange) | Average. Neither penalised nor rewarded. You won't stand out. |
| 90–100 | Good (green) | Fast. Google considers this acceptable. You have a performance advantage. |
The key word in the top band is good — not perfect. Google doesn't require a score of 100. Anything above 90 clears the bar.
Desktop vs Mobile — Why They’re Different
You'll notice your mobile score is almost always lower than your desktop score. This is intentional. Google simulates mobile testing on a mid-tier device with a slower network connection, because that represents the average real-world experience of a mobile visitor.
This matters because Google uses mobile-first indexing — meaning your mobile performance is the one that counts for rankings, not desktop. A stunning desktop score with a terrible mobile score does nothing for you in search results.
What Score Should You Actually Aim For?
90+ on desktop, 80+ on mobile is a realistic and meaningful target for most WordPress sites.
Here's some context on where most sites actually land:
- The average PageSpeed score across thousands of websites studied sits around 40–50 — firmly in the "poor" range
- Research on the #1 Google search result across 1,000 queries found an average mobile score of just 40 and a desktop score of 60 — which shows that content and authority can partially compensate, but speed still matters
- According to the 2025 Web Almanac, only 48% of mobile pages pass all three Core Web Vitals — meaning more than half the web is failing on mobile
- Only 34% of the top 100 websites by traffic pass Core Web Vitals
The point: most of the internet is slow. If your site scores 80+ on mobile, you're already ahead of the majority. If you hit 90+, you're in the top tier.
What Does PageSpeed Actually Measure?
The score is calculated from five weighted metrics, all measured by Lighthouse:
Largest Contentful Paint (LCP) — 25% of score How long until the biggest visible element (usually your hero image or main headline) has loaded. Google's threshold for "good" is under 2.5 seconds.
Total Blocking Time (TBT) — 30% of score How long the page is unresponsive to clicks and input while loading. This is the biggest single contributor to your score and is heavily influenced by JavaScript loading on the main thread.
Cumulative Layout Shift (CLS) — 15% of score How much the page visually jumps around as it loads — elements shifting position, content moving. Good is under 0.1. This is the most commonly passed metric.
First Contentful Paint (FCP) — 10% of score How long before any content appears at all — the moment a visitor sees something rather than a blank screen.
Speed Index — 10% of score How quickly the page visually fills in overall during loading.
One important nuance: only real-user Core Web Vitals data affects your Google rankings — not the lab-based PageSpeed score itself. Your lab score is a useful diagnostic tool. Your field data (LCP, INP, CLS measured on real visitors) is what Google actually uses as a ranking signal.
How Does PageSpeed Affect SEO?
Google confirmed in March 2024 that Core Web Vitals are used by its ranking systems. The honest picture, according to Google's own John Mueller: they are "more than a tiebreaker but less important than content relevance."
In practical terms:
- A poor score won't tank a site with great content and strong backlinks overnight
- But between two pages of similar quality and relevance, the faster one ranks higher
- Fixing a failing score (under 50) to a passing score (90+) has a measurable positive impact
- One analysis found that slow domains (failing Core Web Vitals) ranked 3.7 percentage points lower in search visibility on average than fast domains
The SEO benefit alone makes it worth pursuing. But the conversion impact is just as significant.
How Does PageSpeed Affect Conversions and Revenue?
This is where it gets concrete. The data is unambiguous:
- Sites that load in 1 second have conversion rates nearly 3x higher than sites loading in 5 seconds
- A 1-second delay reduces conversions by an average of 2.11% per second
- When Vodafone improved their LCP by 31%, they saw 8% more sales
- When Rakuten optimised Core Web Vitals, revenue per visitor increased by 53% and conversion rate by 33%
- Nearly 70% of consumers say a site's loading speed directly affects their willingness to buy
For a WooCommerce store, the maths are brutal. If you're getting 500 visitors a month and converting at 2%, that's 10 sales. Speed up the site and push conversions to 3%, that's 15 sales — from the same traffic, with zero extra marketing spend.
Why Most WordPress Sites Never Reach a Good Score
Here's the part most "how to improve your PageSpeed score" articles skip over.
You can install every caching plugin, compress every image, and switch to the lightest theme available — and still sit at a score of 45. Not because you haven't done the work, but because the foundation is wrong.
The single biggest factor in your PageSpeed score is your hosting.
Specifically: your Time to First Byte (TTFB) — the time before your server even starts sending data to the visitor's browser. Google recommends a TTFB under 200ms. Most budget shared hosting delivers 600ms to over 1,000ms.
Everything loads on top of TTFB. If your server takes 800ms to respond before a single byte has been sent, you've already burned most of your LCP budget before the page has done anything. No plugin fixes that.
Beyond TTFB, budget hosting typically means:
- No server-level caching — every page load hits the database and rebuilds from scratch
- No CDN included — files travel the full distance from server to visitor for every request
- Shared resources — your site competes with hundreds of others on the same server
- Outdated PHP versions — older PHP runs slower, and many budget hosts are slow to update
These are infrastructure problems. The solution is infrastructure — not a plugin.
What Score Can You Realistically Achieve on Good Hosting?
On a properly configured hosting environment with server-level caching and a CDN, a typical WordPress site can realistically achieve:
- 85–95 on desktop without aggressive optimisation
- 70–85 on mobile depending on theme and image optimisation
- 90+ on both with a lightweight theme and properly optimised images
The same site that scores 35 on budget shared hosting can score 80+ after migrating to faster infrastructure — with no changes to the theme, no plugin swaps, no code changes. The server was the problem.
How to Check Your Score Right Now
Go to pagespeed.web.dev, enter your URL, and run the test. Check both mobile and desktop.
Look specifically at:
- The overall score — are you in the red, orange, or green?
- LCP — is it under 2.5 seconds?
- TTFB — if PageSpeed flags "Reduce initial server response time," your hosting is the bottleneck
- The field data section — this is what Google actually uses for rankings
If you see "Reduce initial server response time" as a recommendation, that's not something you fix with a plugin. That's a hosting problem.
The Bottom Line
A good PageSpeed score is 90+ on desktop and 80+ on mobile. Most WordPress sites never get there — not because the owners haven't tried, but because budget hosting puts a ceiling on what's possible regardless of how much you optimise.
Fix the hosting first. Everything else follows.
At HigherHost, every plan includes server-level caching and a CDN configured out of the box. Migration is free and takes less than an hour. If your site isn't noticeably faster within 30 days, you pay nothing.