Core Web Vitals and SEO: Why Page Speed Actually Affects Rankings

The Half-Second That Cost More Than It Looked Like

We were once asked to explain, in a single sentence, why a technically “fine” ecommerce page was converting at half the rate of a competitor's. The honest answer was almost anticlimactic: their Largest Contentful Paint was sitting around 4.5 seconds, largely due to an unoptimized hero image and three separate marketing scripts loading before the main content rendered. Nothing was broken. It was simply slow, in a way that quietly bled conversions every single day without ever showing up as an error anywhere.

That's the uncomfortable thing about page speed — it rarely fails loudly. It just costs you a percentage of everyone who almost stayed.

What Core Web Vitals Actually Measure

• Largest Contentful Paint (LCP) — how long it takes the main content of a page to become visible. Google's threshold for "good" is under 2.5 seconds.
• Interaction to Next Paint (INP) — how responsive the page feels when someone actually interacts with it, replacing the older First Input Delay metric in 2024.
• Cumulative Layout Shift (CLS) — how much visible content unexpectedly shifts around while a page loads, the metric behind that frustrating experience of a button moving right as you're about to tap it.

Google has been consistent on one point that's worth repeating precisely: Core Web Vitals is one signal among many, not a dominant one. As Google's own John Mueller has put it, when competing pages are otherwise similar in relevance and quality, Core Web Vitals can become the deciding factor — which is exactly the scenario in the two-competitor story that opened this piece.

The Business Case Is Bigger Than the Ranking Case

The SEO angle on Core Web Vitals is real but secondary to a more direct fact: a one-second delay in mobile load time has been repeatedly measured to reduce conversions by roughly 7 percent — a figure that traces back to joint research from Google and Deloitte and has been reproduced across multiple independent studies since. For a site doing meaningful revenue, that single second is a real, recurring cost, entirely separate from whatever it does to your search ranking.

The scale of the underlying problem is larger than most site owners assume. Data from HTTP Archive's ongoing Core Web Vitals tracking has consistently found that a substantial share of sites — commonly cited around 40-45% of mobile sites — fail to meet all three thresholds simultaneously, meaning most competitive categories still have real room for a fast site to stand out.

The Most Common Causes, in Order of How Often We See Them

1. Unoptimized hero images — the single most frequent cause of a poor LCP score on content and ecommerce sites alike.
2. Render-blocking third-party scripts — chat widgets, marketing pixels and ad tags that load before the main content, one at a time.
3. Web fonts causing layout shift — text rendering in a fallback font, then visibly reflowing once the real font loads.
4. Ads or embeds injected without reserved space — the classic cause of a page jumping just as someone reaches to tap something.
5. Unoptimized JavaScript execution — heavy client-side rendering that delays how quickly a page becomes genuinely interactive.

Fixing It Doesn't Require a Rebuild

Most Core Web Vitals problems are fixable without touching the site's design or rebuilding the platform: compress and properly size images, defer non-critical scripts, reserve layout space for ads and embeds before they load, and audit exactly which third-party tags are actually earning their keep. This is precisely the kind of fix our technical SEO checklist is built to catch early, and it's a natural extension of conversion rate optimization — a faster page converts better independent of any ranking benefit at all.

Mobile Is Where This Actually Gets Decided

Google indexes mobile-first, which means your mobile Core Web Vitals scores are what count for ranking purposes, regardless of how fast your desktop experience is. Mobile consistently scores worse than desktop across the web — slower processors, inconsistent network conditions, heavier proportional impact from the same unoptimized assets — which makes mobile-specific testing, not just a desktop check, the non-negotiable step most audits skip.