A good PageSpeed score is 90 or above, which Google marks green. Scores from 50 to 89 need improvement, and anything from 0 to 49 is poor. Still, the score is only a summary. Real Core Web Vitals (LCP, INP and CLS) tell you more about how visitors experience your pages. You can check yours with our free website speed test.
Key takeaways
- A PageSpeed (Lighthouse) performance score of 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor (Google).
- You do not need a perfect 100. A steady green score on mobile is a strong target.
- Mobile scores are usually lower than desktop scores because the test simulates a slower device and network.
- Core Web Vitals from real visitors matter more than the lab score.
What is a PageSpeed score?
A PageSpeed score is a number from 0 to 100 that Google PageSpeed Insights gives a page after running a Lighthouse test. It summarizes how fast the page loads and becomes usable in a controlled lab test. The score is calculated from several speed metrics, each with its own weight.
The tool also shows a separate section of field data, which comes from real Chrome users over the previous 28 days when enough data exists. Lab data and field data answer different questions, so read both.
What is a good PageSpeed score?
A good PageSpeed score is between 90 and 100. Google groups Lighthouse performance scores into three bands, shown in the table below, and uses the same colors in the report.
| Score | Rating | Color | What to do |
|---|---|---|---|
| 90 to 100 | Good | Green | Keep it stable and re-test after changes |
| 50 to 89 | Needs improvement | Orange | Fix the biggest issues first |
| 0 to 49 | Poor | Red | Treat speed as a priority |
A perfect 100 is rare on real sites with ads, analytics and chat widgets. A green score on mobile is a realistic and healthy goal.
What is a good PageSpeed score for mobile?
A good mobile PageSpeed score is also 90 or above, but it is harder to reach. The mobile test simulates a mid-range phone on a slower connection, so the same page scores lower than on desktop. Because Google uses mobile-first indexing, mobile is the score to prioritize.
If your mobile score is between 70 and 89, you are close. Small fixes such as image compression and caching often move a page into the green zone.
What is a good PageSpeed score for desktop?
A good desktop score is 90 or above, and most well-built sites reach it more easily than on mobile. Desktop tests use a faster simulated connection and a stronger processor. A high desktop score with a low mobile score usually means the page is too heavy for slower devices.
How is the PageSpeed score calculated?
The score is a weighted average of five Lighthouse metrics. Current Lighthouse versions weight them as shown below, so some metrics move your score far more than others.
| Metric | Weight | What it measures |
|---|---|---|
| Total Blocking Time (TBT) | 30% | How long the page is unresponsive while loading |
| Largest Contentful Paint (LCP) | 25% | When the main content appears |
| Cumulative Layout Shift (CLS) | 25% | How much the layout jumps around |
| First Contentful Paint (FCP) | 10% | When the first content appears |
| Speed Index | 10% | How quickly the page fills in visually |
TBT, LCP and CLS together make up 80% of the score, so improving them gives the biggest gain. Interaction to Next Paint (INP) is a Core Web Vital measured in the field, and TBT is its closest lab metric.
Is the PageSpeed score the same as Core Web Vitals?
No. The PageSpeed score is a lab-based summary, while Core Web Vitals are measured from real visits. A page passes Core Web Vitals when its LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, judged at the 75th percentile of visits (Google, web.dev).
A page can have a green score and still fail Core Web Vitals in the field, or the other way around. When the two disagree, trust the field data, because it reflects real visitors.
Does PageSpeed score affect SEO?
It affects SEO indirectly. Google uses page experience signals, including Core Web Vitals, in its ranking systems, but relevance and content quality usually matter more. The score itself is not a ranking factor. It is a diagnostic tool that helps you find the issues that are.
Why is my PageSpeed score low?
The most common reasons for a low score are large images, render-blocking CSS and JavaScript, too many third-party scripts and slow server response. Heavy page layouts add to the problem, including image-rich designs that follow many modern web design trends.
- Uncompressed or oversized images
- Unused JavaScript and CSS from themes and plugins
- Ads, chat widgets and tracking scripts
- Slow hosting or no caching
- Images and embeds without reserved space
How do you improve your PageSpeed score?
To improve your PageSpeed score, test the page, fix the largest issue in the report, then test again. Repeat until the score is green and your Core Web Vitals pass.
- Run the page through our free page speed checker and note the top opportunities.
- Compress and resize images, and use modern formats such as WebP.
- Enable caching and compression.
- Remove or defer unused JavaScript and CSS.
- Cut third-party scripts you do not need.
- Re-test two or three times and compare the pattern, not a single run.
For the full step-by-step list, read our guide on how to improve website speed.
Frequently asked questions
Is 100 the only good PageSpeed score?
No. Google treats 90 to 100 as good, so you do not need a perfect 100. Chasing the last few points often takes a lot of effort for little visible benefit. Focus on passing Core Web Vitals and on a fast experience for real visitors.
Is a PageSpeed score of 70 good?
A score of 70 falls in the needs improvement range, which is 50 to 89. It is not bad, but it is not yet green. Fixing the top two or three issues in the report can often lift it above 90.
Why is my mobile score lower than desktop?
The mobile test simulates a slower network and a less powerful processor, so the same page loads more slowly in the test. This is normal. Fix mobile first, because improvements there usually raise the desktop score too.
Why does my PageSpeed score change every time?
Server response, network conditions and background tasks vary between runs, so small changes of a few points are normal. Run the test two or three times and judge the overall pattern.
What matters more, score or Core Web Vitals?
Core Web Vitals matter more because they come from real visitors and are the metrics Google uses for page experience. Use the score as a quick health check and the field data as the real measure.
How often should I check my PageSpeed score?
Check your key pages after every theme, plugin or design change, and at least once a month. Regular checks help you catch problems such as a new script or an oversized image before visitors notice.
Conclusion
A good PageSpeed score is 90 or above, but the best goal is a fast page that passes Core Web Vitals for real visitors. Check your mobile score first, fix the biggest issues one at a time and re-test after each change. Start now with our free website speed test, then follow the steps in our website speed guide.
