What is a good Core Web Vitals score?

There is no single score. Each metric is rated separately: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less are good. A page passes when at least 75% of real visits meet all three. The 0 to 100 Lighthouse performance score is a separate lab measure and is not the same thing.

Is INP the same as FID?

No. FID measured only the delay before the browser began handling the first interaction. INP looks at how quickly the page visibly responds to interactions throughout a visit and reports one of the slowest. INP replaced FID as a Core Web Vital in March 2024 and is harder to pass on script-heavy sites.

Why does my PageSpeed Insights score change every time?

The lab score depends on network conditions, server load and the test machine, so it varies between runs. Run it a few times and look at the trend. The field data at the top of the report is more stable because it is based on real visits over 28 days, but it can be missing for low-traffic sites.

Why does Search Console say no data for Core Web Vitals?

The Search Console report relies on real Chrome user data, and Google only shows it when a site or group of pages has enough visits. Many small local websites do not reach that level. In that case use PageSpeed Insights lab results and test on real phones, focusing on your most visited pages.

Will fixing Core Web Vitals get me to the top of Google?

Unlikely on its own. Google says Core Web Vitals are used in ranking, but relevance and helpful content carry far more weight. For local businesses, your Google Business Profile, reviews and service pages usually matter more. Better vitals mainly help visitors stay and contact you, which is the result you want anyway.

How long does it take to see improvements?

Lab tests in Lighthouse change immediately after a fix. Field data in PageSpeed Insights and Search Console uses a rolling 28-day window, so expect about four weeks before the full effect shows. Search Console also has a validation feature you can start after fixing an issue to track progress.

Do I need a developer to fix Core Web Vitals?

Simple fixes such as compressing images, removing unused plugins and turning on caching can often be done by an owner with some care. Problems like heavy themes, render-blocking scripts or layout shifts in the template usually need a developer. Get a fixed quote and ask what will be measured before and after.

Speed & Security

Core Web Vitals for Small Business: What LCP, INP and CLS Mean and How to Improve Them

By ITCM Team · Updated November 2026

Core Web Vitals are three Google measurements of how a page feels to real visitors: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A good score means LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less, measured for most of your real visitors. Google uses them in its ranking systems, but they are not a shortcut to page one. For a small business they matter most because slow, jumpy pages lose calls and bookings.

Key takeaways

The three Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability).
INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.
Google says Core Web Vitals are used by its ranking systems, but relevant, helpful content still matters far more.
Field data from real Chrome users is what Google uses; lab scores in Lighthouse are for diagnosing problems.
On small-business sites the usual culprits are huge images, too many plugins and scripts, and slow hosting.
Fix the biggest problem on your most important pages first instead of chasing a perfect 100.

What are Core Web Vitals in plain English?

Think of a customer opening your homepage on their phone. Core Web Vitals ask three questions: how quickly does the main content appear, how quickly does the page react when they tap something, and does the layout stay still while it loads?

Google measures these using data from real Chrome users who visit your site, then looks at the 75th percentile. That means at least three out of four visits need a good experience for a page to pass. A fast laptop on office Wi-Fi does not tell you how your customers on mobile data experience the site.

LCP (Largest Contentful Paint): how long until the biggest visible element, often a hero photo or headline, has loaded.
INP (Interaction to Next Paint): how long the page takes to respond visually after a tap, click or key press, across the whole visit.
CLS (Cumulative Layout Shift): how much the content jumps around unexpectedly, such as a button moving just as you tap it.

What are the good and poor Core Web Vitals thresholds?

Google groups each metric into good, needs improvement and poor. These thresholds are published on web.dev and used in PageSpeed Insights and Search Console.

Metric	Measures	Good	Needs improvement	Poor
LCP	Loading of main content	2.5 seconds or less	2.5 to 4 seconds	Over 4 seconds
INP	Responsiveness to taps and clicks	200 ms or less	200 to 500 ms	Over 500 ms
CLS	Visual stability	0.1 or less	0.1 to 0.25	Over 0.25

What happened to FID?

First Input Delay (FID) only measured the delay before the browser started handling the first interaction on a page. It missed slow responses later in the visit, and most sites passed it easily. On 12 March 2024, Interaction to Next Paint (INP) officially replaced FID as a Core Web Vital.

INP is stricter because it looks at interactions throughout the visit, such as opening a menu, choosing a date in a booking calendar or submitting a form. Sites heavy with JavaScript, chat widgets and tracking scripts often found their scores dropped when INP arrived, even though nothing on the site had changed.

Do Core Web Vitals affect Google rankings?

Yes, but less than many tools and agencies suggest. Google's page experience documentation says Core Web Vitals are used by its ranking systems, and also warns that chasing a perfect score just for SEO may not be the best use of your time. It adds that other page experience aspects do not directly help a site rank higher.

In practice, a plumber with useful service pages, good reviews and a strong Google Business Profile will usually outrank a faster competitor with thin content. Where two pages are similarly relevant, a better experience can help. The bigger effect is on people: a page that loads slowly or jumps around loses visitors before they call.

You are also not alone if you fail. The HTTP Archive Web Almanac 2025 found that only 48% of websites passed all three Core Web Vitals on mobile, and 56% on desktop. On mobile, LCP was the hardest metric, with 62% of sites rated good.

How do I check my Core Web Vitals?

Start with free tools from Google, then use our website health check for a quick overall scan.

PageSpeed Insights: enter a page address. The top section shows field data from real users over the last 28 days, if your site has enough traffic. The lower section is a Lighthouse lab test with suggestions.
Search Console Core Web Vitals report: shows groups of URLs as good, needs improvement or poor for mobile and desktop, based on real-user data. Low-traffic sites may see no data.
Lighthouse in Chrome DevTools: runs a lab test on your own computer, useful for testing fixes before and after.
Real phones: load your key pages on mobile data and notice what feels slow or jumpy.

What is the difference between field data and lab data?

Field data comes from real Chrome users visiting your site on their own devices and connections. It is what Google uses for Core Web Vitals, but it updates slowly because it covers a rolling 28-day window, so fixes take weeks to show.

Lab data comes from a simulated test, such as Lighthouse, on a fixed device and network. It is instant and repeatable, which makes it ideal for finding causes, but it can disagree with field data. A Lighthouse performance score of 70 does not mean you fail Core Web Vitals, and a score of 95 does not guarantee you pass. Small local sites often have no field data at all, in which case lab tests and real-phone checks are your best guide.

What causes poor Core Web Vitals on small-business sites?

The same handful of problems appear again and again on sites for salons, clinics and trades. Most can be fixed without a redesign.

Huge hero images or sliders uploaded straight from a camera, which hurt LCP. Resize, compress and use WebP or AVIF, and do not lazy-load the main image.
Slow server response from cheap or overloaded hosting, which delays everything. Add page caching and consider better hosting.
Too many plugins, page-builder scripts, chat widgets and tracking tags, which hurt INP. Remove what you do not use and delay non-essential scripts.
Images, embeds and ads without set dimensions, which cause CLS. Give every image a width and height or reserved space.
Cookie banners, promo bars and web fonts that push content down after loading, which also cause CLS. Reserve space or overlay them instead.
Booking or map embeds loaded on every page, even where nobody needs them. Load them only where they are used.

WordPress and builders vs custom sites: which is better for Core Web Vitals?

Any platform can pass. Hosted builders handle hosting and caching for you, but you have limited control over the scripts they load. WordPress gives full control, yet many sites accumulate a theme, a page builder and dozens of plugins, each adding code; tidying that up is often the biggest win. Our guide on how to speed up your website lists the fixes in order of impact.

Custom-coded sites can be very lean because they only load what each page needs, but only if they are built with care. If you would rather hand the work over, our website speed optimization service covers diagnosis and fixes. For the wider technical picture, see the technical SEO checklist and our guide to a mobile-friendly website.

How does ITCM approach Core Web Vitals?

We build custom-coded sites without plugin sprawl, size images for phones, reserve space for every image and embed, and keep third-party scripts to what the business actually needs. When we take over troubled sites, such as in our WordPress recovery case study, speed and security hardening are part of the cleanup.

We also work demo-first: through our website and app offer we build your site and installable app, you test it on your own phone, and you pay the $150 one-time fee only if you are happy. Work outside the offer gets a fixed quote before anything starts.

Core Web Vitals checklist for small business

Check your homepage and top service pages in PageSpeed Insights on mobile.
Open the Core Web Vitals report in Search Console if you have data.
Compress and resize the main image on each key page; do not lazy-load it.
Give images and embeds fixed dimensions to stop layout shifts.
Remove unused plugins, widgets and tracking tags.
Turn on caching and check how quickly your server responds.
Re-test with Lighthouse after each change, then wait about four weeks for field data to update.

Frequently asked questions

What is a good Core Web Vitals score?: There is no single score. Each metric is rated separately: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less are good. A page passes when at least 75% of real visits meet all three. The 0 to 100 Lighthouse performance score is a separate lab measure and is not the same thing.
Is INP the same as FID?: No. FID measured only the delay before the browser began handling the first interaction. INP looks at how quickly the page visibly responds to interactions throughout a visit and reports one of the slowest. INP replaced FID as a Core Web Vital in March 2024 and is harder to pass on script-heavy sites.
Why does my PageSpeed Insights score change every time?: The lab score depends on network conditions, server load and the test machine, so it varies between runs. Run it a few times and look at the trend. The field data at the top of the report is more stable because it is based on real visits over 28 days, but it can be missing for low-traffic sites.
Why does Search Console say no data for Core Web Vitals?: The Search Console report relies on real Chrome user data, and Google only shows it when a site or group of pages has enough visits. Many small local websites do not reach that level. In that case use PageSpeed Insights lab results and test on real phones, focusing on your most visited pages.
Will fixing Core Web Vitals get me to the top of Google?: Unlikely on its own. Google says Core Web Vitals are used in ranking, but relevance and helpful content carry far more weight. For local businesses, your Google Business Profile, reviews and service pages usually matter more. Better vitals mainly help visitors stay and contact you, which is the result you want anyway.
How long does it take to see improvements?: Lab tests in Lighthouse change immediately after a fix. Field data in PageSpeed Insights and Search Console uses a rolling 28-day window, so expect about four weeks before the full effect shows. Search Console also has a validation feature you can start after fixing an issue to track progress.
Do I need a developer to fix Core Web Vitals?: Simple fixes such as compressing images, removing unused plugins and turning on caching can often be done by an owner with some care. Problems like heavy themes, render-blocking scripts or layout shifts in the template usually need a developer. Get a fixed quote and ask what will be measured before and after.

Get a website + app built for free

We build your website and mobile app first, and you see it finished. If you’re happy, you pay $150 one-time. If you’re not, you pay nothing.

See the $150 offer Free website audit

← All articles