How Latency Affects SEO: Core Web Vitals and Rankings
Page speed has been a Google ranking signal since 2010. Core Web Vitals made it explicit in 2021. Slow sites face a double penalty: lost conversions from poor UX and lost organic traffic from lower rankings.
Timeline: Speed as a Ranking Factor
Google announces page speed as a desktop ranking factor
Initially affected fewer than 1% of queries. Signal strength has increased steadily since.
Speed Update extends to mobile rankings
Mobile page speed becomes a ranking signal, affecting the majority of searches.
Core Web Vitals become ranking signals
LCP, FID (later replaced by INP), and CLS become explicit, measurable ranking factors via the Page Experience update.
INP replaces FID as the responsiveness metric
Interaction to Next Paint becomes a stable Core Web Vital in March 2024, measuring all interactions, not just the first. More comprehensive than First Input Delay.
Thresholds hold steady; field data drives ranking
Google's 'good' targets remain LCP under 2.5s, INP under 200ms, and CLS under 0.1, measured at the 75th percentile of real Chrome users. Core updates continue to refine ranking, but the CWV thresholds themselves are unchanged.
Current Core Web Vitals Thresholds (2026)
Google rates each metric at the 75th percentile of real-user (CrUX) data, scored separately for mobile and desktop. A page needs all three in the "good" band to pass.
Largest Contentful Paint
Measures loading performance. When the main content is visible.
Interaction to Next Paint
Measures responsiveness. Time from user interaction to visual update.
Cumulative Layout Shift
Measures visual stability. How much content shifts unexpectedly.
Thresholds per Google's web.dev Core Web Vitals documentation (web.dev/articles/vitals), unchanged since INP became a stable metric in March 2024.
The Tiebreaker Effect: Position 3 vs. Position 8
Core Web Vitals do not outrank content quality, backlinks, or relevance. But when two pages are otherwise equal in authority and content, CWV is the tiebreaker. The traffic difference between these positions is enormous:
| Position | Average CTR | Clicks at 10K searches/mo | Monthly Revenue at $5 CPC equiv. |
|---|---|---|---|
| #1 | 27.6% | 2,760 | $13,800 |
| #2 | 15.8% | 1,580 | $7,900 |
| #3 | 11.0% | 1,100 | $5,500 |
| #5 | 6.1% | 610 | $3,050 |
| #8 | 2.9% | 290 | $1,450 |
| #10 | 2.0% | 200 | $1,000 |
CTR data from Advanced Web Ranking. Revenue calculated as equivalent paid search value for illustration.
Moving from position 8 to position 3 nearly quadruples your organic traffic. For a high-volume keyword, that can mean hundreds of additional visitors per month. At a 3% conversion rate with $100 average order value, even a small additional visitor count generates thousands in additional monthly revenue from a single keyword. Multiply across all your keywords.
The Double Penalty of Slow Sites
Slow sites lose revenue through two independent channels that compound:
Channel 1: Direct Conversion Loss
Every extra second of load time costs ~7% of conversions. A site loading in 4s instead of 2s loses roughly 14% of potential revenue from every visitor who does arrive.
Channel 2: Organic Traffic Loss
Failing CWV thresholds pushes rankings down. Dropping from position 3 to position 8 means ~74% fewer organic clicks. You are converting a smaller percentage of an already-smaller audience.
Combined Impact Example
A site earning $10,000/month at position 3 with a 2s load time. If performance degrades to 4s: conversion loss = -14% ($1,400), ranking drop to position 8 = -74% traffic ($5,180). Combined monthly loss: roughly $6,580, or 66% of revenue. The two effects are multiplicative, not additive.
How to Check Your Core Web Vitals
Google Search Console
Search Console > Experience > Core Web VitalsThe CWV report shows site-wide performance grouped by URL pattern. This uses field data from real Chrome users. The most authoritative source for how Google sees your performance.
PageSpeed Insights
pagespeed.web.devEnter any URL to get both field data (from CrUX) and lab data (from Lighthouse). The field data section is what Google uses for ranking. Lab data helps diagnose issues.
Chrome DevTools
F12 > PerformanceOpen DevTools > Performance panel. Run a trace and check the Web Vitals section. Useful for debugging specific interactions that cause poor INP scores.
CrUX Dashboard
Chrome UX Report (BigQuery or Looker Studio)Public dataset of real user performance data for any origin with sufficient traffic. Updated monthly. Shows trends over time.