Core Web Vitals Explained: Why a Fast Website Sells More
Core Web Vitals are three Google metrics that show whether your website loads fast (LCP), responds quickly to taps and clicks (INP) and stays visually stable while it loads (CLS). To pass, a page needs an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, according to web.dev, Google's developer site. And a faster website sells more for a simple reason: customers reach your offer before they give up, something real-world tests at large companies have measured.
What are Core Web Vitals, in plain English?
Core Web Vitals are Google's way of measuring what a visit to your website actually feels like. Instead of an abstract score, each metric answers a question any customer would ask. Think of a visit to a physical store:
- LCP (Largest Contentful Paint): how long it takes for the shop window to show up. It measures the time until the biggest block on the screen, usually the main image or headline, appears.
- INP (Interaction to Next Paint): how long the clerk takes to respond. It measures the delay between a tap or click and the page's reaction.
- CLS (Cumulative Layout Shift): whether the shelves stay put. It measures how much content jumps around while the page loads.
You know when you go to tap "Call now" and the button moves because a banner popped in above it? That's poor CLS. And when you tap the menu and nothing happens for a second or two? That's poor INP.
What are the official LCP, INP and CLS thresholds?
Google splits each metric into three ranges. The table below follows the Search Console Core Web Vitals report:
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | Loading speed | up to 2.5 s | up to 4 s | over 4 s |
| INP | Responsiveness | up to 200 ms | up to 500 ms | over 500 ms |
| CLS | Visual stability | up to 0.1 | up to 0.25 | over 0.25 |
Three details matter when you read these numbers:
- They apply to 75% of visits. web.dev recommends measuring the 75th percentile: if three out of four visits stay within the limit, the page passes.
- Mobile and desktop are assessed separately. Your site can be fine on desktop and poor on mobile, which is where many local customers look you up.
- The worst metric sets the result. According to Search Console, a group of pages with poor CLS is rated poor even if its INP is good.
What about FID, which shows up in older articles?
FID (First Input Delay) was the old responsiveness metric. INP became a stable Core Web Vital in 2024 and replaced FID, according to web.dev. If a report or article still talks about FID, it's out of date.
Why does a faster website sell more?
Speed isn't a technical vanity metric. Several studies have tied performance improvements to business results:
- Vodafone (Italy): in an A/B test on a sales landing page, the version with a 31% better LCP produced 8% more sales, according to the case study published on web.dev.
- Deloitte and 55 research: the Milliseconds Make Millions study, commissioned by Google, analyzed 37 European and American brand sites and more than 30 million sessions. A 0.1-second improvement in mobile site speed came with 8.4% more conversions on retail sites and 10.1% on travel sites. On lead generation sites, 21.6% more users progressed to the form page.
- Agrofy: the agricultural marketplace improved LCP by 70% and cut load abandonment by 76%, according to web.dev's roundup of case studies.
These numbers come from large companies and aren't a promise of results for every site. The logic, however, applies to any business size. Picture a dental practice running Instagram ads. Every click costs money. If the page is slow to open on a mobile connection, some of those people close the tab before they ever see the "Book now" button, and the ad budget goes with them.
Do Core Web Vitals help you rank on Google?
They help, but they aren't magic. Google states on its page experience documentation that Core Web Vitals are used by its ranking systems. On the same page, it makes clear that good scores don't guarantee your pages will rank at the top of the results.
The reason is that relevance comes first. Google says it always seeks to show the most relevant content, even when the page experience is subpar. In practice:
- a fast site with weak content still struggles to show up;
- a site with great content and slow pages loses part of the visitors it managed to attract;
- the goal is to have both, and Google highly recommends achieving good Core Web Vitals for success with Search.
How to check your Core Web Vitals, step by step
You don't need to be a developer to run a first check. It takes a few minutes:
- Open PageSpeed Insights, Google's free tool, and paste in your website address.
- Look at real-user data first. web.dev calls this field data: measurements from actual visitors, taken from the Chrome User Experience Report (CrUX). This is the data Google uses to assess the page.
- Then review the lab diagnosis. It's a simulation run on the spot by Lighthouse, useful for finding what to fix. Note that Lighthouse can't measure INP, because nobody is tapping the screen, so it uses Total Blocking Time (TBT) instead, as web.dev explains.
- Check both the mobile and desktop tabs. The results are often different.
- If you use Google Search Console, open the "Core Web Vitals" report to see which groups of pages are good, need improvement or are poor.
Seeing "no data"? That's common for small sites
Many small business websites don't get enough visits to generate field data. Search Console explains that the no-data message appears when the property is new or when the Chrome report doesn't have enough data for that device type. In that case, use the lab diagnosis as your guide and test the site on your own phone, off Wi-Fi.
What slows a website down most (and how to fix it)
High LCP: heavy images and a slow server
web.dev's guide to optimizing LCP points to the main fixes:
- Properly sized images in modern formats, such as WebP or AVIF, and compressed. That 5 MB phone photo in the homepage banner is a classic culprit.
- Don't lazy-load the main image. web.dev says you should never do this with your LCP image, because it delays its display.
- Fast hosting, with caching and a CDN (a network of servers spread around the world). According to the guide, a high server response time can make a 2.5-second LCP hard or even impossible to reach.
- Less CSS and JavaScript blocking the screen before the main content shows up.
High INP: too much code running on the phone
INP gets worse when the browser is busy running code and can't respond to a tap. Too many plugins, chat widgets, pop-ups and third-party scripts tend to weigh things down. The INP optimization guide recommends breaking up long tasks and reducing the work the browser does on each interaction. In an online store, this shows up as an "Add to cart" button that's slow to react.
High CLS: elements that push the page around
The CLS optimization guide lists common causes: images without set width and height, ads and banners that load without reserved space, and fonts that change size mid-load. The fix is to reserve space for each element before it appears. Picture a restaurant menu that jumps every time a photo finishes loading: customers give up reading.
What to ask whoever manages your website
If you don't touch the code yourself, bring this list to your developer or agency:
- "What are our LCP, INP and CLS on mobile, based on real-user data?"
- "Are our images compressed and served as WebP or AVIF?"
- "Which plugins and third-party scripts can we remove?"
- "Does our hosting use caching and a CDN?"
- "Who checks the Core Web Vitals report after each change?"
Speed is easier to build in than to fix later. That's why, in our custom website design projects, performance is part of the plan from the first draft. If you're planning a new site, you may also want to read how much a professional website costs and what goes into that price.
Conclusion
Core Web Vitals turn what your customers feel into numbers: whether your site opens fast (LCP up to 2.5 s), responds right away (INP up to 200 ms) and doesn't jump around (CLS up to 0.1). They count for Google, but they don't replace relevant content, and no score guarantees the top spot. The most concrete payoff is in sales and leads: cases like Vodafone's show that less waiting means more people reaching the buy button. Start by measuring with PageSpeed Insights, fix the worst metric on mobile first and, if you'd like help with the diagnosis, get in touch.
Frequently asked questions
What are Core Web Vitals?
They are three Google metrics that measure the real experience of people visiting a website: LCP (loading speed), INP (responsiveness to taps and clicks) and CLS (visual stability). You can see them in PageSpeed Insights and Search Console.
Do Core Web Vitals affect SEO?
Yes. Google states that Core Web Vitals are used by its ranking systems. It also says good scores don't guarantee a top ranking, because content relevance comes first.
What are good LCP, INP and CLS scores?
Google considers an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds and a CLS of up to 0.1 to be good. A page passes when at least 75% of visits fall within those limits.
What happened to FID?
FID (First Input Delay) was replaced by INP, which became a stable Core Web Vital in 2024. If a report still mentions FID, it is out of date.
Why does Search Console show "no data" for my site?
This happens when the property is new or when the Chrome User Experience Report doesn't have enough visits for that device type. It's common for small sites; in that case, use the PageSpeed Insights lab diagnosis as your reference.
Want to know if your website passes Core Web Vitals? Send us the URL on WhatsApp and we'll explain what's slowing it down.
Check my website