Core Web Vitals: Why a Slow Website Is Quietly Killing Your Lead Generation

March 27, 2026

Most business owners think their website is “pretty fast.” The reality, when we audit client sites, is that about 70% of small-business websites fail at least one of Google’s Core Web Vitals thresholds. They’re not broken — they’re just slow enough to lose leads invisibly.

This matters for two reasons: Google uses these metrics as a ranking signal, and — more importantly — visitors don’t wait. If your home page takes 4.5 seconds to become usable, you’ve already lost roughly a quarter of the people who clicked.

What Core Web Vitals Actually Are

LCP — Largest Contentful Paint

How long until the biggest thing on screen (usually a hero image or headline) is visible. Good: under 2.5 seconds. This is the “is this site loading or not?” metric.

INP — Interaction to Next Paint

When a user taps or clicks, how long until the page visibly responds. Good: under 200 milliseconds. It replaced First Input Delay in 2024 and catches janky interactions throughout the visit.

CLS — Cumulative Layout Shift

How much things jump around as the page loads. Good: under 0.1. You’ve experienced this: you go to tap a button, an ad loads above it, and you tap the ad instead.

The Business Case — in Actual Numbers

For a business doing $500k/year through its website, the difference between a mediocre and a good site is often $50k–$100k annually — and it happens invisibly. You never get an invoice for slow-page losses.

What Actually Causes Bad Web Vitals

1. Unoptimised images (the #1 culprit)

Someone uploads a 4MB phone photo; the site shrinks it visually but serves the full file. Fix: use WebP or AVIF, resize to display size, use srcset, lazy-load below-the-fold images.

2. Third-party scripts

Every tag — Facebook Pixel, chat widgets, analytics, heatmaps — is another request and source of layout shift. Most sites have 8–15; most need 3–5. Fix: audit, remove, consolidate, defer.

3. Render-blocking CSS and JavaScript

Bad themes and bloated page builders can add 500KB of CSS the user never needs. Fix: inline critical CSS, defer the rest, avoid kitchen-sink page-builder plugins.

4. Web fonts

Four weights of two Google fonts is 200KB+ and a flash of invisible text. Fix: self-host fonts, use font-display: swap, preload critical weights.

5. Cheap shared hosting

If your host runs 500 sites on one machine, your Time To First Byte is 1.5 seconds before you’ve done anything. Fix: move to reputable managed hosting or a modern platform.

6. No CDN / edge caching

A visitor in Toronto shouldn’t fetch your image from Arizona. Fix: put Cloudflare or another CDN in front of your site — most of it is free.

The Quick Diagnostic

Go to pagespeed.web.dev and plug in your home page URL. You’ll get specific recommendations with file names and sizes — the same tool Google uses internally, free.

What “Fast” Looks Like in 2026

These aren’t aspirational — they’re what a well-built WordPress site or a statically-generated Next.js/Astro site achieves by default. If you’re nowhere near them, you have technical debt in the theme, plugins, or hosting.

When to Optimise vs Rebuild

If your site is under 3 years old on a reasonable platform, optimise. If it’s on an ancient page builder, loaded with 40+ plugins, on shared hosting, or customised by five different developers — rebuild. You’ll spend more chasing incremental gains than starting clean. If you want to know which camp you’re in, we run free technical audits covering performance, SEO, and security in one go.