Get a free audit

Core Web Vitals Explained in Plain Terms.

Core Web Vitals are three measurements: LCP (loading speed), INP (responsiveness), CLS (visual stability), and Google uses them as a confirmed ranking signal. Good thresholds: LCP under 2.5 seconds, INP under 200ms, CLS under 0.1. Anything worse than 500ms INP or 0.25 CLS is flagged 'poor' by Google. You can check your own site's scores for free in Google Search Central's page experience tools before paying anyone to fix them.

09/24/2026·7 min read

Core Web Vitals are three specific measurements Google uses to judge how a webpage feels to use: how fast the main content loads, how quickly the page responds when you click something, and whether elements jump around while you are trying to read. That is the whole concept. Everything past this paragraph is detail on how those three numbers get measured and why they matter more than most site owners realize.

I am Bogoljub Zec, and I run a one-person web development and technical SEO studio in Novi Sad, Serbia. Most of the client work that lands on my desk starts with someone asking why their site ranks lower than a competitor with worse content. Nine times out of ten, part of the answer is sitting in these three metrics.

What each letter actually measures

LCP stands for Largest Contentful Paint. It is the time between a visitor opening your page and the biggest visible element (usually a hero image or a headline block) finishing its render. Google treats anything above 2.5 seconds as poor, and anything under that as good. There is no partial credit zone that matters for ranking purposes: you are either inside the good range or you are not.

INP stands for Interaction to Next Paint. It replaced an older metric called First Input Delay, and it measures the delay between a user action (a tap, a click, a keypress) and the moment the browser visibly responds. Google's threshold here is under 200ms for good, over 500ms for poor. This is the metric that catches sites where the button looks clickable but nothing happens for half a second because JavaScript is busy doing something else.

CLS stands for Cumulative Layout Shift. It measures how much visible content moves without a user causing it. Think of a page where you go to tap a link and an ad loads above it, shoving the link down half a second before your finger lands. Google scores that as CLS. Under 0.1 is good. Above 0.25 is poor.

A developer's monitor showing performance metrics during a site audit
A developer's monitor showing performance metrics during a site audit

Why Google put a number on user experience

Core Web Vitals are a confirmed ranking signal according to Google Search Central's own page experience documentation. That does not mean a fast site with thin content will outrank a slow site with strong content. It means that among pages of comparable quality, the faster and more stable one gets an edge. For competitive keywords where ten sites all have decent content, that edge decides who is on page one and who is on page two.

There is a second reason this matters that has nothing to do with rankings: conversion. A page that shifts under your thumb or takes three seconds to respond to a tap loses visitors regardless of what Google thinks. I have watched client analytics drop off mid-scroll on pages with bad CLS scores. People do not file a complaint, they just leave.

The three letters, LCP, INP, CLS, are not abstract engineering jargon. They are Google's attempt to quantify the exact moment a visitor gets annoyed and leaves.

How I read these numbers on a real site

When I run a technical audit through BZ Development, Core Web Vitals are one of the first things I pull, not because they are the only thing that matters, but because they are cheap to check and expensive to ignore. Google Search Console gives you a Core Web Vitals report broken down by URL group, using real visitor data collected in the field rather than a lab test. That field data is what actually affects ranking, so I always start there instead of a synthetic speed test.

The common culprits I find, in rough order of frequency: unoptimized hero images that are three or four times larger than the display size needs, third-party scripts (chat widgets, ad tags, analytics snippets) that block the main thread and hurt INP, and web fonts or ads that load late and shift the layout, hurting CLS. None of these require a rebuild. Most are fixable in a focused pass over a few days.

Close-up of a laptop screen displaying a Lighthouse performance report
Close-up of a laptop screen displaying a Lighthouse performance report

What a good score is worth and what it is not

A perfect Core Web Vitals score does not guarantee traffic. I want to be direct about that because I have seen agencies sell "Core Web Vitals optimization" as if it were a magic lever. It is one input among many: content relevance, backlinks, site structure, and search intent matching all carry weight too. What a good score does is remove a ceiling. If your INP is sitting at 800ms, you are capped no matter how good the content is, because Google's own systems flag that as a poor experience and weight it accordingly.

The inverse is also true. I have taken over sites where every technical box was checked, LCP under a second, CLS at zero, and the site still ranked poorly because the content did not answer the query anyone was actually searching for. Core Web Vitals fix the plumbing. They do not write the content.

Where to check your own numbers first

Before hiring anyone to fix Core Web Vitals, check them yourself. Google Search Central publishes free tools that report the same field data Google uses internally, so there is no reason to pay for a diagnosis you can run in five minutes. If the report shows real problems across a meaningful chunk of your URLs, that is when a focused technical pass earns its cost. If it shows a handful of borderline pages, you may not need to do anything urgent at all.

Photography: AS Photography, Daniil Komov, Atlantic Ambience on Pexels


Frequently asked questions
They are LCP (Largest Contentful Paint, measuring load speed), INP (Interaction to Next Paint, measuring responsiveness), and CLS (Cumulative Layout Shift, measuring visual stability). Google publishes 'good' and 'poor' thresholds for each.
Google treats Largest Contentful Paint under 2.5 seconds as good, and anything above 2.5 seconds as poor. There is no separate 'needs improvement' tier that changes how ranking treats the page.
Interaction to Next Paint (INP) replaced First Input Delay as the responsiveness metric in Core Web Vitals. Google treats INP above 500ms as poor and under 200ms as good.
Yes, Core Web Vitals are a confirmed ranking signal according to Google Search Central's page experience documentation. They function as a tiebreaker among pages of otherwise similar content quality rather than a dominant ranking factor on their own.
Google treats Cumulative Layout Shift above 0.25 as poor and under 0.1 as good. Layout shift usually comes from images without set dimensions, late-loading ads, or web fonts that swap in after the page renders.
Google Search Console has a Core Web Vitals report built from real visitor data, which is the same field data Google uses for ranking purposes. It is worth checking there before paying for any external audit.
Yes. Core Web Vitals remove a technical ceiling but do not substitute for relevant content, proper site structure, or matching what a searcher actually wants. I have taken over sites with excellent scores and weak rankings because the content did not answer the query.
It depends on the cause, but common fixes like image compression, deferring third-party scripts, and reserving space for ads or fonts are usually a focused few days of work rather than a full rebuild.