Core Web Vitals: Why Site Speed Affects Your Revenue

Core Web Vitals are a set of measurements Google uses to judge how fast, stable and responsive your site feels to real visitors. They matter because they affect both your search rankings and whether visitors stay long enough to buy. This guide explains them in business terms, without the engineering.

What do Core Web Vitals measure?

Core Web Vitals measure how quickly the main content appears, how fast the page responds when someone interacts, and whether the layout stays still while it loads. Each has a name and a target, and Google’s web.dev resources define the exact thresholds:

• Largest Contentful Paint (LCP) is loading speed: the time until the biggest element on screen, usually the main image or headline, appears. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP) is responsiveness: how quickly the page reacts when someone taps a button or opens a menu. Good is 200 milliseconds or less. It replaced an older measure, First Input Delay, in 2024.
• Cumulative Layout Shift (CLS) is visual stability: how much things jump around as the page loads. Good is a score of 0.1 or less.

Google assesses each one at the 75th percentile of real visits, separately for mobile and desktop. In plain terms, at least three in four visits need to hit the target.

How do Core Web Vitals affect revenue?

They affect revenue because visitors abandon slow pages, and every second of delay costs conversions, especially on phones. A site that feels sluggish or jumps around as it loads frustrates people before they ever see your offer. A layout shift that moves a button just as someone taps it turns a purchase into a mis-tap.

Improving these scores keeps more visitors moving toward a purchase, which is why Core Web Vitals belong on a business dashboard as well as a developer’s screen. You can check the effect in your own numbers: note the date of each speed fix in your analytics, then compare conversion rates on those pages before and after.

Do Core Web Vitals affect Google rankings?

Yes. Google uses these measurements as a ranking signal. When two sites are otherwise similar, the faster, more stable one tends to win the higher position. Good Core Web Vitals will not rescue weak content, but poor ones can quietly hold back pages that deserve to rank.

How do you check your Core Web Vitals?

Two free Google tools cover most needs: PageSpeed Insights and Search Console. PageSpeed Insights tests any page in seconds and shows two kinds of data: field data from real Chrome visitors over the previous 28 days, and lab data from a simulated test. Field data reflects what your visitors actually experience; lab data is for debugging. Pages without enough traffic fall back to figures for the whole site, or show no field data at all.

Search Console’s Core Web Vitals report sorts your pages into Poor, Need improvement and Good, for mobile and desktop separately, and groups similar pages so you can see which templates need work. If you haven’t set it up, our guide to Google Search Console walks through it.

Because field data covers four weeks, a fix takes about that long to show fully. Don’t judge a change after two days.

What usually fixes poor Core Web Vitals?

The common culprits are heavy images, bloated plugins, slow hosting and code that loads in the wrong order. Each measure has its usual suspects:

• Slow LCP: compress the main image, serve it at the right size, make sure it isn’t set to load late, and look at hosting and caching.
• Poor INP: cut third-party scripts such as chat widgets and trackers, and remove plugins that run heavy code on every page.
• High CLS: set a width and height on images and embeds, and reserve space for banners before they load.

The cheap fixes, like compressing images and trimming unused plugins, often produce a noticeable jump, and better hosting can add another. Measure first, fix the biggest offenders, then measure again. Start with the pages that earn money, such as product and service pages, and fix problems at the template level, because one change there fixes every page built on it. Our guide to page speed goes deeper on each fix.

Frequently asked questions

Do Core Web Vitals really affect SEO?

Yes, as one signal among many. They matter most when other factors are close. Relevant, useful content still comes first.

Why do my scores differ between tools?

Some tools run a single simulated test (lab data), while Google’s field data reports what real visitors experienced over the past 28 days. Lab scores vary between runs; field data moves slowly. Judge your site on field data and use lab results to find the cause.

Is a perfect score necessary?

No. Aim for the “good” range; chasing a flawless number rarely pays off. Once a page passes all three, your time is usually better spent on content and conversion.

Who should fix these?

A developer usually handles the technical fixes, guided by what the measurements flag. Your part is deciding which pages matter most and approving trade-offs, like removing a slow third-party widget.

Turn speed into sales

Strong Core Web Vitals keep visitors engaged and help your pages rank. A sensible next step: run your three most valuable pages through PageSpeed Insights, note which measure fails on mobile, and fix that one first. Our Development & Engineering team diagnoses what slows your site and fixes the issues that cost you customers.