Core Web Vitals are the three measurements Google uses to score how fast and stable a webpage actually feels to a real visitor: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). They matter for two very practical reasons. First, a slow or jumpy page pushes visitors to leave before they ever see your offer, your form, or your product — that is lost revenue, not a technical footnote. Second, Google uses these same scores as a ranking signal, so a site that fails Core Web Vitals can rank below a competitor with a faster one, even with weaker content. Here is what each metric actually means and what usually causes the problem.
What LCP, CLS and INP actually measure
Forget the acronyms for a second and think about what a visitor experiences. LCP asks a simple question: how long until the main thing on the page — a hero image, a headline, a product photo — actually appears? If someone taps a link and stares at a blank or half-loaded screen for three or four seconds, that is a failing LCP. Google's bar is 2.5 seconds.
CLS is the "why does this keep jumping around" problem. A page loads its text first, then an image, an ad, or a cookie banner pops in above it and shoves everything down — right as someone was about to tap a button, so they hit the wrong thing instead. That is a bad CLS score, and it is one of the most common reasons people accidentally click the wrong link on a mobile site.
INP measures responsiveness: when someone taps a button, fills in a form field, or opens a menu, how long until the page actually reacts? A site that loaded quickly but feels sluggish or unresponsive to taps has a bad INP — and that lag is often what makes a page feel "cheap" even when nothing is technically broken.
Why a slow site quietly costs you customers
Visitors do not file a complaint about a slow site — they just leave, and you never see them again. Studies from Google and major retailers consistently show conversion rates drop sharply for every extra second before a page becomes usable, and the drop-off is worse on mobile, where patience is shortest and connections are slower. Speed also shapes trust before a single word is read: a page that appears instantly feels professional and reliable, while one that stutters and shifts feels amateur, even if the business behind it is not. For a site whose job is to turn visitors into bookings, leads, or sales, that first impression is the whole game.
Why Google cares about your site's speed
Core Web Vitals have been an official part of Google's ranking signals since 2021, folded into what Google calls "page experience." The logic is straightforward: Google wants to send searchers to pages that will not frustrate them. Between two pages with similar content, the faster, more stable one tends to get the edge — speed is rarely the single deciding factor, but it is consistently a tie-breaker, and on competitive keywords tie-breakers are what separate page one from page two.
Common causes hiding on most business websites
- Huge, unoptimized images — photos uploaded straight from a phone or camera, several megabytes each, with no compression or resizing.
- Render-blocking fonts and scripts — custom fonts, tracking pixels, and chat widgets that the browser must fully load before it shows anything at all.
- No server-side rendering — the page ships as a blank shell and builds itself in the visitor's browser using JavaScript, so there is nothing to see until that finishes.
- Third-party embeds stacking up — ads, popups, review widgets and analytics scripts added one at a time over the years, each adding its own delay.
- No caching or CDN — every visitor, everywhere in the world, waits on the same slow trip back to a single server.
How to check your own site — no technical knowledge required
You do not need a developer to see where you stand. Go to PageSpeed Insights (pagespeed.web.dev), paste in your homepage or any important page, and run the test. It returns a score out of 100 plus a color-coded breakdown of LCP, CLS and INP for both mobile and desktop — green means good, orange means needs improvement, red means it is likely costing you visitors. Check the mobile score first; most traffic and most Google indexing decisions are mobile-based, and mobile scores are almost always worse than desktop.
A five-minute self-check
Run your homepage through PageSpeed Insights on mobile. If LCP is over 4 seconds, CLS is above 0.25, or the overall score is red, your site is very likely losing you customers and ranking — and the fix is usually a specific, fixable list, not a full rebuild.
What to do once you know your score
If your scores are red, resist the urge to panic-rebuild the whole site. Start with the highest-impact, lowest-effort fixes: compress and resize images before uploading, remove chat widgets or plugins you no longer use, reserve space for images and ads so they don't shove content around, and load fonts and non-essential scripts after the main content appears. If the site is built without server-side rendering, that is a bigger structural fix worth discussing with whoever built it — it is often the single biggest lever for LCP on content-heavy sites.
Frequently asked questions
What is a good Core Web Vitals score?
Google's targets are LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds. Hitting all three on both mobile and desktop puts you in the "good" tier Google looks for.
Do Core Web Vitals really affect Google rankings?
Yes, but as one signal among many — strong content on a slow site can still outrank thin content on a fast one. Speed matters most as a tie-breaker between otherwise similar pages, which is common on competitive keywords.
Can I fix Core Web Vitals myself without a developer?
Some of it, yes — compressing images and removing unused plugins or embeds goes a long way on platforms like WordPress or Shopify. Structural fixes, like adding server-side rendering, need a developer.
How often should I check my Core Web Vitals?
Check after any major site change — a new plugin, a redesign, a new ad or chat script — and do a routine check every couple of months, since third-party scripts tend to accumulate and slow a site down over time.