Core Web Vitals for small business websites, in plain English

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 someone taps or clicks, and whether things jump around while it loads. For most small business sites, the fixes are not exotic. Smaller images, fewer scripts, decent hosting and a little care with layout get you most of the way.

Here is what each metric means, how to check yours and what to fix first.

The three metrics

Google assesses each metric at the 75th percentile of page visits. In plain terms, at least three out of four visits need to hit the "good" threshold for the page to pass. You can find the definitions in our glossary entry on Core Web Vitals.

INP replaced an older metric, First Input Delay, in 2024. If you read older advice that mentions FID, the idea is similar, but INP is stricter because it looks at interactions across the whole visit, not just the first one.

Largest Contentful Paint (LCP)

LCP is usually the hero image, a large heading or a background video at the top of the page. If that element is a 4 MB photo straight off a camera, LCP will be slow no matter how good your hosting is.

Common causes of slow LCP:

• Oversized or uncompressed hero images
• Slow server response (cheap or overloaded hosting, no caching)
• Render-blocking CSS and JavaScript loaded before the content
• Sliders and carousels that load several large images at once
• Lazy-loading the hero image, which delays the one image that should load first

Interaction to Next Paint (INP)

INP is about what happens after the page loads. A visitor taps the menu, opens an accordion or submits a form. If the browser is busy running JavaScript, the response lags.

Common causes of poor INP:

• Too many third-party scripts: chat widgets, heatmaps, ad pixels, review widgets, popups
• Heavy page builders that ship a lot of JavaScript on every page
• Large, complex pages with thousands of elements
• Custom scripts that do too much work on every click or scroll

Cumulative Layout Shift (CLS)

CLS measures unexpected movement. You go to tap "Call now" and a banner loads above it, pushing the button down, and you tap something else instead. That is layout shift, and it is as annoying as it sounds.

Common causes of CLS:

• Images and videos without set dimensions
• Ads, embeds or cookie banners that push content down when they load
• Web fonts that swap in and change text size
• Content injected at the top of the page after load

How to check your site

You do not need special software. Three free tools cover it:

1. PageSpeed Insights. Enter a URL. The top section, "Discover what your real users are experiencing," shows field data from real Chrome users if your site has enough traffic. Below that is a lab test with a 0 to 100 score and specific suggestions.
2. Google Search Console. The Core Web Vitals report groups your URLs into good, needs improvement and poor, for mobile and desktop separately. This is the best view of the whole site.
3. Chrome DevTools. The Performance and Lighthouse panels let a developer see exactly what is slow on a page.

One point causes a lot of confusion: the 0 to 100 score is a lab simulation, not your Core Web Vitals. It is useful for diagnosis, but Google Search uses the field data. A page can score 70 in the lab and still pass in the field, or the reverse. Small sites with low traffic may not have field data at all, in which case the lab results are your best guide.

Check mobile first. Most small business traffic is mobile, phones are slower than laptops, and mobile is where most sites fail.

What to fix first

Work in this order. The first few items solve most problems we see on small business sites.

1. Fix your images

• Resize images to the size they actually display. A 4000-pixel-wide photo in a 1200-pixel space is wasted weight.
• Use modern formats like WebP or AVIF where your platform supports them.
• Do not lazy-load the hero image. Lazy-load images further down the page.
• Always set width and height (or an aspect ratio) so the browser reserves space.

2. Audit third-party scripts

List every script on the site: analytics, tag manager, chat, heatmaps, pixels, review widgets, popups. Remove anything nobody uses. Load what remains after the main content where possible. Marketing tools are one of the most common causes of poor INP.

3. Trim plugins and page builder weight

On WordPress, each plugin can add CSS and JavaScript to every page. Deactivate and delete plugins you do not need. If a heavy page builder is the root problem, consider a lighter theme or the block editor for new pages. Our comparison of Elementor, Divi and Astra covers the performance tradeoffs.

4. Improve hosting and caching

Slow server response hurts LCP before anything else happens. Page caching, a CDN and current PHP versions make a real difference. If you are on an overloaded entry-level plan, moving to better hosting is often the single biggest improvement. See our guides on choosing web hosting and when managed WordPress hosting is worth it.

5. Reserve space for everything that loads late

Cookie banners, announcement bars, embedded maps and video should have space reserved, or should overlay the page rather than push it down.

6. Rethink sliders and autoplay video

Hero sliders rarely help conversions and almost always hurt LCP. A single strong image and a clear headline usually perform better on every measure.

Does platform choice matter?

Yes, but less than how the site is built. A carefully built WordPress site can pass easily, and a careless Next.js site can fail. That said, some platforms make good results easier:

• Hosted builders like Squarespace, Webflow and Framer handle hosting, CDN and image optimization for you. Results are usually decent, but you have less control when something is slow.
• WordPress can be very fast or very slow. It depends on the theme, builder, plugins and hosting.
• React and Next.js sites with static or edge rendering can be extremely fast, which is a big reason we use them for performance-sensitive projects. We covered why in React and Next.js for business websites.

Why this matters beyond rankings

Core Web Vitals are part of Google's page experience signals, but they are not the most important ranking factor. Relevant, helpful content still wins. The bigger reason to care is people. A slow, jumpy page loses visitors before they read your offer, and a laggy form loses leads. Fixing vitals is usually a conversion improvement first and an SEO improvement second.

The short version

Check your site in PageSpeed Insights and Search Console, focusing on mobile field data. Fix images first, then scripts and plugins, then hosting. Reserve space for anything that loads late. Most small business sites can reach "good" without a rebuild.

If your site is still slow after the basics, or you are planning a rebuild with performance in mind, our SEO and AEO work includes performance audits, or you can get in touch.