Google PageSpeed Insights scores your WordPress site on performance and identifies the specific issues holding it back. It measures Core Web Vitals — the speed and user experience signals Google uses as ranking factors — and shows you both lab data from a simulated test and field data from real Chrome users visiting your site.
Understanding what the scores mean, which recommendations to act on first, and which ones to ignore is more useful than simply chasing a high number. A site scoring 65 with good field data often outranks a site scoring 95 with poor real-world performance.
What PageSpeed Insights Actually Measures
PageSpeed Insights uses Lighthouse, Google’s open-source performance auditing tool, to generate lab scores. It also pulls field data from the Chrome User Experience Report (CrUX), which aggregates real performance data from Chrome users who have visited your URL.
The field data is what actually matters for SEO. Google’s Core Web Vitals assessment in PageSpeed Insights and Search Console is based on field data, not lab scores. A site that scores 55 in Lighthouse but has good field data (because real users are mostly on fast connections near the CDN edge) can still pass Core Web Vitals. Conversely, a site scoring 90 in the lab but with slow field data has a real performance problem.
| Metric | What it measures | Good threshold |
| LCP (Largest Contentful Paint) | When main content loads | Under 2.5 seconds |
| INP (Interaction to Next Paint) | Responsiveness to interactions | Under 200ms |
| CLS (Cumulative Layout Shift) | Visual stability | Under 0.1 |
| TTFB (Time to First Byte) | Server response time | Under 800ms |
How to Run a PageSpeed Insights Test on Your WordPress Site
Go to pagespeed.web.dev and enter your URL. Run the test for both mobile and desktop. Mobile is more important: Google uses mobile-first indexing, so your mobile Core Web Vitals score is what affects rankings.
Test at least three pages: your homepage, a representative blog post or content page, and a key landing page. Homepage performance does not represent the whole site. A homepage that loads quickly because it has little content can mask performance problems on heavier content pages that get more organic traffic.
Run each test more than once if the score varies significantly between runs. PageSpeed Insights tests can vary due to server load, CDN warming, and network conditions. Three tests and averaging the scores gives a more reliable baseline than a single result.
Which Recommendations to Act On First
Reduce initial server response time (TTFB). If PageSpeed flags this, it is almost always a hosting or caching problem. No front-end optimisation fixes a slow server. See What Is TTFB and Why Your Hosting Determines It for the full breakdown. This is the highest-priority fix because it affects every other metric.
Eliminate render-blocking resources. CSS and JavaScript files that load in the head of your page delay when the browser can start rendering content. A caching plugin with CSS/JS optimisation (or a managed host that handles this) defers non-critical scripts and inlines critical CSS.
Properly size images. Images served larger than their display size waste bandwidth and slow LCP. Set WooCommerce and WordPress thumbnail sizes to match your theme’s actual display dimensions. Serve images in WebP format where supported.
Reduce unused CSS and JavaScript. Most WordPress themes and plugins load their full asset files site-wide even when only used on specific pages. A plugin like Asset CleanUp or the optimisation features in WP Rocket can unload specific scripts from pages where they are not needed.
What Not to Obsess Over
A perfect 100 score is not the goal. Several factors lower Lighthouse scores without affecting real-world performance or rankings: third-party scripts from analytics, advertising, or live chat tools that Google flags but you cannot remove; WooCommerce session cookies that prevent full page caching; and Lighthouse’s test environment limitations that do not reflect real CDN delivery.
Focus on the field data section. If your Core Web Vitals pass in field data (shown as green), your site is performing well for real users and rankings. Use Lighthouse lab scores to identify specific technical issues, not to target an arbitrary number.
For how hosting affects these scores at the infrastructure level, see WP Engine Speed Test Results Explained.
Frequently Asked Questions
Does PageSpeed Insights score directly affect Google rankings?
The Lighthouse lab score shown in PageSpeed Insights does not directly affect rankings. What affects rankings is your Core Web Vitals field data: your real LCP, INP, and CLS values as measured from actual Chrome users. Use the lab score to diagnose issues, but monitor field data in Google Search Console for what actually affects your SEO.
Why does my PageSpeed score vary between tests?
PageSpeed Insights test results vary due to CDN cache state, server load at test time, network conditions between Google’s test servers and your host, and third-party script load times. Run multiple tests and average the scores for a reliable baseline. Significant variance (more than 15 points) usually points to inconsistent server response times.
My PageSpeed score is low but my site feels fast. Which is correct?
If your site feels fast for real users and your Core Web Vitals field data shows green in PageSpeed Insights, the site is performing well where it counts. Lighthouse lab scores test under specific simulated conditions (slow 4G mobile, no cached assets) that may not reflect your actual audience’s experience. Field data reflects reality; lab scores diagnose specific technical issues.
How much does hosting affect PageSpeed scores?
Significantly. Server response time (TTFB) is the first metric Lighthouse measures and affects every other score that follows. Moving from shared hosting to managed hosting with server-level caching routinely improves PageSpeed scores by 15 to 30 points, particularly for the mobile score where Google’s simulated connection is slower.
