( GUIDES — — 7 MIN READ )
Core Web Vitals explained for small business owners
What LCP, INP and CLS actually mean, why Google measures them, how to check your own site in five minutes and the fixes that make the biggest difference — in plain English, no developer jargon.
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how quickly it shows its main content, how quickly it responds when you tap something, and whether things jump around while it loads. They are part of Google's page experience signals. They will not rescue a page with poor content, but between two similarly useful pages, the faster, steadier one has the edge — and it almost always converts better too.
The three metrics
Largest Contentful Paint (LCP) — does it load fast?
The time until the biggest thing on screen — usually a hero image or headline — has appeared. Good is 2.5 seconds or less. Slow LCP is usually caused by huge images, slow hosting or too much code having to load before anything is shown.
Interaction to Next Paint (INP) — does it respond quickly?
How long the page takes to visibly react when someone taps a button, opens a menu or types in a form. Good is 200 milliseconds or less. INP replaced the older First Input Delay metric in 2024. Poor INP is nearly always heavy JavaScript — chat widgets, tracking scripts, sliders and page-builder bloat all compete for the same processor.
Cumulative Layout Shift (CLS) — does it stay still?
A score for how much content jumps around as the page loads — the classic "I went to tap the link and an advert pushed it down". Good is 0.1 or less. It is caused by images without dimensions, late-loading banners and fonts that swap size.
Google assesses each metric at the 75th percentile of real visits, so three out of four visitors need a good experience for the page to pass.
How to check your site in five minutes
- Go to PageSpeed Insights (pagespeed.web.dev) and enter your homepage.
- Look at the top section first: "Discover what your real users are experiencing". That is real-world data from Chrome users, and it is what Google uses. If your site is too new or quiet, this section will be empty.
- The lower "Diagnose performance issues" section is a lab test. It is useful for finding problems, but the score itself is not a ranking factor — do not chase 100.
- Repeat for your most important service page and contact page, on mobile.
- In Google Search Console, open the Core Web Vitals report to see which groups of pages pass or fail across the whole site.
The fixes that make the biggest difference
- Compress and resize images. Serve modern formats like WebP or AVIF, and never upload a 4,000-pixel photo to fill a 600-pixel space.
- Give every image and video set width and height so the browser reserves space for it — the quickest CLS win there is.
- Do not lazy-load the hero image. Lazy-load everything below the fold instead.
- Audit third-party scripts. Every chat widget, heatmap, pixel and embed costs time. Remove what you do not use and load the rest after the page is interactive.
- Host fonts yourself, limit the number of weights, and use font-display: swap with matched fallback sizes.
- Choose decent hosting with a CDN, so pages are served from a location near your visitors.
- If your site is built with a heavy page builder or a theme packed with features you do not use, a rebuild is often cheaper than endless optimisation.
Does speed matter more than design?
It is a false choice. Our own site uses WebGL, scroll animation and motion throughout, and it is built to keep Core Web Vitals in the green by deferring the heavy parts until the page is usable. Good engineering lets you have both. If you want a site that feels alive and still ranks, that is exactly what we build — and if you want your current site audited for speed and SEO, get in touch.
