Yes, site speed affects Google rankings. But not in the way most SEO guides describe it, and not as much as the hosting companies selling you expensive plans would like you to believe.
Here's the honest picture, based on what Google has actually said and what the data shows.
What Google Has Actually Said
Google confirmed page speed as a ranking signal in 2010 (desktop) and 2018 (mobile). In 2021, they formalized it via Core Web Vitals as part of the Page Experience update. Specifically: LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint, which replaced FID in 2024).
What Google hasn't said: that page speed is a dominant ranking factor. The Page Experience announcement specifically noted that "great page experience doesn't override having great page content." It's a tiebreaker, officially.
The Tiebreaker Reality
In my experience, this is accurate. I've analyzed hundreds of sites' CWV data against their ranking performance and the pattern is clear: passing Core Web Vitals gives you a small edge in close competition, but a fast site with weak content and few backlinks won't outrank a slow site with excellent content and strong links.
The situations where site speed actually moves rankings:
- You're competing for positions 3-10 in a relatively competitive niche where content quality is roughly equal among competitors
- You're in the "mobile-heavy" categories: news, entertainment, local search, food delivery
- Your current performance is genuinely terrible (LCP over 6 seconds, CLS over 0.5) — that level of failure does meaningfully suppress rankings
Going from a 90 PageSpeed score to 95 when you're already at position 8? Won't move you to position 3. Fixing an LCP of 8 seconds to 2 seconds? That can move the needle.
Core Web Vitals: The Actual Thresholds That Matter
Google's scoring uses field data (real user measurements via Chrome User Experience Report), not lab data (Lighthouse). The thresholds:
- LCP: Good = under 2.5s | Poor = over 4.0s
- INP: Good = under 200ms | Poor = over 500ms
- CLS: Good = under 0.1 | Poor = over 0.25
If your field CWV are "Good" on mobile, you're passing Google's threshold. Going from "Good" to "Exceptional" provides no additional ranking benefit based on available evidence. Getting from "Poor" to "Good" is where the ranking benefit exists.
The Real Reason to Care About Speed: Conversion Rates
This is the actual argument for investing in page speed, and it's stronger than the ranking argument.
The numbers from Google's research and industry studies:
- Pages loading in 1 second convert 3x better than pages loading in 5 seconds
- Each 100ms delay in load time reduces conversion rates by approximately 1%
- 53% of mobile users abandon a page that takes more than 3 seconds to load
- A 0.1 second improvement in LCP increases retail conversions by 2.5% (from Google's research)
For a site doing $50,000/month in revenue, a 10% conversion rate improvement from a 1-second LCP improvement is $5,000/month. That's a business case, not just an SEO argument.
What Tools to Use
Google Search Console (Core Web Vitals Report)
Field data — real user measurements that Google actually uses for rankings. This is the number that matters. Check it under Experience > Core Web Vitals.
Google PageSpeed Insights
Shows both lab and field data for any URL. The CrUX field data here is the same data Google uses. The Lighthouse lab score is useful for diagnosing issues, not for benchmarking rankings impact.
Chrome User Experience Report (CrUX) Dashboard
Looker Studio dashboard that shows your site's field data trends over time. Free, and the clearest view of how real users experience your site.
Our Free Speed Test
Our Website Speed Test gives you Lighthouse scores and CWV lab data instantly, without setting up Google tools first. Good for quick checks and competitive analysis.
Which Speed Improvements Actually Move Rankings
Based on impact-to-effort ratio, in order:
- Reduce LCP to under 2.5s on mobile — This is the big one. Preload the LCP image, reduce TTFB, use a CDN.
- Fix CLS to under 0.1 — Set explicit dimensions on images. Eliminate content that shifts after load.
- Reduce TTFB to under 600ms — Use caching, CDN, or static generation. Server response time is the ceiling for everything else.
- Fix INP to under 200ms on mobile — Audit third-party scripts. Reduce JavaScript execution on interaction.
If all four of those are in the "Good" range, further speed optimization is purely a conversion rate and user experience play. Still valuable — maybe more valuable than the ranking play. But be clear about why you're doing it.
Common Speed Myths Worth Ignoring
"Get a 100 PageSpeed score to rank #1" — No. Field data is what Google uses. A 100 lab score with bad field data does nothing for rankings.
"Shared hosting is killing your rankings" — Not directly. Slow TTFB from shared hosting hurts LCP, which affects rankings. But moving to an expensive server won't help if the bottleneck is client-side JavaScript.
"Improve page speed, improve rankings overnight" — CrUX field data uses a 28-day rolling window. Speed improvements take a month to fully reflect in your rankings, and the effect is modest unless you were genuinely in "Poor" territory.
The bottom line: invest in site speed primarily for conversions and user experience. The ranking benefits are real but modest. Any speed improvement that gets your Core Web Vitals into the "Good" range is worth doing; beyond that, focus on content and backlinks first.