Guides
Core Web Vitals and SEO: What Actually Matters
What Core Web Vitals measure, how much they really affect rankings, how to measure them with field data, and the mistakes that waste your optimisation effort.
Run a fresh DomainLens audit and use the report as your priority list.
What Core Web Vitals actually measure
Core Web Vitals are three field metrics that describe how a real visit feels: how fast the main content appears, how quickly the page responds to interaction, and how visually stable it is while loading. Google collects them from real Chrome users and uses them as part of its page experience signals.
They are not a separate ranking trick. Page experience is a tiebreaker: when two pages are similarly relevant, the faster, more stable one has an edge. Great Core Web Vitals will not rescue thin or irrelevant content, but poor ones can hold back a page that otherwise deserves to rank.
The important word is field — real users on real devices and networks. A perfect lab score on your fast laptop means little if real visitors on mid-range phones experience something slower.
The three metrics, in plain terms
- LCP (Largest Contentful Paint) — how long until the largest visible element, usually the hero image or headline, finishes rendering. Aim for under 2.5 seconds.
- INP (Interaction to Next Paint) — how quickly the page responds after a click, tap, or keypress. Aim for under 200 milliseconds.
- CLS (Cumulative Layout Shift) — how much the layout jumps around while loading. Aim for under 0.1.
How much Core Web Vitals affect rankings
Treat Core Web Vitals as a meaningful but secondary factor. Relevance, content quality, and links decide most of the ranking; page experience refines it at the margins and matters more in competitive results where everything else is close.
There is also a user-experience payoff that is independent of rankings: faster, more stable pages convert better and bounce less. Even if the ranking effect is small, the business effect often is not.
How to measure them correctly
- Prefer field data: the Core Web Vitals report in Search Console and the CrUX dataset reflect real users.
- Use lab tools (Lighthouse, PageSpeed Insights lab section) to debug, not to judge — they simulate one device.
- Segment mobile and desktop separately; problems usually appear on mobile first.
- Measure the page types that matter, not just the homepage — templated inner pages often perform differently.
Common Core Web Vitals mistakes
- Optimising for a green lab score while real-user field data stays poor.
- Ignoring INP because older audits only reported the now-retired First Input Delay.
- Fixing the homepage and assuming inner templates improved too.
- Loading every third-party script eagerly, then wondering why interaction is slow.
How DomainLens reports them
DomainLens pulls Core Web Vitals into the same report as crawlability, indexability, and on-page checks, so you see performance alongside the issues that actually block ranking rather than in a separate silo.
Use it to spot which metric is failing and on which page type, then dig into the specific cause — hero image, long JavaScript task, or unstable layout — with the matching DomainLens guide.