Does Page Speed Affect SEO?
Performance work gets sold internally on SEO because that is the budget line it fits. The claim is true enough to justify the work and overstated often enough to disappoint whoever approved it, since a site that fixes its vitals and expects a ranking jump usually does not get one.
What has Google actually said?
That page experience signals, including Core Web Vitals, are used in ranking, and that they matter most when multiple pages answer a query with comparable relevance and quality. Google has repeatedly stated that great content will still rank above faster but less relevant pages.
That framing has been consistent since the page experience update rolled out in 2021. Nothing in it promises movement for a page that already ranks where its content merits, and the wording deliberately positions speed as a differentiator rather than a driver.
Where does speed genuinely change outcomes?
In behaviour after the click. Slow loading increases abandonment before the page renders, and layout shift causes mis-taps and frustration that shorten sessions. These effects are measurable in analytics and revenue regardless of whether search position moves at all.
Crawl efficiency is a second, less-discussed channel. A faster server lets Googlebot fetch more URLs within its crawl budget, which matters for large sites where indexation coverage is the actual constraint. On a fifty-page brochure site it is irrelevant.
Does failing Core Web Vitals get you penalised?
No. There is no penalty mechanism for slow pages. Failing simply means you forgo a small positive signal, which is materially different from being demoted. Pages that fail their vitals continue to rank at the top of competitive queries every day.
The distinction matters for prioritisation. If a page is failing vitals and also ranking poorly, the ranking problem is almost certainly about content, intent match or links. Fixing LCP will not address any of those, and treating it as the cause wastes a quarter.
How should you prioritise performance work?
Start with pages that carry commercial value and fail their vitals, not with whatever scores worst. A checkout flow at 0.3 CLS deserves attention before a blog archive at 0.4, because the cost of frustration differs by orders of magnitude between them.
Then fix the specific failing metric rather than pursuing a general score. Sites routinely spend weeks on image optimisation when their failure was INP caused by a third-party script, because the composite score directed attention at the wrong thing.
Key takeaways
- Core Web Vitals are a confirmed but modest ranking signal, positioned as a tiebreaker.
- There is no penalty for failing; you simply forgo a small positive signal.
- Abandonment and conversion effects are usually larger than ranking effects.
- Crawl efficiency matters for large sites and is irrelevant for small ones.
- Prioritise commercially important pages and fix the specific failing metric.
Frequently asked questions
- Will fixing Core Web Vitals improve my rankings?
- Possibly slightly, and only where you compete against pages of similar relevance and quality. If your content is weaker than competitors, speed will not close that gap. Expect performance work to protect position and improve conversion rather than to lift rankings on its own.
- Does page speed matter more on mobile?
- Effectively yes, because Google indexes mobile-first and mobile field data typically sets the failing assessment. Mobile devices are slower and networks less reliable, so the same page usually performs worse there. Mobile is where the assessment is won or lost.
- Do AI search engines care about page speed?
- Less directly, since they retrieve and summarise content rather than ranking pages for a click. Crawlability and clean static HTML matter more to them than paint timings. A page that renders content only via JavaScript risks being read as empty regardless of how fast it feels.
- Is there evidence linking speed to conversion?
- Numerous published case studies from retailers and publishers report conversion improvements after latency reductions, though the figures vary widely by sector and baseline. Treat specific percentages as illustrative of direction rather than transferable to your site without testing.
Web Performance, BigBalli. We track Core Web Vitals definitions and thresholds as Google revises them, cross-checked against web.dev and Chrome developer documentation.