Core Web Vitals Explained: A Plain-English Guide for Business Owners

Core Web Vitals come up in almost every website audit, usually as a set of red, amber and green results that are hard to interpret. What they measure is simple: whether your pages load quickly, respond promptly and stay still while people use them. This guide explains the three metrics in plain English, how to check them, the fixes that usually make the biggest difference and, just as importantly, how much they really matter for rankings compared with the content on the page.

What Core Web Vitals are

Core Web Vitals are a small set of metrics Google uses to describe the experience of using a web page. They sit within what Google calls page experience, alongside things like serving the site securely over HTTPS, working well on mobile and not hiding content behind intrusive pop-ups.

The important detail is that Google's assessment is based on real visits, not a simulated test. The data comes from Chrome users who have opted in to sharing usage statistics, collected in the Chrome User Experience Report. Each metric is assessed at the 75th percentile, which means roughly three out of four visits need to meet the "good" threshold for a page to pass. Mobile and desktop are measured separately, and mobile is usually the harder of the two, because phones have less processing power and often slower connections.

The three metrics in plain English

Largest Contentful Paint (LCP): loading

LCP measures how long it takes for the largest visible element on the first screen, usually a hero image, banner or main heading, to appear. It is a reasonable proxy for the moment a visitor feels the page has loaded. Google's "good" threshold is 2.5 seconds or less.

Interaction to Next Paint (INP): responsiveness

INP measures how quickly the page responds visually when someone taps, clicks or types. It replaced First Input Delay as a Core Web Vital in 2024 and is more demanding, because it considers interactions throughout the visit and reports one of the slowest, rather than looking only at the first. A "good" INP is 200 milliseconds or less. Poor INP is what visitors experience as a sluggish page: a menu that hesitates before opening, or a form field that lags behind their typing.

Cumulative Layout Shift (CLS): visual stability

CLS measures how much content unexpectedly moves around while the page is in use. If you have ever gone to tap a button and hit an advert instead because the page jumped, you have experienced layout shift. CLS is a score rather than a time, and "good" is 0.1 or less.

How to check your own site

• PageSpeed Insights: enter a URL to see field data from real users at the top, where Google has enough of it, and a lab test underneath. The field data reflects what Google uses; the lab test is a diagnostic tool.
• Google Search Console: the Core Web Vitals report groups similar URLs and shows which groups are good, need improvement or are poor, on mobile and desktop. It is the best way to spot patterns across a whole site.
• Chrome DevTools: the Performance panel shows live LCP, INP and CLS readings as you use a page, which helps a developer track down a specific problem.

Two points cause a lot of confusion. First, the performance score out of 100 in a lab test is not a Core Web Vitals assessment and is not what Google uses for ranking. It is useful for spotting problems, but chasing a perfect score is rarely a good use of budget. Second, smaller sites often do not have enough traffic for Google to report field data. In that case, use lab results as a guide and work through the fixes below.

Practical fixes that usually make the biggest difference

Core Web Vitals problems on small business websites tend to come from a familiar set of causes, which is good news, because the fixes are well understood.

Improving LCP

• Compress and correctly size the main hero image, and serve it in a modern format such as WebP or AVIF.
• Do not lazy-load the main image at the top of the page. Lazy loading is for images further down; applied to the hero, it delays the very thing LCP measures.
• Tell the browser the hero image is important, for example with a preload hint or the fetchpriority attribute, which a developer can add quickly.
• Improve server response time with decent hosting, page caching and, where it suits your audience, a content delivery network.
• Reduce render-blocking CSS and JavaScript so the browser can draw the page sooner.
• Reconsider large image sliders or background videos at the top of the page. They are often the slowest element and seldom the most persuasive.

Improving INP

• Audit third-party scripts. Chat widgets, social feeds, duplicate analytics tags and marketing pixels all compete for the browser's attention, so remove anything nobody uses.
• On WordPress and similar platforms, remove unused plugins and be wary of page builders that load large amounts of script on every page.
• Ask your developer to break up long JavaScript tasks and defer non-essential scripts until after the page is usable.
• Keep pages lean. Very large pages with thousands of elements take longer to update after every interaction.

Improving CLS

• Set width and height, or an aspect ratio, on images, videos and embeds so the browser reserves space for them.
• Reserve space for cookie banners, adverts, booking widgets and other elements that load late, or display them as overlays rather than pushing content down.
• Load web fonts carefully so text does not visibly jump when the custom font arrives.
• Avoid inserting banners or notices above content that is already on screen.

How much do Core Web Vitals matter for rankings?

This is where a balanced view helps. Core Web Vitals are used by Google's ranking systems, but Google has been consistent that relevance and the overall helpfulness of content come first. A page that answers a search well will usually outrank a faster page that does not, and passing every metric will not lift thin or off-topic content.

In practice, page experience tends to matter most when several pages are similarly relevant, which is common in competitive local and commercial searches. There, it can be one of the factors that separates otherwise comparable results. It is best thought of as a supporting factor, not a shortcut.

The stronger argument for fixing performance is commercial rather than algorithmic. Slow, jumpy, unresponsive pages frustrate people, particularly on mobile, and frustrated visitors leave before they call or book. That makes speed and stability as much a conversion rate optimisation concern as an SEO one.

Where to start: a sensible priority order

1. Check the Core Web Vitals report in Search Console to see whether you have a problem at all, and on which types of page.
2. Prioritise templates rather than individual pages. Fixing the service page layout or product template improves every page built on it.
3. Start with the pages that earn enquiries and sales: your homepage, key service pages and contact or booking pages.
4. Tackle quick wins first: hero images, unused plugins and unnecessary third-party scripts.
5. Re-test, then allow time for the field data to catch up. Because it reflects a rolling window of real visits, improvements take several weeks to show in reports.

If your site is built on an older theme or platform that resists every improvement, it may be more economical to rebuild key templates than to keep patching. A performance-focused website design can build good Core Web Vitals in from the start rather than retrofitting them later.

The bottom line

Core Web Vitals are worth understanding and worth fixing, but they are one part of a healthy website rather than the whole story. Make sure your pages are relevant and genuinely useful first, then remove the technical friction that stops visitors using them comfortably. If you would like an expert view of where your site stands, our technical SEO service covers performance alongside crawling, indexing and site structure, and an SEO audit will show which issues are worth fixing first.