Core Web Vitals Explained: INP, LCP and CLS for Business Owners

Two fixes move Core Web Vitals on most business websites: make the biggest thing at the top of the page load fast, and stop JavaScript from blocking the browser when somebody taps. Everything else is detail. Before you spend a penny, look at your field data rather than a lab score, because the lab score is a simulation and the field data is what Google and your customers actually experienced.

The three metrics in plain language

• LCP, Largest Contentful Paint. How long until the biggest piece of content in the first screenful has rendered. Usually your hero image, a banner, or the headline block. It is the closest thing to “did the page appear?”
• INP, Interaction to Next Paint. How quickly the page visibly responds when a visitor taps, clicks or presses a key, measured across the whole visit rather than the first interaction. web.dev describes it as the successor to First Input Delay, which only measured the delay on the first input.
• CLS, Cumulative Layout Shift. How much the layout jumps around while loading. The ad that pushes the paragraph down as you start reading, the web font that reflows a heading, the button that moves just as your thumb arrives.

Three different complaints, in other words: it was slow to appear, it felt sticky when I used it, and it moved under my finger. Each has its own fix list, and conflating them is why so many performance projects spend money in the wrong place.

The thresholds, and the 75th percentile

Google publishes a three-band scale for each metric. The number that counts is the 75th percentile of page visits, split between mobile and desktop, which means roughly three quarters of your visitors need the good experience before the page is classified as good. That is deliberately demanding: your fast visits on a fast laptop do not cancel out the slow ones on a mid-range phone.

How the rest of the web is doing

The HTTP Archive’s Web Almanac 2025 measured the whole crawlable web against these thresholds. 48% of mobile websites and 56% of desktop websites achieved good scores on all three metrics, up from 32% and 41% respectively in 2021. Steady progress, and it means failing all three is no longer normal: if your site does not pass, it is now behind the median.

Split by metric, the picture is more useful. Layout stability is largely solved on mobile and responsiveness is close to solved on desktop. The two real problems are mobile responsiveness, where slower processors turn JavaScript into visible lag, and loading speed on phones.

One more figure worth holding on to: the Almanac found that an image is the largest element on 85.3% of desktop pages and 76% of mobile pages. If you only have budget for one piece of performance work, it is almost certainly the hero image.

Field data beats lab scores

There are two kinds of measurement and people constantly argue using the wrong one. Lab tools, such as Lighthouse in your browser, simulate a visit on a throttled connection. They are excellent for diagnosis and useless as a verdict. Field data, collected from real Chrome users and published in the Chrome User Experience Report, is what Google uses to inform its page experience ranking factor, and it is the number your Search Console report shows.

• Start in Search Console, in the Core Web Vitals report. It groups your URLs and tells you which metric is failing on which template.
• Then use PageSpeed Insights for a single URL: it shows the field data at the top and the lab diagnosis underneath.
• Expect gaps. Chrome’s dataset only includes origins and pages with enough visitors to be statistically meaningful, so a small or new site may have no field data at all. In that case use lab tools plus your own real-user monitoring.
• Fix by template, not by page. One product template fixed is a thousand URLs fixed.

This is also where expectations need managing. Field data aggregates recent visits, so a fix deployed today does not show up in the report tomorrow. Give it a few weeks before concluding that the work did not help.

What actually moves each metric

web.dev maintains a short list of the changes that move each metric most, and it has stayed remarkably stable. Translated for a business site running a mainstream CMS:

Notice how many INP problems are commercial decisions rather than engineering ones. A chat widget, two analytics tools, a heatmap recorder and a consent banner can easily add hundreds of milliseconds of main-thread work on a mid-range Android phone. Somebody has to be allowed to say no to the fourth tag.

While you are in there, treat performance and accessibility as the same project. Reserved space for images helps screen-reader and keyboard users as much as it helps CLS, and a page that responds within 200 milliseconds is kinder to everyone. Do be careful about claiming compliance, though: meeting WCAG 2.2 cannot be verified by an automated score. Full validation needs manual testing with assistive technology and review by someone with accessibility expertise.

Rankings, revenue and what the case studies show

Google is clear that page experience signals, which Core Web Vitals feed, are one input among many and will not rescue content nobody wants. The commercial argument is stronger than the ranking one. Google’s own collection of case studies includes these documented results:

Our honest position: for a small business site with modest traffic, the revenue case is usually about conversion on mobile rather than search position. A checkout that stops jumping around and a product page that paints in two seconds will do more for your numbers than any ranking shuffle. Our older note on why website speed matters covers that argument in more detail.

Your platform changes the odds

Platform choice shifts your starting odds, because defaults, themes and plugin ecosystems differ. The Web Almanac’s 2025 CMS chapter measured mobile Core Web Vitals pass rates by platform: Duda at 85%, TYPO3 at 79% and Wix at 74% lead, while WordPress sits among the lowest at 45%, with Weebly at 47%. On loading specifically, 94% of Duda sites and 89% of TYPO3 sites achieved good LCP against 53% of WordPress sites.

Do not read that as “leave WordPress”. The Almanac’s own reading is that the gap reflects how much the platform lets you change: tightly managed builders can roll an improvement out to every customer at once, whereas an open ecosystem of themes, plugins and page builders produces enormous variance. A carefully built WordPress site on decent hosting passes comfortably. A WordPress site with a page builder, 38 plugins and shared hosting does not, and the platform is only part of the reason. Hosting matters too, which is the subject of our guide to web hosting types.

A realistic plan for a small site

1. Week 1: measure. Open the Core Web Vitals report in Search Console and note which templates fail which metric. Record today’s numbers so you can prove the change later.
2. Week 1: audit what loads. List every third-party script and ask who needs it. Delete the ones nobody can justify.
3. Week 2: fix the hero. Correct image dimensions and format, preload the LCP image, remove render-blocking CSS and fonts above the fold.
4. Week 2: reserve space. Width and height on every image, iframe and embed. Move banners below the first screenful.
5. Week 3: cut the main thread. Defer non-essential JavaScript, load chat and heatmaps on interaction, break up anything long enough to block a tap.
6. Week 4 onwards: wait and re-measure. Field data lags, so compare in four to six weeks and keep the before-and-after in writing.

That sequence fits a month of part-time attention and covers the majority of what a small business site needs. Mobile-first layout decisions make the whole exercise easier, which is where mobile-first web design comes in. Performance work sits inside our web development and hosting service, delivered remotely for clients worldwide: we measure, fix and hand back a before-and-after you can show your board, and we will tell you when the honest answer is that your site is already fast enough.

Want your Core Web Vitals measured, fixed and documented without a full redesign? Get in touch with Eudora Technology to talk about your project.