Core Web Vitals Explained: What They Mean for Your Revenue

Your website’s speed isn’t a technical metric – it’s a business metric. Core Web Vitals are Google’s way of measuring how a real user experiences your site: how fast it loads, how quickly it responds, and whether the layout jumps around as it does. Get them right and you rank better, convert more, and spend less on ads. Get them wrong and you’re quietly paying a penalty every single day.

In this post we break down what each metric actually means, why it matters commercially, what scores you should be aiming for, and what typically causes poor performance. So you can have an informed conversation with whoever is managing your website.

What Are Core Web Vitals?

Core Web Vitals (CWV) are a set of performance metrics defined by Google that measure real-world user experience. They’ve been a confirmed Google ranking signal since 2021 which means they directly affect where you appear in search results.

There are three metrics. Each one measures a distinct aspect of how a page feels to a real user:

The Three Metrics, Explained

LCP — Largest Contentful Paint

LCP measures how long it takes for the largest visible element on your page (usually a hero image, headline, or banner) to fully load. It’s the closest thing CWV has to a ‘first impression’ metric.

Think of it this way: a user lands on your homepage and sees a white screen for three seconds before anything appears. They don’t know if the page is loading or broken. LCP is measuring exactly that window.

Why it matters commercially

Google uses LCP as a proxy for page load quality. A slow LCP damages your search rankings directly. It also affects PPC: Google Ads uses landing page experience as part of Quality Score — a poor score means you pay more per click for the same position.

–

Common causes of poor LCP:

• Unoptimised images (wrong format, wrong size, not lazy-loaded correctly)
• Slow server response times (cheap shared hosting is a common culprit)
• Render-blocking JavaScript or CSS delaying the page from displaying
• No caching layer in place

INP — Interaction to Next Paint

INP replaced FID (First Input Delay) as a Core Web Vital in March 2024. Where FID only measured the delay before the browser started responding to the very first interaction, INP measures responsiveness across the entire page visit: every click, tap, and keypress.

If a user clicks a button on your site and nothing visibly happens for half a second, that registers as a poor INP. On a form, a product filter, or a checkout step, that delay is the moment a user starts questioning whether it worked.

Why it matters commercially

Poor INP is particularly damaging on ecommerce and lead-gen sites. Slow form responses, unresponsive filters, and laggy CTAs all erode trust and directly reduce conversion rates. If you’re running paid traffic to a sluggish landing page, you’re paying to frustrate people.

–

Common causes of poor INP:

• Heavy JavaScript executing on the main thread (blocking interaction)
• Third-party scripts — analytics, chat widgets, ad trackers — competing for resources
• Poorly built WordPress page builder output generating excessive JS
• Lack of code-splitting or deferred script loading

CLS — Cumulative Layout Shift

CLS measures visual stability. Specifically, how much the page layout moves around as it loads. If you’ve ever tried to click a button and the page jumped so you tapped something else instead, that’s a layout shift in action.

CLS is scored between 0 (no shifting) and higher numbers representing worse instability. A score under 0.1 is considered good. Anything over 0.25 is poor.

Why it matters commercially

CLS is the metric most directly tied to user frustration and accidental clicks. On mobile — where most of your traffic likely arrives — layout shifts cause misclicks, failed form submissions, and users abandoning the page entirely. It’s also a direct Google ranking signal, so a high CLS score is hurting your organic visibility.

–

Common causes of poor CLS:

• Images without explicit width and height dimensions defined
• Web fonts causing text to reflow as they load (FOUT – Flash of Unstyled Text)
• Ads, embeds, or iframes loading and pushing content down
• Dynamically injected content above existing page content

What Do the Scores Actually Mean?

Google scores each metric in one of three bands. To pass the Core Web Vitals assessment — and receive the ranking benefit — a site needs to hit the ‘Good’ threshold on all three metrics for at least 75% of real-world page visits.

The 90+ score you’ll see referenced in our work (including our Agitate 99 guarantee) refers to Google PageSpeed Insights — the tool that translates these field metrics into a 0–100 score. A score of 90+ means you’re comfortably inside ‘Good’ territory on all three metrics. The average site scores between 20 and 40. Even well-built sites often struggle to break 70.

The Agitate 99 guarantee

Every site we build launches with a minimum 90+ PageSpeed score across all Core Web Vitals. We aim for 99. If we don’t hit 90+, we fix it at no additional cost. It’s not a marketing line — it’s how we’ve built every project since we started.

Why Most Sites Are Slow — And Why It’s Not Random

The reason the average site scores 20–40 isn’t that developers are careless. It’s that most websites are built with the wrong priorities. Speed is treated as something to bolt on at the end, if there’s time.

Here are the patterns we see repeatedly when we audit underperforming sites:

1. Page builders doing the heavy lifting

Elementor, WPBakery, Divi, Wix, Squarespace and similar tools make it easy to build pages, but they output enormous amounts of CSS and JavaScript — much of it unused. A page that looks simple might be loading hundreds of kilobytes of builder code that has nothing to do with what’s on the screen.

2. Unoptimised images

Images are usually the single biggest contributor to slow LCP. Uploading a 4MB photograph and letting WordPress handle it is not optimisation. Images need to be correctly sized for the device they’ll appear on, converted to modern formats (WebP or AVIF), and loaded at the right time.

3. Third-party scripts

Every marketing tool you add to a site — Google Analytics, Meta Pixel, HubSpot, Hotjar, Intercom, live chat — comes with JavaScript that loads on every page visit. Individually, each is manageable. Together, they can add seconds to your load time and badly damage INP scores. Most sites have no strategy for managing this.

4. Cheap hosting

Shared hosting providers offer low prices because you’re sharing a server with hundreds of other websites. Your server response time — how quickly the server even starts sending data — is a core component of LCP. No amount of front-end optimisation fully compensates for a slow server.

5. Performance as an afterthought

The most consistent cause of poor scores is treating performance as the last step rather than the first. Design decisions, plugin choices, and development approaches all affect performance. If those choices are made without performance in mind, fixing them later is significantly harder and more expensive.

The Business Case: What Better Scores Are Actually Worth

It’s easy to treat Core Web Vitals as a technical checkbox. The real question is what passing — or failing — is worth in commercial terms.

SEO and organic rankings

Google uses Core Web Vitals as a tiebreaker when other ranking signals are equal. In competitive markets where the top results are all high-quality, authoritative pages, page experience — including CWV — is what separates position 3 from position 8. The difference in click-through rate between those positions can be 2–3x.

PPC and paid media efficiency

Google Ads uses landing page experience as part of its Quality Score calculation. A lower Quality Score means a higher cost per click for the same ad position. A site with a poor PageSpeed score — particularly on mobile — is likely paying a meaningful premium on every click. If you’re spending £5k–£50k a month on paid media, the compounding cost of a slow landing page is significant.

Conversion rate

The research on speed and conversion is consistent: faster pages convert better. Google’s own data shows that as page load time goes from 1 second to 3 seconds, the probability of a user bouncing increases by 32%. By 5 seconds, that figure reaches 90%. For an ecommerce site or a lead-gen page, every fraction of a second has a measurable impact on revenue.

Brand perception

A slow website signals something about the business behind it. It’s not a conscious judgment by users — it’s instinctive. Fast, stable, responsive experiences build trust. Slow, jumpy experiences erode it. In professional services especially, where trust is the product, this matters more than most businesses realise.

How to Check Your Scores

You don’t need to hire anyone to get a baseline. These tools give you a clear picture:

• Google PageSpeed Insights (pagespeed.web.dev) — the primary tool, uses real-world Chrome data where available
• Google Search Console → Core Web Vitals report — shows your actual field data aggregated across all visitors
• GTmetrix — useful for waterfall analysis to identify exactly what’s causing slow load times
• WebPageTest — more detailed diagnostic tool for technical teams

A few things to know when reading your scores:

• Test on mobile as well as desktop. Mobile scores are almost always lower and are weighted more heavily by Google.
• Test your actual landing pages, not just the homepage. Blog posts, product pages, and campaign pages often perform very differently.
• Look at the field data (real user data) not just the lab data. Field data is what Google actually uses for rankings.

More questions or want to know where your site stands?

Learn more about our website speed optimisation services or reach out to arrange a call or a coffee.