Core Web Vitals Explained: LCP, INP & CLS (2025 Guide)

Core Web Vitals guide illustration showing a developer climbing a page-speed performance curve.

What Are Core Web Vitals?
Largest Contentful Paint
Interaction to Next Paint
Cumulative Layout Shift
How to Measure
How to Fix Each Metric

Illustration of mobile Core Web Vitals data analysis.

Core Web Vitals are three metrics Google uses to evaluate page experience: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). They've been a confirmed ranking factor since 2021, and INP replaced First Input Delay (FID) in March 2024.

This guide explains each metric in plain English, shows how to measure them accurately, and lists the high-impact fixes that actually move the score. If you want this analysis done on your specific site, our Core Web Vitals audit delivers a developer-ready roadmap.

What Are Core Web Vitals?

Google introduced Core Web Vitals as part of its broader "Page Experience" signal in 2021. The intent: reward sites that load fast, respond quickly, and don't jank around as the page loads.

Google measures each metric at the 75th percentile of real users via the Chrome User Experience Report (CrUX) — meaning 75% of your visitors need to experience a passing score for your URL to be classified as "Good."

Largest Contentful Paint (LCP)

LCP measures when the largest visible element above the fold finishes rendering. For most pages, this is the hero image, the main headline, or a video poster frame.

Good: under 2.5 seconds
Needs improvement: 2.5–4.0 seconds
Poor: over 4.0 seconds

The most common LCP problems we see in audits: oversized hero images, missing image dimensions causing layout recalculation, render-blocking JavaScript delaying the LCP element, and slow TTFB at the server level.

Interaction to Next Paint (INP)

INP measures how quickly your page responds to user interactions — clicks, taps, and keypresses. Unlike FID (which only measured the first interaction), INP samples every interaction across the entire session and reports the worst.

Good: under 200ms
Needs improvement: 200–500ms
Poor: over 500ms

INP is dramatically harder to pass than FID was. JavaScript-heavy sites — React, Vue, Next.js apps — often passed FID but fail INP because the main thread is blocked during interactions. The fixes are deeper: code splitting, web workers, breaking up long tasks.

Cumulative Layout Shift (CLS)

CLS measures unexpected layout shifts during page load — when content jumps around because an image, ad, or late-loading element pushes everything else. CLS is a unitless score from 0 (no shift) to higher values.

Good: under 0.1
Needs improvement: 0.1–0.25
Poor: over 0.25

The biggest CLS culprits: images without explicit width/height attributes, web fonts that swap mid-load, ads that load asynchronously, and dynamically inserted content above existing content.

How to Measure Core Web Vitals

You have three measurement options, each with strengths:

Google Search Console: Shows real-user CrUX data aggregated across your indexed URLs, grouped into "Good," "Needs Improvement," and "Poor." Best starting point.
PageSpeed Insights: Pulls both lab data (Lighthouse) and CrUX field data for individual URLs. Free, gives both views.
Real User Monitoring (RUM) tools: SpeedCurve, Calibre, Sentry RUM. Best for ongoing tracking, especially after deploys.

Don't rely only on Lighthouse lab scores — they're useful for debugging but don't reflect what real users experience. CrUX data is what Google uses for ranking.

How to Fix Each Metric

Fixing LCP

Compress and resize hero images. Use modern formats (WebP, AVIF).
Add explicit width/height attributes to all images.
Use fetchpriority="high" on the LCP element.
Defer or async non-critical JavaScript.
Use a CDN to reduce TTFB.

Fixing INP

Code-split your JavaScript bundles.
Break up long tasks (over 50ms) using requestIdleCallback or setTimeout.
Move heavy work to web workers.
Optimize third-party scripts (chat widgets, analytics, A/B testing).
Avoid synchronous JavaScript on critical interaction handlers.

Fixing CLS

Always specify width and height on images and video.
Reserve space for ads and embeds before they load.
Use font-display: swap with proper font fallback metrics.
Avoid inserting content above existing content unless triggered by user action.
Preload critical fonts.

The Bottom Line

Core Web Vitals are a ranking tie-breaker, not a primary signal — but they also directly affect bounce rate, conversion, and engagement, which compound into stronger search performance over time. Hit all three at the 75th percentile and you pass; fail any one and you don't.

For a developer-ready CWV audit with prioritized fixes for your specific URLs, see our Core Web Vitals audit service.

Key Takeaways

If you only remember three things from this guide:

SEO is a discipline, not a hack. The sites that win in 2025 are the ones with disciplined technical foundations, useful content, and consistent execution. Quick fixes rarely move rankings; systematic improvements compound.
Audits surface what tools miss. Anyone can run Screaming Frog or PageSpeed Insights. The value is in interpretation — a senior auditor turning raw data into a prioritized roadmap your team can actually ship.
Implementation is where ROI happens. The best audit in the world is worthless if the recommendations sit in a Slack channel for six months. Plan for execution before you commission the audit.

Frequently Asked Questions

How does this apply to my specific industry?

Most SEO fundamentals apply across industries, but each vertical has unique signals — YMYL standards for healthcare and legal, faceted navigation challenges for e-commerce, freshness requirements for news. We tailor our audits to industry-specific patterns. See our industry pages for niche-specific guidance.

Do I need to redo this when Google updates its algorithm?

Major Google updates happen 4–8 times per year (Core Updates, Helpful Content, Reviews, Spam). Most don't require a wholesale strategy reboot, but each one warrants a quick audit to see whether your traffic patterns shifted. Sites with strong fundamentals tend to weather updates well; sites with shortcuts tend to get hit.

What tools should my team use day-to-day?

At a minimum: Google Search Console (free, indispensable), Google Analytics 4 (free), one paid SEO platform (Ahrefs, Semrush, or Moz), and Screaming Frog for crawl analysis (free for sites under 500 URLs). Most professional SEO work can be done with that stack alone.

How do I know if I need professional help vs DIY?

If you have a dedicated SEO professional in-house with 5+ years of experience, you can likely run audits internally and supplement with external second opinions. If your team is marketing-generalist or technically skilled but new to SEO, a professional audit will surface issues you don't know to look for — and the ROI typically pays back within 60–90 days.