Does page speed actually move rankings, or just help conversions?
- Published November 6, 2026
- Linked from 5 answers
- In a cluster of 8
Both, but not equally. Google’s ranking systems use Core Web Vitals, which measure loading speed, responsiveness, and visual stability, so speed is a real input. Google is just as clear about its limits: its page experience documentation says good results in reports like the Core Web Vitals report “doesn’t guarantee that your pages will rank at the top”, and that Google aims to show the most relevant content even when page experience is weaker. Speed can matter between pages that are otherwise close; it does not lift a page that answers the query worse.
Where the ranking effect sits
Search Console groups pages as Good, Needs Improvement or Poor against thresholds measured on real visits, and Google’s documentation describes no extra credit for scores beyond Good. The thresholds, from web.dev’s Core Web Vitals guide:
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading: when the main content appears | Within 2.5 seconds |
| Interaction to Next Paint (INP) | Responsiveness to taps, clicks, and keys | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
A page passes when it meets all three at the 75th percentile of page loads, measured separately on mobile and desktop. INP replaced First Input Delay as a Core Web Vital in March 2024. Google’s documentation warns against treating a perfect score as the goal: trying to get a perfect score “just for SEO reasons may not be the best use of your time.”
Where speed pays more
Visitors feel speed before Google measures it. A slow page loses people who leave before it finishes loading, and a sluggish page frustrates the ones who stay. Those losses show up in your own analytics and sales, regardless of what happens to your position. Measure them directly: compare conversion rate by page load time in your analytics, or test a faster template on a section of the site.
How to decide whether speed work is worth it
- Open the Core Web Vitals report in Search Console. URL groups marked Poor on mobile are the first candidates.
- For a page that ranks well and fails a threshold, fixing it protects a close comparison and improves the experience.
- For a page that ranks poorly and passes, speed is unlikely to be what holds it back, provided the pass reflects that page: the report groups similar URLs, so check the page’s own field data where there is enough of it; to decide between content and Core Web Vitals, use whether to fix Core Web Vitals or content first on a weak page. Two narrower speed decisions follow: self-hosting or a CDN for speed, and when render-blocking resources cost rankings.
- For a page that passes and converts poorly, speed may still be worth improving for visitors, judged by conversion data rather than rankings.
Treat speed as a requirement for a good page, and judge the work by the visitors it keeps.
Add a comment