Speed & performance · Explainer
What Is a Good PageSpeed Score for WordPress?
Short answer
A good PageSpeed score is 90 to 100. That is the green band in Lighthouse, the tool behind PageSpeed Insights. A good WordPress site also passes Core Web Vitals in real-user data, with LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
Key takeaways
- A PageSpeed score of 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor.
- Passing Core Web Vitals in real-user data matters more than a single lab score.
- LCP should be 2.5 seconds or less, INP 200 milliseconds or less and CLS 0.1 or less.
- Google judges Core Web Vitals at the 75th percentile, so 3 in 4 visits must meet each limit.
- A score of 100 is not required, and Google calls a perfect score extremely challenging.
- Mobile scores often run lower because the mobile test simulates a mid-tier phone on a mobile network.
What is a good PageSpeed score for WordPress?
A good PageSpeed score is 90 to 100, and a good WordPress site also passes Core Web Vitals in real-user data.
Google sorts the 0 to 100 Lighthouse performance score into 3 bands. Scores of 90 to 100 are good and shown in green, 50 to 89 need improvement and are shown in orange, and 0 to 49 are poor and shown in red, according to Chrome's Lighthouse scoring page.
That score comes from one lab test, so it is only part of the answer. A page can score 90 in the lab and still fail Core Web Vitals for real visitors, so check both parts of the report before you judge a site.
For a quick sense of the load time behind the score, see how fast a WordPress site should load.
What does the 0-100 score actually measure?
The 0-100 score is a weighted mix of 5 lab metrics from one simulated page load.
Lighthouse runs the page in a controlled setting and turns each raw timing into a score from 0 to 100. It then blends those metric scores into one performance score, using weights set for each Lighthouse version.
In Lighthouse 10, the weights are Total Blocking Time at 30%, Largest Contentful Paint at 25%, Cumulative Layout Shift at 25%, First Contentful Paint at 10% and Speed Index at 10%, as listed on Chrome's Lighthouse scoring page.
That weighting explains why one slow metric can pull the whole score down. Total Blocking Time alone counts for almost a third of the score, so heavy JavaScript during load has a large effect.
| Metric | Weight in Lighthouse 10 | What it measures |
|---|---|---|
| Total Blocking Time | 30% | Time the page is too busy to respond while loading |
| Largest Contentful Paint | 25% | When the main content appears |
| Cumulative Layout Shift | 25% | How much the layout moves while loading |
| First Contentful Paint | 10% | When anything first appears on screen |
| Speed Index | 10% | How fast the visible page fills in |
Lighthouse maps each raw value onto a curve built from HTTP Archive data. The 25th percentile of that data becomes a score of 50, and the 8th percentile becomes a score of 90, according to the same Chrome page.
As an example, Chrome says an LCP of about 1,220 milliseconds maps to a score of 99. That curve also explains why gains get harder near the top.
What are the good limits for LCP, INP and CLS?
LCP should be 2.5 seconds or less, INP 200 milliseconds or less and CLS 0.1 or less.
These 3 limits are the Core Web Vitals good thresholds. Google judges each one at the 75th percentile of page loads, split across mobile and desktop, according to web.dev.
The 75th percentile means 3 in 4 visits must meet the limit. An average can hide slow visits, but the 75th percentile keeps the slowest quarter in view.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less | Over 2.5 to 4.0 seconds | Over 4.0 seconds |
| Interaction to Next Paint (INP) | 200 milliseconds or less | Over 200 to 500 milliseconds | Over 500 milliseconds |
| Cumulative Layout Shift (CLS) | 0.1 or less | Over 0.1 to 0.25 | Over 0.25 |
| First Contentful Paint (FCP) | 1.8 seconds or less | Over 1.8 to 3.0 seconds | Over 3.0 seconds |
| Time to First Byte (TTFB) | 800 milliseconds or less | Over 800 to 1,800 milliseconds | Over 1,800 milliseconds |
The limits in that table come from PageSpeed Insights documentation. FCP and TTFB are supporting metrics, not Core Web Vitals, and TTFB is still listed as experimental.
A page passes the Core Web Vitals assessment only when all 3 metrics are good at the 75th percentile. If INP has too little data, the page can pass on LCP and CLS alone, according to the same PageSpeed Insights page.
To work on the loading metric first, read how to improve Largest Contentful Paint in WordPress.
How is the score different from Core Web Vitals?
The score is one lab test, while Core Web Vitals come from real Chrome users over 28 days.
PageSpeed Insights shows both kinds of data in one report. The top section, called real-user experience data, comes from the Chrome User Experience Report, known as CrUX, according to PageSpeed Insights documentation.
The lower section is lab data from Lighthouse. It simulates a single page load in a controlled setting and gives the 0 to 100 score, plus scores for accessibility, best practices and SEO.
Field data covers the previous 28 days and is updated daily in PageSpeed Insights. Lab data reflects only the moment of that one test run.
That split matters because the two can disagree. A page may score well in the lab on a fast connection and still be slow for visitors on older phones or weak networks.
Google states the point plainly in its PageSpeed Insights FAQ: any green score of 90 or more is good, but good lab data does not necessarily mean real-user experiences are also good. For a full plan, see how to pass Core Web Vitals in WordPress.
Why does your mobile score matter more than desktop?
Your mobile score matters more because the mobile test is stricter and Google judges Core Web Vitals on mobile and desktop separately.
PageSpeed Insights tests mobile and desktop separately, and the two scores use different curves. Lighthouse has used separate desktop scoring curves since version 6, after mobile-based curves made desktop scores look too high.
The mobile lab test simulates a mid-tier Moto G4 device on a mobile network. The desktop test uses an emulated desktop with a wired connection, according to PageSpeed Insights documentation.
Google Search Central says it highly recommends good Core Web Vitals for success with Search, and it lists the same LCP, INP and CLS limits for both device types, as shown on Google Search Central. Read does page speed affect SEO for how that ranking link works.
How do you check your PageSpeed score on WordPress?
Open PageSpeed Insights, enter the full page URL, and run the test for mobile and then desktop.
The tool is free and needs no sign-up. It first shows the real-user section at the top, if your page has enough CrUX data, and then the lab section below it.
Follow these steps for a fair reading:
- Test the exact page you care about, not only the home page, because each page has its own score.
- Run the test 2 or 3 times and note the range, not a single number.
- Read the Core Web Vitals assessment first, then the 0 to 100 score.
- Open the Opportunities list in the lab section to see what slows that page.
A new page or a page with few visitors may show no field data at all. PageSpeed Insights then falls back to origin-level data for the whole site, and if that is also too thin, it shows no real-user data, according to PageSpeed Insights documentation.
Search Console gives a second view for a whole site. Its Core Web Vitals report groups similar pages and shows which groups pass or fail, so you can see if a problem affects one template or many pages.
What score should different types of WordPress sites aim for?
Aim for 90 or more on mobile, and pass all 3 Core Web Vitals, whatever type of site you run.
That target is the same for a blog, a business site and a shop, because Google uses the same bands for every page. The work to reach it differs, since a shop page often loads more scripts and images than a plain post.
A score of 50 to 89 means the page needs improvement, not that it is broken. Fix the largest items in the Opportunities list first, then retest and look for a higher band, not a perfect number.
The 2025 Web Almanac shows how common each result is. In July 2025 data, 48% of mobile sites had good Core Web Vitals, up from 44% in 2024 and 36% in 2023, while desktop reached 56% in 2025, according to the Web Almanac 2025 performance chapter.
That same chapter found 51% of the 1,000 most popular mobile sites had good Core Web Vitals.
Why does your score change between runs?
Your score changes because network routing, ads, tests and device load change, even when your page does not.
Chrome lists common causes: A/B tests, changes in ads, internet traffic routing, testing on different devices, browser extensions that add JavaScript, and antivirus software, as noted on Chrome's Lighthouse scoring page.
PageSpeed Insights also runs in a Google data centre that can be in North America, Europe or Asia. The location can vary, and that changes the network path to your server.
For that reason, treat the score as a range, not a fixed grade. Chrome suggests thinking of site speed as a spread of scores, rather than a single number.
What should you fix first when your score is low?
Fix the metric with the largest weight and the worst value first, usually Total Blocking Time or Largest Contentful Paint.
Start with the Opportunities list in the lab report. It ranks fixes by the time each one could save, so work from the top down.
Common first fixes for WordPress are:
- Remove or delay JavaScript that blocks the page, such as chat widgets and extra trackers.
- Shrink and serve images at the size shown on the page.
- Use caching and a content delivery network so repeat visits load faster.
- Check the host if Time to First Byte stays above 800 milliseconds.
For a step-by-step plan, see how to speed up WordPress.
If the server is the slow part, the host is the fix, not another plugin. Read does hosting affect WordPress speed before you change hosts.
Do not chase 100. Chrome says a perfect score is extremely challenging and not expected, and moving from 99 to 100 needs about the same improvement as moving from 90 to 94, according to Chrome's Lighthouse scoring page.
What mistakes should you avoid?
Do not chase a perfect 100, do not trust one run, and do not judge a page by its desktop score alone.
These errors waste time on many WordPress sites:
- Treating the lab score as a ranking factor, when Google ranks on field Core Web Vitals.
- Testing only the home page, when posts, product pages and checkout pages often score lower.
- Adding more speed plugins to fix a slow host, which adds scripts instead of removing the cause.
- Judging a fix from one test run, when scores move between runs.
- Still using First Input Delay, which INP replaced as the responsiveness Core Web Vital.
INP became the responsiveness metric in place of First Input Delay, and web.dev notes that INP moved from experimental to pending status in 2023 before that change, as described on web.dev.
Set a simple routine instead. Test the main page types once a month, note the mobile score and the 3 Core Web Vitals, fix the top opportunity, and retest after the change.
Frequently asked questions
Is a PageSpeed score of 80 good for WordPress?
A score of 80 is in the needs improvement band, which runs from 50 to 89, so it is not rated good. It is a usable result for a busy WordPress page, but it leaves room to improve. Check the Core Web Vitals first, because a page at 80 that passes them in real-user data serves visitors better than a page at 95 that fails them.
Do I need a PageSpeed score of 100?
No. Google rates 90 to 100 as good, and Chrome says a perfect 100 is extremely challenging and not expected. Moving from 99 to 100 needs about the same improvement as moving from 90 to 94. Aim for 90 or more and for good Core Web Vitals, then spend your time on content and other fixes that help visitors more.
Why is my mobile PageSpeed score lower than desktop?
The mobile test simulates a mid-tier phone on a mobile network, while the desktop test uses an emulated desktop with a wired connection. Mobile also uses stricter scoring curves. The same page therefore loads slower in the mobile test, and heavy scripts and large images hurt the mobile score more than the desktop score.
Does the PageSpeed score itself affect Google rankings?
No, the 0 to 100 lab score is not a ranking factor on its own. Google uses Core Web Vitals from real users in its ranking systems, and it highly recommends good results for success with Search. A high lab score often goes with good Core Web Vitals, but only the field result counts for that ranking signal.
How often should I check my PageSpeed score?
Check the main page types once a month, and again after any theme change, plugin change or host change. Run each test 2 or 3 times and note the range. For a fuller picture, also watch the Core Web Vitals report in Search Console, which uses 28 days of real-user data and updates as visitors use the site.
What is a good PageSpeed score for a WooCommerce store?
The same bands apply: 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor. A shop page often scores lower than a blog post because it loads more scripts, images and cart code. Aim for 90 or more on the main shop and product pages, and pass LCP, INP and CLS in real-user data before you chase a perfect score.
Sources
- Lighthouse performance scoring Chrome for Developers
- Web Vitals web.dev
- About PageSpeed Insights Google for Developers
- Understanding Core Web Vitals and Google search results Google Search Central
- Performance | 2025 | The Web Almanac by HTTP Archive HTTP Archive
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
