Core Web Vitals SEO

Core Web Vitals are Google's three field-based metrics measuring a page's real-world loading, interactivity, and visual stability, used as part of page experience signals for Search.

Many SEOs treat Core Web Vitals as a single pass/fail test, but they are three separate field metrics that contribute to but do not override content relevance.

Key points

Measure LCP, INP, and CLS separately because a good score on one does not excuse a poor score on another.
Use field data from Search Console, not lab-only scores, to understand real user experience.
How to optimise website performance: use Core Web Vitals to identify the most impactful technical fixes, then address them in order of user impact.
Core Web Vitals confirm that page speed affects SEO as part of page experience signals, but speed alone does not determine rankings.

The same metric, different devices, different outcomes

A news site's LCP was 2.8s on desktop (good) but 5.2s on mobile (poor). The Search Console report showed 62% of mobile URLs failing. The issue was a large hero image not lazy-loaded. After adding lazy loading, mobile LCP dropped to 2.1s, and the pass rate rose to 89%. The site owner asked 'does page speed affect SEO?' and saw that the improvement correlated with higher organic traffic.

Three metrics you must measure separately

LCP (Largest Contentful Paint) Measures loading performance: time largest content element becomes visible. Target 2.5 seconds or less. Poor LCP often from slow server, render-blocking resources, or unoptimised images.
INP (Interaction to Next Paint) Measures interactivity: delay between user interaction and next paint. Target under 200 milliseconds. INP replaced FID in 2024; outdated tools may report FID.
CLS (Cumulative Layout Shift) Measures visual stability: sum of unexpected layout shifts. Target below 0.1. Common causes: images without dimensions, ads, dynamic content that pushes elements.

Four ways people misread Core Web Vitals

Confusing FID with INP Many SEOs still reference First Input Delay (FID) as the interactivity metric. Google replaced FID with INP in March 2024. Using old data or tools that report FID gives misleading results.
Treating lab scores as final Lab data from Lighthouse shows a single synthetic test under ideal conditions. Google uses field data from real users for ranking. A lab pass does not guarantee a field pass.
Ignoring the device split Core Web Vitals are reported separately for mobile and desktop. A page may pass on desktop but fail on mobile. Optimising for one device leaves a gap in page experience.
Focusing only on the average The 75th percentile is the threshold metric, not the average. If 25% of users have poor experience, you fail. Target the tail, not the mean.

Three things to check before you act

Identify the worst metric Start with the Core Web Vitals report in Search Console to see which metric fails most often. Fixing the biggest problem gives the most improvement for users and signals.
Use real user monitoring Tools like CrUX and PageSpeed Insights provide field data. Lab tools alone cannot replicate real-world conditions. Rely on field data to prioritise fixes.
Fix the biggest impact first A single change can improve multiple metrics. For example, reducing image sizes can improve LCP and CLS. Look for high-leverage optimisations that address several issues.

Common questions

What are Core Web Vitals?

Core Web Vitals are Google's three field-based metrics—LCP, INP, CLS—that measure real-world loading, interactivity, and visual stability.

What is INP?

INP stands for Interaction to Next Paint and measures a page's responsiveness to user interactions, with a target of under 200 milliseconds.

Sources

Google Search Central — Understanding Core Web Vitals and Google search results Official Google documentation on Core Web Vitals and their role in search.
Chrome Developers — Web Vitals Google's guide to the Web Vitals initiative, including metrics and thresholds.