Core Web Vitals explained for business owners

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content appears, how quickly the page responds when you tap or click, and whether things jump around while it loads. They’re a ranking signal, but the bigger reason to care is simpler. Slow, jumpy pages lose customers.

What the three metrics measure

Metric	What it measures	“Good” threshold
LCP, Largest Contentful Paint	How long until the biggest thing on screen (usually a hero image or headline) has loaded	2.5 seconds or less
INP, Interaction to Next Paint	How quickly the page visibly responds after someone clicks, taps or types	200 milliseconds or less
CLS, Cumulative Layout Shift	How much the layout jumps around while loading	0.1 or less

Google looks at these for real visitors, at the 75th percentile, so most of your visitors need a good experience, not just the ones on fast connections.

Where to see your real scores

• Google Search Console → Core Web Vitals report: groups your URLs into good, needs improvement and poor, using real visitor data.
• PageSpeed Insights: shows real-user data for a page (if there’s enough traffic) plus a lab test with specific suggestions.

Lab scores, the 0–100 number, are useful for debugging but aren’t what Google ranks on. Field data from real users is what counts.

The usual culprits on business sites

Slow LCP is usually caused by:

• huge, uncompressed hero images or background videos;
• slow hosting or no caching;
• web fonts or sliders that block the page from showing anything;
• the hero image being lazy-loaded when it should load first.

Poor INP is usually caused by:

• too much JavaScript: page builders, plugins, chat widgets, tracking scripts;
• heavy third-party tags firing on every interaction.

High CLS is usually caused by:

• images and embeds without set dimensions;
• cookie banners, promo bars or ads pushing content down after load;
• web fonts swapping in at a different size.

Fixes ranked by effort

1. Compress and resize images, serve modern formats (WebP or AVIF), and give every image width and height attributes.
2. Don’t lazy-load the hero image. Load it first, with high priority.
3. Turn on page caching and a CDN. Often the biggest single win on WordPress sites.
4. Audit third-party scripts. Remove the ones nobody uses and delay the rest until after load.
5. Reserve space for banners, embeds and late-loading elements.
6. Use fewer fonts and weights, with font-display: swap.
7. Reduce plugins and page-builder add-ons that load scripts on every page.

When a rebuild beats patching

If a site carries years of plugins, a heavy theme and a page builder layered on top, patching can only go so far. A rebuild on a lean theme, keeping URLs and content intact, is sometimes cheaper than months of fixes. If you do rebuild, follow a migration checklist so you don’t trade a speed problem for a rankings problem.

We build sites to pass Core Web Vitals from launch, and include performance in our care plans. See our web solutions, or ask us to look at your scores.