Google's Core Web Vitals (CWV) became an official ranking signal in 2021 and have been updated twice since, most recently replacing FID with INP (Interaction to Next Paint) in March 2024. With over four years of data, we now have a clear picture of what actually moves rankings and what doesn't.
Core Web Vitals still matter, but they're a tiebreaker, not a differentiator. Here's the full picture, without the panic.
The Three Core Web Vitals (2025)
LCP — Largest Contentful Paint
LCP measures how long it takes for the largest visible content element on the page to load. Usually that's a hero image or a large heading, not body text.
- Good: ≤ 2.5 seconds
- Needs Improvement: 2.5 – 4.0 seconds
- Poor: > 4.0 seconds
LCP is the most impactful CWV for rankings. It correlates directly with perceived load speed and bounce rate. Fix this one first.
INP — Interaction to Next Paint (Replaced FID in 2024)
INP measures the latency of all user interactions throughout the entire page lifetime, not just the first click. This is a harder metric than FID, and the cutover caught a lot of teams off guard.
- Good: ≤ 200 ms
- Needs Improvement: 200 – 500 ms
- Poor: > 500 ms
Most sites that passed FID fail INP. React-heavy apps with complex re-renders are particularly exposed here.
CLS — Cumulative Layout Shift
CLS measures visual stability — how much page elements shift during loading. The most common offenders: images without set dimensions, dynamically injected ads, and web fonts that cause invisible-text flashes.
- Good: ≤ 0.1
- Needs Improvement: 0.1 – 0.25
- Poor: > 0.25
Do Core Web Vitals Actually Affect Rankings?
Yes, but less than most SEOs initially expected. The honest picture from the data:
- Sites passing all three CWVs rank roughly 1-2 positions higher than comparable sites that fail on mobile
- The effect is strongest in competitive niches where content quality is otherwise equal
- CWVs are a tiebreaker. Content relevance and backlinks still dominate.
- Mobile CWVs matter more than desktop because Google uses mobile-first indexing
In my experience, fixing CWV issues rarely vaults you from page 3 to page 1. But if you're competing for top-3 positions in a crowded niche, failing CWVs can be the thing holding you back.
The Most Important CWV Improvement Techniques
Improving LCP
1. Preload the LCP image:
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high">2. Use fetchpriority="high" on the LCP element:
<img src="/hero.webp" fetchpriority="high" alt="Hero image">3. Reduce server response time (TTFB). Use a CDN, enable HTTP/2, optimize your server. TTFB above 600ms makes good LCP nearly impossible regardless of what else you do.
4. Defer non-critical JavaScript and inline critical CSS. Render-blocking resources delay LCP more than most people realize.
5. Use next-gen image formats. WebP is typically 30% smaller than JPEG. AVIF is 40-55% smaller. The tradeoff is encoding time and slightly older browser support for AVIF.
Improving INP
1. Break up long tasks. Any JavaScript task over 50ms blocks the main thread. Use requestAnimationFrame or setTimeout(0) to yield to the browser between tasks.
2. Audit third-party scripts. Analytics, chat widgets, and A/B testing tools are the leading cause of INP failures. Not all of them are worth keeping.
3. For React/Vue/Angular sites, use React's startTransition for non-urgent state updates. Partial hydration or Islands architecture helps on content-heavy pages.
4. Move expensive computations to web workers to keep the main thread free for interactions.
Improving CLS
1. Always set width and height on images:
<img src="photo.jpg" width="800" height="600" alt="...">2. Reserve space for ads and embeds with CSS aspect-ratio or min-height on containers.
3. Don't insert content above existing content on load. Cookie notices and sticky bars that push content down are CLS traps.
4. Use font-display: optional or swap to prevent invisible text during font loading.
Checking Your Core Web Vitals
Two types of data, and the difference matters:
- Field data (CrUX) — Real user measurements from Chrome. This is what Google actually uses for rankings. Check it in Google Search Console.
- Lab data (Lighthouse) — Simulated measurements. Useful for debugging, but a 95 Lighthouse score doesn't mean your field data is good.
Use our free Website Speed Test to get Lighthouse scores and CWV lab data immediately. Then cross-reference with your Search Console Core Web Vitals report.
Common CWV Mistakes
- Optimizing for desktop only. Google ranks based on mobile experience. Fix mobile first, always.
- Trusting lab scores over field data. A 95 Lighthouse score doesn't guarantee good CrUX numbers.
- Ignoring TTFB. Time to First Byte above 800ms makes LCP improvements far harder to achieve.
- Third-party scripts. A/B testing and chat tools are responsible for over 40% of INP failures. Audit them regularly.
Core Web Vitals and GEO
Page speed is also relevant for AI search. Slow-loading pages get skipped during real-time AI crawling. Pages that load in under 2 seconds are crawled more reliably by PerplexityBot and ChatGPT's browsing feature, which means better GEO performance on top of the traditional SEO benefits.
Check both your CWV and GEO signals with our Website Speed Test and GEO Readiness Score tools.