Core Web Vitals are Google's way of measuring whether your page actually feels fast and stable to real users. They became ranking signals in 2021. They're not the biggest ranking factor, but they're the tiebreaker that decides who wins when two pages are otherwise equal. And more importantly, they directly affect conversion. This page walks through the three metrics, what each one really means, how to measure them, and how to fix them without burning weeks.
Google's whole business depends on people trusting search. If the top result is a page that takes six seconds to load and jumps around while loading, people bounce back to Google, click the next result, and eventually switch to a different search engine. Google loses. So Google penalizes slow, janky pages to protect its own product.
Core Web Vitals are Google's attempt to measure the specific flavors of slow and janky that drive users away. They're not abstract metrics. Each one tracks a specific thing that would annoy you if it happened on a page you were trying to use.
How long until the biggest visible element on the page has finished rendering. Usually that's a hero image, a big headline, or the main content block. It's Google's proxy for "how long until the page looks done."
Good is under 2.5 seconds. Bad is over 4. The targets are real, not aspirational. If your LCP is 5 seconds, Google's telling you something.
When a user clicks, taps, or types, how long until the page visibly responds. Replaces an older metric called FID in 2024. INP is harsher because it looks at the worst interaction during the whole session, not just the first.
Good is under 200ms. Anything over 500ms feels broken to users. INP is where over-engineered single-page apps and heavy JavaScript frameworks get caught.
How much the page moves around while loading. You know when you're about to click a button and then an ad loads and pushes everything down and you click the wrong thing? That's CLS, and Google measures it.
Good is under 0.1. Bad is over 0.25. The fix is usually just telling the browser ahead of time how much space to reserve for images, ads, and dynamic content.
Less than people claim, more than people think. A great page with poor CWV usually still outranks a mediocre page with perfect CWV. The signal isn't weighted heavily enough to flip dominant rankings. But when two pages are close, CWV decides.
The real reason to fix CWV isn't SEO. It's conversion. Every 100ms of added load time drops conversion by about 1% on average. Slow pages cost money directly, regardless of rank. Fixing CWV is one of the rare SEO projects that also pays off instantly in revenue.
There are two completely different ways to measure CWV, and confusing them is the number-one reason people mis-fix their sites.
If your field data looks fine and your lab data looks bad, your users are fine. If your lab data looks fine and your field data looks bad, your users are suffering and you're not replicating their conditions in testing.
Don't try to chase perfect scores everywhere. The returns are wildly diminishing past "Good."
Open Search Console now. Check the Core Web Vitals report. If everything's green, move on. If you have URLs in the Poor bucket, note which metric is failing and plan a fix sprint. Don't make it a side project, block a real week for it. Speed is one of the few SEO investments that pays off both in rank and in conversion at the same time.
Next: E-E-A-T explained, the trust framework Google uses to evaluate whether your site is a credible source.