Core Web Vitals SEO
Core Web Vitals are Google's field-based metrics for measuring a page's real-world loading, interactivity, and visual stability experience.
Key takeaways
- Core Web Vitals measure real user experience, not just lab tests.
- Three metrics: LCP (loading), INP (interactivity), CLS (visual stability).
- Good thresholds: LCP ≤2.5s, INP ≤200ms, CLS <0.1.
- Use Google Search Console field data for prioritization.
- Content relevance still matters more than Core Web Vitals for ranking.
These three metrics—LCP, INP, and CLS—reflect how real users actually experience your site.
Example
A product page on an e-commerce site:
- LCP: The hero image takes 3.2 seconds to load (poor, target ≤2.5s).
- INP: Clicking the "Add to Cart" button feels sluggish, responding in 400ms (poor, target ≤200ms).
- CLS: As the page finishes loading, a banner ad pushes the product description down by 150px (poor, target <0.1).
Result: Users bounce, conversions drop, and the page may rank lower in Google Search.
When Should I Use This?
Core Web Vitals should be part of your technical SEO checklist when:
- Launching a new site or redesign.
- Diagnosing organic traffic drops or high bounce rates.
- Optimizing for Google’s page experience ranking signals.
- Prioritizing technical fixes in an SEO audit.
- Improving mobile user experience for any page.
What It Is Not
- A single score: Core Web Vitals are three separate metrics, not one number.
- Lab-only measurement: They are field metrics collected from real Chrome users, not just Lighthouse tests.
- A direct ranking factor: They are part of page experience signals, but content relevance is far more important.
- The FID metric: Interactivity is now measured with INP (Interaction to Next Paint), not First Input Delay (FID).
- A replacement for other SEO work: Good Core Web Vitals do not compensate for weak content or bad links.
Quick Start
- Open Google Search Console and navigate to the Core Web Vitals report.
- Identify which metric (LCP, INP, CLS) is failing on mobile or desktop.
- For LCP issues: Optimize hero images, reduce server response time, and remove render-blocking resources.
- For INP issues: Minimize JavaScript execution, debounce event handlers, and avoid long tasks.
- For CLS issues: Set explicit width/height for images and ads, reserve space for dynamic content.
- Test fixes using PageSpeed Insights or field data in Search Console.
- Monitor the report weekly until all URLs pass the “Good” threshold.
Common Mistakes
- Treating Core Web Vitals as a single score instead of three independent metrics.
- Using FID as the interactivity metric instead of INP (INP replaced FID in 2024).
- Relying only on lab scores (e.g., Lighthouse) and ignoring field data from real users.
- Assuming Core Web Vitals override content relevance and other SEO factors.
- Focusing only on desktop while ignoring mobile, which is often worse and more impactful.
Next step
FAQ
What is a good Core Web Vitals score?
There is no single score. Good thresholds: LCP ≤2.5 seconds, INP ≤200 milliseconds, CLS <0.1.
How do I check my Core Web Vitals?
Use Google Search Console (Core Web Vitals report) or PageSpeed Insights.
Related topics
Sources
- Google Search Central — Understanding Core Web Vitals and Google search results — Primary source for definitions, thresholds, and Google’s Search guidance.
- Google Search Central — Core Web Vitals reporting and tools — Best source for how Google measures and recommends improving the metrics.
- Chrome Developers — Web Vitals — Canonical explainer for the metric family and implementation context.
- Google Search Console Help — Core Web Vitals report — Useful for understanding how site owners see CWV data in Search Console.
Reviewed by Lucía Marín, Founding editor.