What Core Web Vitals Actually Mean for Your Business

Google says Core Web Vitals matter. Your developer mentions them in monthly reports. You've seen the scores in PageSpeed Insights. But nobody has explained what actually happens to your revenue when these numbers are bad.

This post isn't a technical deep dive into browser rendering pipelines. It's a translation of three technical metrics into the business outcomes that pay your bills: conversion rates, bounce rates, and search rankings.

The Three Core Web Vitals in Plain English

Core Web Vitals are three specific measurements that Google uses as ranking signals. They've been part of the ranking algorithm since 2021, and their weight has increased with each update.

Largest Contentful Paint (LCP) — How Fast Your Main Content Appears

LCP measures the time from when a user clicks your link to when the largest visible element on the page finishes loading. This is usually your hero image, a heading, or the first block of text. It's the moment a visitor stops seeing a blank screen and starts seeing your content.

Google's threshold: Under 2.5 seconds = good. 2.5-4 seconds = needs improvement. Over 4 seconds = poor.

What it means for your business: Every additional second of LCP increases your bounce rate. Users don't wait. If your competitor's page loads in 1.5 seconds and yours loads in 4 seconds, the visitor has already formed an impression of your competitor's offering before your page has even appeared.

Interaction to Next Paint (INP) — How Quickly Your Page Responds

INP replaced First Input Delay (FID) in March 2024. It measures the delay between when a user interacts with your page — clicking a button, tapping a menu, selecting a form field — and when the browser visually responds. It captures the worst responsiveness experience during the entire page visit, not just the first interaction.

Google's threshold: Under 200 milliseconds = good. 200-500ms = needs improvement. Over 500ms = poor.

What it means for your business: When a user clicks "Add to Basket" and nothing happens for half a second, they click again. Now they've added two items, or they've become frustrated, or they've left entirely. Unresponsive interfaces feel broken — and users don't buy from websites that feel broken.

Cumulative Layout Shift (CLS) — How Much Your Page Jumps Around

CLS measures how much visible content moves unexpectedly during loading. You've experienced this: you're about to click a link, an ad loads above it, the page shifts, and you click the wrong thing. That's layout shift.

Google's threshold: Under 0.1 = good. 0.1-0.25 = needs improvement. Over 0.25 = poor.

What it means for your business: Layout shift causes accidental clicks, disrupts reading flow, and makes your site feel unstable. On mobile — where most of your traffic probably comes from — it's especially noticeable. Users who experience significant layout shift are less likely to complete a purchase or fill out a contact form.

The Revenue Impact: What the Research Shows

The business case for Core Web Vitals isn't theoretical. Multiple large-scale studies have quantified the relationship between performance and revenue:

Google/Deloitte: Speed Equals Revenue

A joint study by Google and Deloitte analysed 37 European and American brands across retail and travel. They found that a 0.1-second improvement in mobile load speed increased conversion rates by 8% for retail sites and 10% for travel sites. That's not a 1-second improvement — it's one-tenth of a second.

For a retail site doing £100,000 per month in online revenue, an 8% conversion rate increase from a 0.1-second speed improvement translates to £8,000 per month in additional revenue — £96,000 per year.

Vodafone: LCP and Sales

Vodafone optimised their LCP by 31% and saw an 8% increase in sales. They also observed a 15% improvement in their lead-to-visit rate and an 11% improvement in their cart-to-visit rate. The changes that improved LCP — primarily image optimisation and critical path improvements — cost a fraction of what the revenue increase delivered.

Yahoo! JAPAN: INP and Revenue

When Yahoo! JAPAN reduced their INP score, they measured a direct correlation between faster interaction response and higher page views per session. Users who experienced responsive pages explored more content, clicked more links, and generated more ad impressions.

The HTTP Archive: Industry Averages

The HTTP Archive tracks performance metrics across millions of websites. As of late 2025, the median LCP for UK mobile sites was approximately 3.8 seconds — well above Google's 2.5-second threshold. This means most UK businesses are in the "needs improvement" or "poor" category, which affects both their rankings and their conversion rates.

How to Check Your Own Scores

You don't need a developer to check your Core Web Vitals. Here are three ways to see where you stand:

1. Google PageSpeed Insights — Enter your URL at pagespeed.web.dev. The tool shows both "field data" (real user measurements from the Chrome User Experience Report) and "lab data" (simulated tests). Field data is what Google uses for rankings; lab data is useful for diagnosing specific problems.
2. Google Search Console — If you have Search Console set up, the "Core Web Vitals" report shows which pages pass and fail, with specific problem areas highlighted.
3. Our free P.E.E.R. scanner — Run a free mini P.E.E.R. review to get your Core Web Vitals alongside performance, emissions, and ranking scores in a single analysis.

What "Good" Scores Look Like for UK Businesses

Based on our P.E.E.R. framework data from UK websites:

• Excellent (A grade): LCP under 1.5s, INP under 100ms, CLS under 0.05. These sites load almost instantly. Users don't wait, don't experience jank, and don't see layout shifts. Conversion rates are measurably higher than competitors.
• Good (B grade): LCP under 2.5s, INP under 200ms, CLS under 0.1. These sites meet Google's thresholds. They won't lose rankings due to performance, but they're not gaining a competitive advantage either.
• Problematic (C-D grade): LCP 2.5-4s, INP 200-500ms, CLS 0.1-0.25. These sites are actively losing rankings and conversions. Google flags them as "needs improvement" in Search Console.
• Critical (F grade): LCP over 4s, INP over 500ms, CLS over 0.25. These sites are penalised in rankings and haemorrhaging potential customers. Most WordPress sites with heavy themes, unoptimised images, and multiple plugins fall into this category.

Our whitepaper research confirms this distribution. When we audited 20 UK B Corp websites, the majority fell into the C-D range despite being professionally designed. The average page weight was over 4MB — the primary driver of poor LCP scores.

Quick Fixes vs Structural Problems

Some Core Web Vitals problems have quick fixes. Others require structural changes. Here's how to tell the difference:

Quick Fixes (Days, Not Weeks)

• Image optimisation — Convert images to WebP, serve at appropriate dimensions, add width and height attributes. This is the single biggest LCP improvement for most sites.
• Font loading strategy — Add font-display: swap to prevent invisible text. Preload your primary font. Remove font weights you don't use.
• Third-party script deferral — Move non-critical scripts to load after the main content. Analytics, chat widgets, and tracking pixels don't need to block your page render.
• Explicit image/iframe dimensions — Adding width and height to every <img> and <iframe> eliminates the most common source of CLS.

Structural Problems (Require Architecture Changes)

• Heavy JavaScript frameworks — If your site ships 1MB+ of JavaScript, no amount of deferral will fix INP. The framework itself is the problem.
• Server response time — If your server takes 2+ seconds to respond (Time to First Byte), your LCP can never be good. This usually requires hosting migration or server-side caching.
• Render-blocking CSS — Large, monolithic stylesheets that block rendering need to be split into critical and non-critical CSS. This often requires build tooling changes.
• WordPress with heavy themes — Many premium WordPress themes ship 3-5MB of CSS and JavaScript. Switching themes or migrating to a performance-first platform may be the only viable fix.

What This Means for Your Next Decision

If you're about to commission a new website, make Core Web Vitals part of the specification. Include specific targets: LCP under 2 seconds, INP under 150ms, CLS under 0.05. Ask your agency to demonstrate these scores on their own website first. If they can't achieve good scores on their own site, they won't achieve them on yours.

If you have an existing website with poor Core Web Vitals, start with a P.E.E.R. audit to identify whether you're dealing with quick fixes or structural problems. Quick fixes can often double your performance scores. Structural problems may require a phased improvement plan or a rebuild.

Either way, the business case is clear: faster websites convert better, rank higher, and cost less to run. Core Web Vitals aren't abstract technical metrics — they're the measurement of whether your website is helping or hindering your business.