What Is a Good PageSpeed Score? (And How to Fix a Bad One)

Introduction

You run PageSpeed Insights on your site and get a score of 54. Is that good? Bad? Should you panic?

Most website owners have no idea what their PageSpeed score actually means for their Google rankings — or what score they genuinely need. Some chase a perfect 100. Others ignore it entirely. Both approaches are wrong.

In this guide you will learn exactly what each score range means, what score actually matters for SEO, and the four fastest fixes to improve a low score. No technical jargon — just clear, actionable steps.

What Do PageSpeed Score Ranges Mean?

PageSpeed Insights scores every page from 0 to 100 using Google's Lighthouse engine. These ranges apply separately to mobile and desktop.

Your desktop score is almost always higher than your mobile score because desktop devices are faster and on stronger connections. Learn why in our guide → Why Your Mobile PageSpeed Score Is Always Lower Than Desktop

What Score Do You Actually Need for SEO?

Here is the honest answer most articles avoid: Google does not use your PageSpeed score as a ranking signal.

What Google uses is your Core Web Vitals field data — LCP, INP, and CLS measured from real visitors. A page can score 61 on PageSpeed Insights and still pass all three Core Web Vitals. That page ranks better than a competitor with a score of 88 that fails Core Web Vitals.

That said, score ranges are a useful proxy:

The real target: Pass Core Web Vitals. Use the score as a guide, not a goal.

For the full explanation of how page speed connects to rankings → Does Page Speed Actually Affect Google Rankings in 2026?

For official Core Web Vitals thresholds → web.dev/articles/vitals

Mobile vs Desktop: Which Score Matters More?

Mobile — every time.

Google uses mobile-first indexing. This means it crawls and evaluates the mobile version of your site for rankings. Your desktop score is nearly irrelevant for SEO purposes.

PageSpeed Insights tests mobile by simulating a mid-range Android device on a 4G connection. This is intentionally harder than desktop testing. A score of 70 on mobile is solid. A score of 90+ on mobile is excellent.

Do not be discouraged by a low mobile score. Most sites score 20–40 points lower on mobile than desktop. Focus all your optimisation effort on the mobile score first.

Why Your Score Varies Every Time You Test

You run the same URL three times and get 61, 58, and 67. This is normal — here is why.

PageSpeed Insights runs a Lighthouse lab test from Google's servers. Network conditions, server load at the moment of testing, and third-party script timing all affect results. Scores naturally vary by 5–15 points between tests.

What to do: Run the test three times and take the middle result. Or better — check your Core Web Vitals field data in Google Search Console, which averages 28 days of real user data and does not fluctuate between tests.

Learn how to read your Google Search Console data → 5 Google Search Console Reports That Explain a Traffic Drop

How to Fix a Bad PageSpeed Score

The four fixes below address the most common causes of low PageSpeed scores. Start with Fix 1 — it has the highest impact for the least effort on most sites.

Fix 1: Optimise Your Images

Unoptimised images are the single most common cause of a poor PageSpeed score. A single hero image saved as a 3MB JPEG can drop your score by 20–30 points alone.

What to do: (1) Convert all images to WebP format — typically 30–50% smaller than JPEG at the same quality. (2) Compress before uploading using squoosh.app — free, no software needed. (3) Set explicit width and height on every image — prevents layout shift (CLS). (4) Add loading="lazy" to images below the fold — defers loading until needed.

Learn the full image optimisation process → How WebP Images Improve Your PageSpeed Score and SEO

See how images affect your Core Web Vitals → Your Images Are Probably Killing Your PageSpeed Score

Fix 2: Remove Render-Blocking Resources

Render-blocking resources are CSS and JavaScript files that force the browser to stop and load them before showing anything on screen. Every second the browser waits = slower LCP = lower score.

What to do: Move non-critical CSS to load asynchronously. Add defer or async attribute to non-essential JavaScript files. Remove unused CSS — most WordPress themes load entire stylesheets when only 10% is used. For WordPress users: plugins like WP Rocket or Asset CleanUp handle this automatically without touching code.

Fix 3: Reduce Unused JavaScript

PageSpeed Insights flags unused JavaScript as a major opportunity on most sites. Unused JS loads in the browser, takes up memory, and slows page response — directly hurting your INP score.

What to do: In WordPress, deactivate plugins you are not actively using — every plugin adds JavaScript. Use a performance plugin to defer or delay JS until user interaction. Check the Coverage tab in Chrome DevTools to see exactly which scripts have unused code.

Learn how WordPress plugins impact your performance → How to Find Which WordPress Plugins Are Slowing Your Site

Fix 4: Improve Server Response Time (TTFB)

Time to First Byte (TTFB) is how long your server takes to respond after a browser requests your page. A slow TTFB delays everything — your LCP cannot start until the server responds. Good TTFB is under 600ms. Poor TTFB is over 1800ms.

What to do: Enable server-side caching — most hosting providers offer this in one click. Use a CDN (Cloudflare free tier works well) — serves pages from servers nearest to your visitor. Upgrade your hosting if on shared hosting — shared hosting TTFB is often 1–3 seconds.

For the official PageSpeed Insights documentation → developers.google.com/speed/docs/insights/v5/about

FAQ

Conclusion

A good PageSpeed score in 2026 is not about hitting 100 — it is about passing Core Web Vitals for your real visitors. If your score is above 75 on mobile and your LCP, INP, and CLS are all in the green, your site is performing well for SEO purposes.

If your score is under 50, start with images. Compress them, convert to WebP, and set explicit dimensions. That single fix resolves the most common PageSpeed failures faster than any other change.

Use PageSpeed Insights to identify what to fix. Use Google Search Console's Core Web Vitals report to track real improvement over time. And remember — a competitor with a score of 65 who passes Core Web Vitals will outrank you at 88 if you are failing them.