Core Web Vitals Explained: What LCP, INP and CLS Mean for Your Business
Core Web Vitals are three Google measures of how a page feels to real visitors: how fast the main content shows (LCP), how fast the page reacts to taps (INP), and whether things jump around (CLS). They do count in Google rankings, but relevance counts more. Fix them because slow, jumpy pages lose leads.
Key takeaways
- The targets are simple: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, measured on real visitors.
- Google says Core Web Vitals are used by its ranking systems, but it will still rank the most relevant page even if its experience is weak.
- Only 48% of mobile websites pass all three, so a fast site can still stand out against local and national competitors.
What are Core Web Vitals, in plain English?
Core Web Vitals are three scores Google uses to judge whether a web page feels fast, responsive and stable to the people actually using it. Google collects them from real Chrome users, not from a lab. A page passes only when all three scores are good for at least 75% of visits, on mobile and desktop separately.
Think of it like a restaurant inspection that only looks at three things. Did the food show up quickly? Did the staff respond when you waved? Did anyone knock your plate off the table? A website can have nice photos and strong copy and still fail on all three.
The 75% rule matters. Google's guidance on web.dev says to measure the 75th percentile of page loads. In plain terms, your site needs to be good for three out of four visits. A fast experience on your office Wi-Fi does not count for much if a customer on a weak phone signal waits eight seconds.
What do LCP, INP and CLS actually measure?
LCP measures loading: how long until the biggest image or text block appears. INP measures responsiveness: how long the page takes to react after a tap, click or key press. CLS measures stability: how much the layout shifts while loading. Each has a good, a needs improvement and a poor range set by Google.
| Metric | What it means for a visitor | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | "Is the main thing on the page showing yet?" | 2.5 seconds or less | 2.5 to 4.0 seconds | Over 4.0 seconds |
| INP (Interaction to Next Paint) | "Did my tap on the button do anything?" | 200 ms or less | 200 to 500 ms | Over 500 ms |
| CLS (Cumulative Layout Shift) | "Why did the page jump right when I tried to tap?" | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
A few notes help make sense of the table:
- LCP usually tracks your hero photo or main headline. Google counts images, video poster images, background images and large text blocks.
- INP looks at nearly all the taps and clicks during a visit, not just the first one. Menus, quote forms and click-to-call buttons all count.
- CLS is a unitless score, not seconds. It goes up when images load without set sizes, when fonts swap, or when banners and widgets push content down.
Search Console labels a group of pages by its worst metric. If your LCP and INP are good but CLS is poor, the whole group shows as poor.
Why did INP replace FID in 2024?
INP replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. FID only measured the delay before the first interaction started. INP measures how long it takes the page to visibly respond, across the whole visit. It is a stricter and more honest test of whether a page feels sluggish.
FID was easy to pass. A page could respond quickly to the first tap and then freeze when someone opened a menu or filled in a form. INP catches that. Google promoted INP to pending status in 2023 to give site owners time to prepare, then made the switch official in March 2024.
If an old audit, plugin or agency report still talks about FID, it is out of date. Ask for INP numbers instead. Sites with heavy scripts, chat widgets, tracking tags and pop-ups are the ones most likely to have slipped when the rules changed.
Do Core Web Vitals affect your Google rankings?
Yes, but less than most people think. Google's documentation states that Core Web Vitals are used by its ranking systems. The same page says Google always tries to show the most relevant content, even if the page experience is sub-par. Speed can help you win a close race. It will not rescue a weak page.
Google's own words are careful. Its Search Central documentation says there is no single page experience signal. It also says good Core Web Vitals scores do not guarantee top rankings, and that chasing a perfect score just for SEO reasons may not be the best use of your time.
Here is how to read that as a business owner:
- If your page is the best answer to a search, a slow load will not erase that.
- If you and a competitor are both strong answers, a better experience can help you edge ahead.
- Moving from poor to good is worth real effort. Moving from good to perfect usually is not, at least for rankings.
The bigger reason to care is what happens after the click, which is where the money is.
How much does speed really matter for leads and sales?
It matters more for conversions than for rankings. In a Google-commissioned study by 55 and Deloitte, a 0.1-second faster mobile site was linked to 8.4% more retail conversions and a 21.6% rise in lead-generation visitors moving from the first form step to submission. Small delays add up.
That study, called Milliseconds Make Millions, tracked 37 brand sites and over 30 million user sessions in late 2019. Two points keep it honest. First, Google paid for it, and Google wants a faster web. Second, it found a link, not proof that speed alone caused the gains. Even so, the pattern held across retail, travel, luxury and lead generation.
A cleaner test comes from Vodafone, which ran an A/B test on a landing page. The two versions looked and worked the same. The only change was performance work on one version, which made its LCP about 31% better. That version produced 8% more sales and a 15% higher lead-to-visit rate.
For a service business, the lesson is direct. Your money pages are the ones with quote forms, booking calendars and phone numbers. If those pages load slowly or jump when someone tries to tap "Call now," you are paying for traffic that never turns into a job.
How do most websites score right now?
Most sites still fall short on mobile. HTTP Archive's 2025 Web Almanac, based on July 2025 data, found that 48% of mobile websites and 56% of desktop websites pass all three Core Web Vitals. LCP is the weakest metric on mobile, where only 62% of sites score good.
| Metric (2025 Web Almanac) | Mobile sites rated good | Desktop sites rated good |
|---|---|---|
| All three Core Web Vitals | 48% | 56% |
| LCP | 62% | 74% |
| INP | 77% | 97% |
| CLS | 81% | 72% |
The platform you build on affects your odds. The Web Almanac's 2025 CMS chapter reported mobile pass rates of 85% for Duda and 74% for Wix, up from 55% for Wix in 2024. WordPress sat at 45%, which the report called among the lowest-ranked. Weebly came in at 47%.
Read these numbers with care. A platform's average mixes millions of sites, from tidy brochure pages to bloated ones stuffed with plugins. A well-built WordPress site can pass easily. A neglected site on a fast platform can fail. The platform sets the starting line. How the site is built and maintained decides the finish.
How do you check your own Core Web Vitals?
Use two free Google tools. PageSpeed Insights shows real-visitor data for a single page plus a lab test with fix suggestions. The Core Web Vitals report in Google Search Console groups similar pages across your site and labels them good, needs improvement or poor based on the last 28 days.
A simple routine works for most owners:
- Open Search Console and go to the Core Web Vitals report. Start with the mobile tab.
- Note which groups of pages are poor or need improvement, and which metric is the problem.
- Run your homepage and your top service page through PageSpeed Insights. Look at the field data section first, labeled as what real users are experiencing.
- Use the lab diagnostics lower on the page to find causes, such as an oversized hero image or a slow script.
- After fixes go live, give the field data about four weeks to catch up.
Two cautions. The 0 to 100 performance score is a lab number, not the pass or fail Google uses. And low-traffic sites may not have enough real visitor data to show page-level results, so Search Console may group the whole domain together or show nothing.
Which fixes help each metric the most?
Most failing pages share the same few causes: a heavy hero image, too much JavaScript, and content that loads without reserved space. Google's web.dev team lists the highest-impact fixes for each metric. Many are small changes a competent web developer can make in days, not months.
| Problem | Common cause | Fix to ask for |
|---|---|---|
| Slow LCP | Large hero photo, lazy-loaded main image, slow server | Compress and resize the hero image, load it with high priority and no lazy-loading, serve the site through a CDN |
| Slow LCP | Main image hidden behind scripts or a slider | Put the main image directly in the page HTML so the browser finds it right away |
| Poor INP | Too many scripts: chat widgets, tracking tags, pop-ups | Remove unused code and old tags, split long scripts so the page can respond between tasks |
| Poor INP | Very large, complex pages | Keep the page structure lean and avoid layout work that blocks the browser |
| Poor CLS | Images and videos with no set size | Set width and height or an aspect ratio on every image and embed |
| Poor CLS | Banners, ads or widgets that push content down | Reserve space for them with a minimum height, or place them below the fold |
| Poor CLS | Animations that move page elements | Animate with transforms instead of changing position or margins |
The biggest wins for small business sites are often about removing things, not adding them. Every third-party widget, tracking tag and pop-up adds weight. Before buying a speed plugin, list every script on your site and ask whether each one still earns its place.
When should you stop chasing a perfect score?
Stop once all three metrics are in the good range for your key pages on mobile. Past that point, extra speed work rarely moves rankings, and Google itself warns against chasing perfect scores for SEO alone. Spend the next hour on content, reviews and follow-up instead.
A practical order of work looks like this:
- First: fix any page group marked poor, starting with pages that bring in leads.
- Second: move needs improvement groups into good.
- Third: protect your gains. New plugins, chat tools and tracking tags are the usual reasons a passing site slips back.
Speed is one part of a site that wins work. A fast page with a vague offer, no reviews and a buried phone number will still underperform. Treat Core Web Vitals as the floor, not the goal.
Frequently asked questions
Is a 100 score in PageSpeed Insights the same as passing Core Web Vitals?
No. The 0 to 100 score comes from a lab test run on one simulated device. Passing Core Web Vitals is judged on field data from real Chrome users over the last 28 days. A page can score 70 in the lab and still pass in the field, or the other way around. Google ranks on the field data.
My site is too small to have Core Web Vitals data. What now?
Google's Search Console report needs a minimum amount of real visitor data before it shows a page. Low-traffic sites may see grouped results for the whole domain or nothing at all. In that case, use the lab test in PageSpeed Insights as a guide, fix the obvious problems, and check again as traffic grows.
Should I check mobile or desktop first?
Start with mobile. Google measures mobile and desktop separately, and mobile is where most sites struggle. HTTP Archive's 2025 data shows 48% of mobile sites pass all three metrics, against 56% on desktop. Most visitors to a service business also find you on a phone, so mobile problems cost more.
Will switching website platforms fix my Core Web Vitals?
Sometimes, but not on its own. Platform pass rates vary a lot in HTTP Archive data, which shows the platform sets a starting point. Still, heavy images, extra scripts and pop-ups can sink a page on any platform. A rebuild helps most when it also removes the clutter that caused the slow scores.
How long does it take for fixes to show up in Search Console?
Search Console uses the last 28 days of real visitor data. After you fix a problem, the old slow visits slowly roll out of that window. Expect to wait about four weeks before the report fully reflects the change. Check the report again after that window, and keep notes on what changed and when.
The bottom line
Core Web Vitals give you three plain targets: show the main content within 2.5 seconds, react to taps within 200 milliseconds, and keep the layout steady. Hit those on mobile for your lead pages, then move on to the work that wins customers. If you want a second set of eyes, Book a free call with Mike or run the free 60-second check to see where your site stands.
Sources
- web.dev: Web Vitals
- web.dev: Largest Contentful Paint (LCP)
- web.dev: Interaction to Next Paint (INP)
- web.dev: Cumulative Layout Shift (CLS)
- web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
- Google Search Central: Understanding Core Web Vitals and Google search results
- Google Search Central: Understanding page experience in Google Search results
- Google Search Console Help: Core Web Vitals report
- HTTP Archive Web Almanac 2025: Performance
- HTTP Archive Web Almanac 2025: CMS
- web.dev: Milliseconds make millions (Google, 55 and Deloitte)
- web.dev: Vodafone case study
- web.dev: The most effective ways to improve Core Web Vitals
Keep reading
