SEO · Search Engine Optimisationintermediate3 min read

What is Core Web Vitals?

Core Web Vitals are a set of three Google-defined metrics that measure real-world user experience on a webpage: Largest Contentful Paint (LCP) measures loading speed, Interaction to Next Paint (INP) measures responsiveness, and Cumulative Layout Shift (CLS) measures visual stability. Since 2021, they are confirmed Google ranking signals.

24%
lower bounce rate on sites that pass Core Web Vitals vs those that fail
Source: Google, 2021
Fact-checked against 3 sourcesLast updated 8 June 2026
Key Takeaways
  • LCP should be under 2.5 seconds, INP under 200ms, CLS under 0.1.
  • Core Web Vitals are measured from real user data (CrUX), not just lab tests — use Search Console for accurate scores.
  • LCP is most commonly fixed by optimising images and reducing server response time.
  • CLS is usually caused by images/videos without dimensions, or late-loading ads pushing content down.
  • PageSpeed Insights and web.dev/measure give free CWV audits.

The Three Core Web Vitals Explained

LCP (Largest Contentful Paint): How long it takes for the largest visible element to load — usually a hero image or above-the-fold text. Target: under 2.5s. Main fixes: optimise images, use a CDN, preload critical resources.

INP (Interaction to Next Paint): Replaced FID in 2024. Measures the delay between a user interaction (click, tap, key press) and the visual response. Target: under 200ms. Main fixes: reduce JavaScript execution time, avoid heavy event handlers.

CLS (Cumulative Layout Shift): Measures unexpected layout shifts during page load. A score of 0.1 or less is good. Main fixes: set explicit width/height on images and embeds, avoid inserting content above existing content.

How to Measure and Fix Core Web Vitals

Start with Google Search Console → Core Web Vitals report. This shows real-world data from Chrome users. Then use PageSpeed Insights for page-level diagnostics and specific fix recommendations.

For LCP: compress and properly size images, use next-gen formats (WebP/AVIF), add image preload hints, and improve Time to First Byte (TTFB) with server-side caching.

For CLS: audit every image and video element for explicit dimensions. Check for ad slots, embeds, and dynamic content that appears without reserved space.

Stay sharp

Most guides are already outdated.

One email a week. The search stuff that actually matters — what shifted, what died, and what to do about it.

Subscribe free →
2.5s
LCP target threshold (Good)
200ms
INP target threshold (Good)
0.1
CLS target score (Good)
2021
Year CWV became Google ranking signals
CORE WEB VITALS: A BRIEF HISTORY
2020
Core Web Vitals Introduced

Google announced the Core Web Vitals initiative in May 2020, introducing LCP, FID, and CLS as the three defining metrics for page experience.

2021
Page Experience Rollout

Core Web Vitals officially became Google ranking signals as part of the Page Experience update, rolling out across all pages by August 2021.

2023
INP Introduced as Experimental Metric

Google introduced Interaction to Next Paint (INP) as a pending replacement for First Input Delay (FID), giving developers time to adapt.

2024
INP Replaces FID

In March 2024, INP officially replaced FID as a Core Web Vital, offering a more comprehensive measure of a page's overall responsiveness throughout the entire user session.

✓ DO

Set explicit width and height attributes on all images and video elements to prevent layout shifts

Use a Content Delivery Network (CDN) to reduce server response times and improve LCP

Preload your LCP image using <link rel='preload'> in the document head

Serve images in next-gen formats like WebP or AVIF to reduce file size

Reserve space for ads and dynamic embeds before they load to protect your CLS score

✗ DON'T

Inject content above existing on-page content after the page has begun rendering

Use render-blocking JavaScript or CSS that delays the loading of the largest visible element

Rely solely on CSS to size images without defining HTML width/height attributes

Use heavy synchronous event handlers that block the main thread and inflate INP

Ignore mobile CWV scores — Google primarily uses mobile data for ranking assessments

CORE WEB VITALS: GOOD VS. NEEDS IMPROVEMENT VS. POOR
MetricGoodNeeds ImprovementPoor
LCP (Loading)≤ 2.5s2.5s – 4.0s> 4.0s
INP (Responsiveness)≤ 200ms200ms – 500ms> 500ms
CLS (Visual Stability)≤ 0.10.1 – 0.25> 0.25
CORE WEB VITALS AUDIT CHECKLIST
0/7 complete
Check your Core Web Vitals report in Google Search Console to identify failing URLs at scale
Run PageSpeed Insights on your top landing pages to get field data and lab diagnostics
Confirm your LCP element is identified correctly and is being preloaded or prioritised
Audit all images and embeds to ensure explicit width and height dimensions are set
Review JavaScript bundles for long tasks (>50ms) that could be causing high INP scores
Test for CLS caused by late-loading web fonts by using font-display: swap or preloading fonts
Verify that TTFB is under 800ms — slow server response directly delays LCP
⚠️
Field Data Overrides Lab Data for Rankings

Google uses real-user field data (Chrome User Experience Report / CrUX) — not lab simulations — to evaluate Core Web Vitals for ranking purposes. A page may pass in PageSpeed Insights lab mode but still fail in Search Console if real users experience slower conditions. Always prioritise fixing your Search Console field data, not just your lab score.

Free Tool

How does your site score on SEO?

Paste your URL. Get a score and a fix list across all three disciplines. No form, no email.

Run Free Audit →

Frequently Asked Questions

Google has confirmed CWV as a tiebreaker signal — if two pages are equally relevant, the one with better CWV may rank higher. In practice, content quality and relevance still dominate. CWV matters most in competitive niches where the top pages are nearly identical in content quality.

Lab data (PageSpeed Insights, Lighthouse) is measured in a controlled environment with simulated conditions. Field data (CrUX) is aggregated from real Chrome users on your pages. Google uses field data for ranking. If your lab score is good but field score is poor, investigate real-world performance issues like third-party scripts or mobile-specific bottlenecks.

Sources & Further Reading
  • 1.Google — Core Web Vitals documentation
  • 2.web.dev — Web Vitals
  • 3.Google Search Console CWV report