Core Web Vitals: how site speed affects sales

Core Web Vitals are three Google metrics that measure how fast a page loads, how quickly it responds to clicks and whether its layout jumps around while loading. For a business, this is not just a topic for developers: a slow site means abandoned forms, unfinished checkouts and a weaker first impression. This article explains exactly what Core Web Vitals measure, how to check your own scores and what to fix first so the work shows up in sales.

Key takeaways

• Core Web Vitals consist of three metrics: LCP (loading), INP (responsiveness) and CLS (layout stability).
• Good scores are LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1, measured at the 75th percentile of real visits.
• Google assesses pages using field data from real Chrome users, not the result of a single Lighthouse test.
• Page speed is one ranking signal among many and will not compensate for weak, irrelevant content.
• The most common culprits are heavy images, too many third-party scripts and elements with no reserved space.

What are Core Web Vitals?

Core Web Vitals are the subset of Google’s Web Vitals that it considers essential to user experience. Each metric answers a question visitors ask themselves, without thinking about it, in the first seconds of a visit.

LCP — has the page loaded yet?

LCP (Largest Contentful Paint) is the time until the largest visible element appears on screen — usually the hero image or the main heading. It is the moment a user decides the page is “there”.

INP — does the page respond?

INP (Interaction to Next Paint) is the delay between an interaction — a click, a tap, a keystroke — and a visible response. INP replaced the older FID metric in March 2024. A high INP makes a “Submit” button feel broken, so people click it several times.

CLS — is the layout stable?

CLS (Cumulative Layout Shift) is a measure of unexpected movement of page elements. The classic example: you go to tap a link, a banner loads above it at the last moment, and you hit something else.

Core Web Vitals thresholds at a glance

Metric	What it measures	Good	Needs improvement	Poor
LCP	main content loading	≤ 2.5 s	2.5–4 s	> 4 s
INP	response to interactions	≤ 200 ms	200–500 ms	> 500 ms
CLS	layout stability	≤ 0.1	0.1–0.25	> 0.25

A page passes when at least 75% of visits fall within the “good” range for all three metrics — assessed separately for mobile and desktop.

How site speed affects sales

The link between speed and conversion is intuitive, but understanding the mechanism tells you what to fix first:

• First impressions. If people stare at a blank screen for several seconds, some go back to the search results and pick a competitor before they ever see your offer.
• Trust. A page that shifts and lags looks neglected. On a contact form or a payment step, that is a real barrier.
• Friction at key moments. Poor INP hurts most where users act: filters, the cart, forms. Those are exactly the screens that decide conversion.
• Mobile traffic. Phones have slower processors and connections than the laptop you test on. Mobile scores are usually worse, and they deserve attention first.

Rather than leaning on other people’s statistics, check your own data. In Google Analytics, compare conversion rates on your fastest and slowest pages, or before and after an optimisation. That tells you more than any industry-wide figure.

Core Web Vitals and Google rankings

Core Web Vitals are part of the “page experience” signals Google uses in ranking. Their weight is limited: between two equally useful pages, the faster one may win, but speed will not lift thin content. Treat optimisation primarily as a conversion investment, with the SEO benefit as a bonus.

How to measure Core Web Vitals

Distinguish two kinds of data. Field data comes from real Chrome users (the CrUX report) and is what Google’s assessment is based on. Lab data is a simulated single page load — useful for diagnosis, but not always representative.

• PageSpeed Insights (pagespeed.web.dev) shows field data if the page has enough traffic, plus a lab test with recommendations.
• Google Search Console, in the Core Web Vitals report, groups URLs with similar issues and shows trends over time.
• Chrome DevTools, via the Lighthouse and Performance panels, lets you dig into what blocks loading or interactions.

Field data is aggregated over the previous 28 days, so after shipping fixes, give it a few weeks before judging the result in Search Console.

How to improve Core Web Vitals: a checklist

LCP

• compress images and use modern formats such as WebP;
• serve images sized for the screen with srcset and sizes;
• never lazy-load the hero image;
• cut server response time with caching and a CDN — a network of servers close to your users;
• reduce render-blocking CSS and fonts.

INP

• audit third-party scripts: chat widgets, heatmaps, ad pixels — each one adds work for the browser;
• load non-critical scripts with defer, or only after user interaction;
• break long JavaScript tasks into smaller chunks;
• clean out unused tags in Google Tag Manager.

CLS

• give images and embeds explicit dimensions (width, height or aspect-ratio);
• reserve space for banners, ads and the cookie banner;
• use font-display: swap with a fallback font of similar proportions;
• never insert content above what is already visible, unless the user asked for it.

Where to start

Don’t try to fix everything at once. Pick the templates with the most traffic and commercial value — homepage, service pages, product page, contact form — and start with their weakest metric. A single template fix improves hundreds of pages at once.

LessCMS and Core Web Vitals

Many factors behind Core Web Vitals depend on infrastructure rather than content. With LessCMS, several are handled from day one:

• pages are server-side rendered (SSR) and served from Cloudflare’s edge network, close to your visitors;
• the cache is purged automatically by tag on publish, so a fast CDN copy never means stale content;
• images uploaded to the media library are automatically optimised to WebP;
• GA, GTM and custom head scripts live in one place, which makes it easier to control what actually loads.

Your own choices — the number of third-party scripts, the size of videos — still affect the result, so keep measuring. Read more about the technical foundations on SEO in LessCMS, or, if you build your own front end, see the headless API.

Frequently asked questions

How do I check my site’s Core Web Vitals?

The quickest way is to paste a URL into PageSpeed Insights, which shows real-user data alongside a lab test. For the whole site, use the Core Web Vitals report in Google Search Console. Both tools are free.

Why does PageSpeed Insights show different results from Search Console?

PageSpeed Insights assesses a single URL, while Search Console groups similar URLs and shows 28 days of data. The Lighthouse performance score (0–100) comes from a simulation and is not the same as the Core Web Vitals assessment. Field data from real users is what counts.

Do Core Web Vitals affect Google rankings?

Yes, but modestly — they are one signal among many, and relevance still matters more. Their bigger payoff is higher conversion and fewer abandoned visits.

What usually causes a poor INP score?

A poor INP is most often caused by too much JavaScript, especially third-party scripts such as chat widgets, analytics tools and ad pixels. Auditing your tags and removing unused ones usually brings the fastest improvement.

How long until Core Web Vitals improvements show up?

Lab tests reflect changes immediately, but field data in Search Console updates gradually over a 28-day window. Expect to judge the real effect three to four weeks after deploying fixes.

Want to see how a site built on LessCMS performs? Pick a plan on the pricing page and create an account without a card.