Core Web Vitals Explained for Business Owners: Why Site Speed Costs You Leads
By Alexey Chasin · Updated September 18, 2026 · 6 min read
Core Web Vitals are three numbers Google uses to measure how a page feels to a real visitor: how fast the main content appears (LCP, good is under 2.5 seconds), how quickly the page responds to a tap (INP, good is under 200 milliseconds), and whether things jump around while loading (CLS, good is under 0.1). Google uses them as a ranking tiebreaker, and visitors abandon pages that fail them. You can check any site free at pagespeed.web.dev.
The three numbers
| Metric | What it measures | Good | Common cause of failure |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main content is visible | Under 2.5 s | Huge hero images, slow hosting, render-blocking scripts |
| INP (Interaction to Next Paint) | How fast the page reacts when you tap or click | Under 200 ms | Heavy JavaScript, chat widgets, animation libraries |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | Under 0.1 | Images without dimensions, late-loading fonts, ads and embeds |
Why business owners should care
Two reasons. Google uses page experience to decide between pages with similar content, so a slow site loses the tie to a fast competitor. And people leave: a page that takes five seconds on a phone loses a large share of visitors before they see the phone number. For a local business, that is calls that never happen.
How to check your site
- Go to pagespeed.web.dev and enter your homepage. Choose Mobile.
- The top section shows real-user data if Google has enough traffic; the bottom shows a lab test.
- Green on all three vitals is passing. Orange or red on any is failing.
- Check your busiest service page too, not just the homepage.
What usually fixes them
- LCP: compress and resize images, preload the hero image, remove render-blocking scripts and fonts, use a fast host with a CDN.
- INP: remove heavy JavaScript, animation libraries, chat widgets and tag-manager bloat.
- CLS: set width and height on every image, load fonts with swap, reserve space for embeds.
Why builders and heavy themes fail
Wix, Squarespace and page-builder WordPress themes ship the whole editor's code on every page. You can improve images and embeds, but the floor is the platform. A hand-coded static site ships only what the page needs, which is why it scores 95 to 100 instead of 40 to 70.
Every page on this site passes all three vitals on mobile. Test it, then test your own. If yours fails, a free call tells you whether a fix or a rebuild is the right move.