Core Web Vitals explained for business owners

If you have looked at a speed report for your website, you have probably seen three short codes: LCP, INP and CLS. Your developer may have said they matter for Google. This guide explains what they measure in plain language, what good scores look like, and what usually causes poor ones.

What Core Web Vitals are

Core Web Vitals are three measurements Google uses to describe the experience of loading and using a web page. Each one covers a different part of that experience:

• Loading: how quickly the main content appears
• Responsiveness: how quickly the page reacts when someone taps or clicks
• Visual stability: whether things jump around while the page loads

Google measures these on real visits from Chrome users, collected in the Chrome User Experience Report. That makes them different from a single lab test on your developer's fast laptop. They reflect what your actual visitors experience on their own phones and networks.

The three metrics

LCP: Largest Contentful Paint

LCP measures how long it takes for the largest visible element on the screen to appear. On most pages this is a hero image, a banner or a large block of text. It answers a simple question from the visitor's point of view: when does the page look ready?

Good: 2.5 seconds or less. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor.

INP: Interaction to Next Paint

INP measures how quickly the page responds visually after a visitor interacts with it. That includes tapping a menu, clicking an Add to cart button or opening a filter. It looks at interactions across the whole visit and reports one of the slowest ones.

Good: 200 milliseconds or less. Between 200 and 500 milliseconds needs improvement. Over 500 milliseconds is poor.

INP replaced an older metric, First Input Delay (FID), in March 2024. FID only measured the delay before the first interaction. INP is stricter because it considers interactions throughout the visit. If an older report mentions FID, it is out of date.

CLS: Cumulative Layout Shift

CLS measures how much the content moves around unexpectedly while the page loads. You have seen this when you try to tap a link and an advert loads above it, pushing the link down so you tap something else. CLS is a score with no unit.

Good: 0.1 or less. Between 0.1 and 0.25 needs improvement. Over 0.25 is poor.

How the scores are judged

Google assesses each metric at the 75th percentile of real visits. In simple terms, at least three out of four visits need to reach the good threshold for a page to pass. This means you cannot pass on the strength of fast visits from office Wi-Fi alone. Slower phones and mobile data connections count too, which matters a lot for Indian audiences who mostly browse on mobile.

Google reports mobile and desktop separately. Your mobile scores are usually the ones to focus on first.

Where to check your scores

PageSpeed Insights

Enter any page address into PageSpeed Insights, Google's free tool. The top section shows real-user data for that page or for your whole site, if Google has enough visits to report. The lower section shows a lab test with a list of specific suggestions. Use the real-user data to judge whether you have a problem. Use the lab suggestions to find the cause.

Search Console Core Web Vitals report

If your site is verified in Google Search Console, open the Core Web Vitals report. It groups similar pages together and shows which groups are good, need improvement or are poor. This is the best place to see problems across the whole site, such as all product pages failing LCP.

Smaller sites may not have enough traffic for real-user data. In that case, the lab test in PageSpeed Insights is still a useful guide.

Common causes and fixes

Slow LCP

• Large, uncompressed images. Resize images to the size they display at and use modern formats such as WebP or AVIF.
• The main image loads late. Make sure the hero image is not lazy-loaded and that the browser knows to fetch it early.
• Slow server response. Cheap shared hosting, no caching or a server far from your visitors all add delay. Good hosting, page caching and a content delivery network help.
• Too many fonts, scripts and stylesheets that block the page from showing. Remove what you do not use and defer what is not needed straight away.
• Sliders and videos at the top of the page. A single well-optimised image usually loads much faster.

Poor INP

• Heavy JavaScript. Large themes, page builders and many plugins add code that keeps the browser busy. When the browser is busy, it cannot respond to taps.
• Third-party scripts. Chat widgets, tracking tags, heatmaps and social embeds all compete for the same processor time. Keep only the ones you actively use.
• Long tasks on click. If a button triggers a lot of work, developers can break it into smaller steps or show feedback first and do the work after.

High CLS

• Images and videos without set dimensions. Give every image a width and height so the browser reserves the space.
• Adverts, banners and pop-ups that push content down. Reserve space for them, or place them where they do not move existing content.
• Web fonts that swap late and change the size of text. Preloading key fonts and choosing sensible fallback fonts reduces the jump.
• Content injected above existing content, such as cookie bars or offer strips. Overlay them, or reserve their space from the start.

How much do Core Web Vitals affect rankings?

Core Web Vitals are part of Google's page experience signals. Google has said that it looks at many signals, and that relevance and helpful content come first. A fast page with weak content will not outrank a slower page that answers the question far better.

That said, speed matters to your visitors directly. People leave slow pages, they get frustrated when buttons lag, and they lose trust when content jumps around. Better scores mean a better experience for real customers, and that is reason enough to fix them. Any ranking benefit comes on top.

A simple checklist

1. Run your home page and two or three key pages through PageSpeed Insights on mobile.
2. Check the Core Web Vitals report in Search Console for groups of failing pages.
3. Fix the biggest problem first, usually images or hosting for LCP.
4. Audit plugins and third-party scripts. Remove anything you do not use.
5. Set dimensions on images and reserve space for banners and adverts.
6. Re-test after changes. Real-user data in Search Console takes around 28 days to fully reflect fixes.
7. Check again after any major site change, new plugin or new marketing tag.

How WebCrea can help

We audit Core Web Vitals using both real-user data and lab tests, then fix the causes in your theme, hosting, images and scripts. We build new sites with these measurements in mind from the start.