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

A page that loads slowly, reacts late to taps or jumps around while you read loses visitors, whatever its content. Google measures these experiences with three metrics called Core Web Vitals, and uses them as part of how it evaluates pages. The good news is that the most common problems on small business websites have straightforward fixes.

The three metrics#

A page passes when at least 75% of real visits meet the "good" threshold for each metric. The definitions and thresholds come from Google's Web Vitals documentation.

How to check your site#

• PageSpeed Insights shows field data from real Chrome users (when your site has enough traffic) and a lab test with suggestions.
• Google Search Console has a Core Web Vitals report that groups your URLs into good, needs improvement and poor.
• Chrome DevTools (Lighthouse and the Performance panel) for detailed testing while you fix things.

The page speed check in the Tekservix SEO tools runs a Lighthouse test for any URL and lists the fixes, which is a quick starting point before digging into DevTools.

Remember the difference: field data is what real visitors experienced and what Google uses; lab data is a single simulated run, useful for diagnosing. Fixes show up in the lab immediately but take up to 28 days to appear fully in field data.

Improving LCP#

The LCP element is usually the hero image or the main heading. Typical causes of a slow LCP, and fixes:

• A huge hero image. Resize it to the size it's displayed at and use a modern format (WebP or AVIF). A 4000-pixel photo shown at 1200 pixels wastes most of its weight. See compressing images for your website.
• The hero image is lazy-loaded. Lazy loading is great for images further down, but the main image should load immediately. Add fetchpriority="high" to it.
• Slow server response. Cheap shared hosting and heavy plugins make the first byte slow. Use caching, and a CDN if your visitors are spread across countries.
• Render-blocking CSS and fonts. Load only the CSS the page needs, and use font-display: swap so text shows while fonts load.

Improving INP#

Poor INP means the browser is too busy running JavaScript to respond to the visitor. Common culprits:

• Too many third-party scripts: chat widgets, several analytics tools, ad scripts, social embeds. Remove what you don't use; delay the rest until after the page is interactive.
• Heavy page builders and sliders that run a lot of code on every interaction.
• Long tasks: big chunks of JavaScript that block the main thread. Developers can split them up so the browser can respond between steps.

Analytics is a frequent offender. A lightweight, cookie-free script does the same basic job with far less code; see cookie-free website analytics.

Improving CLS#

Layout shift is the page jumping as things load: you go to tap a button and an ad pushes it down. Fixes:

• Set width and height on images and videos, so the browser reserves space before they load.
• Reserve space for ads, embeds and banners with a fixed-height container.
• Don't insert content above existing content, such as cookie bars or promo banners that push the page down. Overlay them instead.
• Use font-display: optional or matched fallback fonts if web fonts cause text to reflow.

A typical small-site plan#

1. Run a test on your home page and your most visited page.
2. Compress and resize every large image; set width and height attributes.
3. Remove unused plugins and third-party scripts.
4. Turn on caching and, if possible, a CDN.
5. Test again, then check Search Console over the following weeks.

On most small business sites, steps 2 and 3 alone move LCP and CLS from "poor" to "good". Our broader guide to improving website speed goes further.

WordPress and website builders#

Many small business sites run on WordPress, Wix or similar builders, where you can't rewrite code. You can still make a big difference:

• Choose a lightweight theme rather than a multipurpose one that loads every feature on every page.
• Audit plugins: deactivate anything unused, and replace heavy sliders, popups and social feeds with simpler options.
• Use a caching plugin or the builder's built-in performance settings.
• Upload images at the right size in the first place; image optimisation plugins help, but starting smaller is better.

Test after each change so you know which one helped.

How much do they matter for SEO?#

Keep it in proportion. Google has said that great content can still rank with average page experience, and that Core Web Vitals work more like a tie-breaker between similar pages. But speed affects visitors directly: people leave slow pages, especially on mobile data. Treat the vitals as part of your SEO audit, fix the obvious problems, and then put your effort back into content.

Keeping them good#

Scores slip over time as new images, plugins and scripts are added. Make a habit of resizing images before upload, question every new third-party script, and recheck your key pages every month or after any redesign.

Speed decides how your page feels once someone arrives; the meta description decides whether they click through from Google in the first place.