If a report or your developer has told you to “pass Core Web Vitals” and you have no idea what that means, this guide is written for you. Core Web Vitals are three measurements Google uses to judge how a real person experiences your page: how fast the main content loads, how quickly the page reacts when someone taps or clicks, and how much the layout jumps around while it loads. You do not need to be technical to understand them. But knowing what they are helps you ask the right questions and spot when your site is costing you visitors.
What Core Web Vitals are and why Google cares
Core Web Vitals are Google’s attempt to put a number on page experience. Rather than guessing whether a site “feels” good, Google measures three specific things from real Chrome users and uses them as a ranking signal. The logic is simple: slow, janky pages frustrate people, frustrated people leave, and Google would rather send searchers to pages that work well. For a small business, that means Core Web Vitals sit at the intersection of SEO and conversions. A page that loads fast and responds instantly ranks better and turns more visitors into calls and bookings.
Importantly, these scores come from real visitors over a rolling 28-day window, measured at the 75th percentile. In plain terms, roughly three out of four visits need to hit the good mark for the page to pass. A lab test on your fast laptop can look great while real users on phones struggle, so field data is what counts.
LCP: how fast your main content loads
Largest Contentful Paint, or LCP, measures how long it takes for the biggest visible element on the page, usually a hero image, headline, or banner, to finish loading. It answers the visitor’s silent question: “Is this page actually showing up?” As of October 2026, a good LCP is 2.5 seconds or faster. Between 2.5 and 4 seconds needs improvement, and anything slower than 4 seconds is considered poor. The usual culprits behind a slow LCP are oversized images, slow hosting, and heavy code that blocks the page from rendering.
INP: how quickly your page responds
Interaction to Next Paint, or INP, measures responsiveness: when someone taps a button, opens a menu, or fills a form field, how long before the page visibly reacts? INP replaced an older metric called First Input Paint in March 2024, and it looks at the full lifecycle of interactions across the whole visit, not just the first click. A good INP is 200 milliseconds or faster. Between 200 and 500 milliseconds needs improvement, and over 500 milliseconds is poor. Sluggish responsiveness usually comes from too much JavaScript, often from piled-up plugins and third-party scripts fighting for the browser’s attention.
CLS: how stable your layout stays
Cumulative Layout Shift, or CLS, measures visual stability. You have felt bad CLS yourself: you go to tap a link, an ad or image loads late, the page jumps, and you tap the wrong thing. CLS scores how much the layout moves unexpectedly while the page loads. A good CLS is 0.1 or lower. Between 0.1 and 0.25 needs improvement, and above 0.25 is poor. The common causes are images and ads without reserved space and fonts that load late and reflow the text.
The three metrics side by side
| Metric | What it measures | Good | Needs work | Poor |
|---|---|---|---|---|
| LCP | Main content load speed | 2.5s or faster | 2.5s to 4s | Over 4s |
| INP | Responsiveness to taps and clicks | 200ms or faster | 200ms to 500ms | Over 500ms |
| CLS | Visual stability, layout shift | 0.1 or lower | 0.1 to 0.25 | Over 0.25 |
Passing Core Web Vitals is not rare but it is not automatic either. According to the 2025 Web Almanac from HTTP Archive, only about 48 percent of mobile sites and 56 percent of desktop sites hit “good” across all three metrics, which means many small business sites are leaving ranking and conversion on the table.
How to check and improve your scores
You can see your own numbers in minutes. Here is a simple, non-technical path:
- Run your home page through Google’s free PageSpeed Insights tool and read the field data at the top.
- Check the same scores in Google Search Console under the Core Web Vitals report, which groups your pages by status.
- Note which of the three metrics is failing, since the fix differs for each.
- For LCP, compress large images and move to faster hosting.
- For INP, remove unused plugins and heavy scripts that slow interaction.
- For CLS, set width and height on images and reserve space for ads and embeds.
- Re-test after each change, remembering field data updates over a 28-day window.
Many fixes, especially image compression, caching, and quality hosting, are things a good build and host handle for you from the start, which is why some sites pass without their owners ever touching the code.
What small business owners should actually do
You do not need to memorize milliseconds. The practical move is to run the test above once, see whether your pages pass, and treat a failing score as a sign your site needs attention. Core Web Vitals reward the same things customers reward: fast loading, instant response, and a page that stays put. Get those right and you improve rankings and conversions at once. If the numbers look bad and the fixes feel over your head, that is a reasonable point to bring in help.
What is a good Core Web Vitals score?
As of October 2026, good scores are an LCP of 2.5 seconds or faster, an INP of 200 milliseconds or faster, and a CLS of 0.1 or lower. To pass, your site needs to meet all three thresholds for about 75 percent of real visits measured over a rolling 28-day window.
Do Core Web Vitals really affect my Google ranking?
Yes, they are part of Google’s page experience signals, though they are one factor among many. Relevant content still matters most. Where Core Web Vitals often tip the balance is between similar pages, and strong scores also lift conversions because fast, stable pages keep visitors from leaving.
What happened to FID, the old Core Web Vital?
First Input Delay was replaced by Interaction to Next Paint in March 2024. INP is a better measure because it looks at the responsiveness of interactions across the whole visit, not just the delay on the first one, giving a fuller picture of how the page feels to use.
How do I check my Core Web Vitals for free?
Use Google’s PageSpeed Insights for a single page and the Core Web Vitals report in Google Search Console for a site-wide view. Both are free. Focus on the field data, which reflects real visitors, rather than only the lab score from a single test run.
Can I fix Core Web Vitals myself?
Some fixes are approachable, such as compressing images and removing unused plugins. Others, like reducing JavaScript or tuning server response time, are more technical. Fast hosting and a well-built site prevent many issues from the start, so for many owners the simplest path is to build and host on a stack that passes by default.
Not sure if your site passes? We build fast, stable local business sites and host them on infrastructure tuned for Core Web Vitals. Explore our website design services, see our website hosting plans, or get started with a site built to pass from day one.