Core Web Vitals: why a slow website costs you leads

Core Web Vitals sound like a developer concern, and most of the writing about them is aimed at developers. But the underlying idea is simple and entirely commercial: Google measures whether your site feels good to use, because sites that feel bad get abandoned.

Here's what the three metrics mean without the jargon, and which fixes are worth your money.

The three metrics in plain English

LCP: how fast the main thing shows up

Largest Contentful Paint measures how long it takes for the biggest element on screen (usually your hero image or headline) to appear. Google considers 2.5 seconds or less to be good.

This is the metric visitors feel most directly. A slow LCP is the blank white screen while someone waits and reconsiders.

INP: how fast the page reacts to you

Interaction to Next Paint measures the delay between a tap or click and the page visibly responding. Under 200 milliseconds is good.

Bad INP is the menu button you press twice because nothing happened the first time. It's the metric that makes a site feel cheap even when it looks expensive.

CLS: how much the page jumps around

Cumulative Layout Shift measures unexpected movement while the page loads. Under 0.1 is good.

This is the one everybody has suffered: you go to tap a link, an image finishes loading above it, everything shifts down, and you tap an ad instead. On a booking form it's the difference between a customer and a bounce.

Why this is a business problem, not a technical one

Two separate consequences, and the second is the bigger one.

First, ranking. Core Web Vitals feed Google's page experience signals. They will not rescue thin content, but between two comparable pages the faster one has an advantage, and in local search your competitors are often very comparable.

Second, conversion. This is where the actual money is. Every extra second before your page becomes usable loses a slice of the people who were going to contact you. They don't complain, they don't bounce dramatically. They just quietly go back to the results page and pick someone else. You never see it in your analytics as a lost lead, because it never became one.

The fixes that move the needle

In rough order of impact per hour spent:

1. 01Fix your images. This is far and away the biggest win on most small business sites. Serve modern formats, size them correctly for the device, and never ship a 4000px photo to a phone. Always set explicit width and height so the space is reserved before the image arrives. That alone fixes most CLS problems.
2. 02Cut third-party scripts. Every chat widget, tracking pixel, heatmap, and social embed costs you. Audit what's loading and delete anything nobody has looked at in six months. This is usually the single largest INP improvement available.
3. 03Reserve space for anything that loads late. Ads, embeds, banners, fonts. If it appears after the page renders, give it a reserved slot so nothing shifts.
4. 04Handle fonts deliberately. Use font-display: swap and preload the ones you need. Invisible text while a font downloads is a real LCP penalty.
5. 05Host sensibly and use a CDN. Cheap shared hosting shows up directly in server response time, which delays everything downstream.
6. 06Lazy-load below the fold, but never the hero. Lazy-loading your main hero image is a classic self-inflicted LCP wound.

How to check yours

PageSpeed Insights gives you both a lab test and, if you have enough traffic, real field data. Search Console has a Core Web Vitals report covering your whole site rather than one page at a time. That's the one to watch over time, because it tells you which templates are the problem rather than which single URL.

Test on a real phone on mobile data before you conclude anything. The gap between your office wifi and a customer's commute is where most of these problems hide.

If you'd rather not dig through it yourself, we'll audit your site's performance for free and tell you exactly what's slowing it down. Send us your website. That's all we need to start.