When I rebuilt our own website, speed was one of the main reasons. I wrote about that in why we rebuilt our website as a static site. Core Web Vitals are how Google measures the part of speed customers actually feel.
The three Core Web Vitals
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually the big image or headline, shows up | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
Those thresholds are Google’s published targets, measured on how most of your real visitors experience the page.
LCP: does it look loaded?
LCP is the moment the biggest thing on screen finishes appearing. On most small business sites, that’s the hero image or main headline. If it takes too long, visitors stare at a blank or half-built page and leave. Common causes are huge images, slow hosting and too much code loading before the content.
INP: does it respond?
INP measures the delay between tapping something, like a menu or a button, and the page reacting. A slow INP feels like the site is frozen. The usual cause is heavy JavaScript: chat widgets, sliders, tracking scripts and page-builder code all competing for the phone’s attention.
CLS: does it hold still?
CLS measures unexpected movement. You’ve probably tried to tap a button just as an ad or image loaded above it, and tapped the wrong thing. That’s layout shift. It’s usually caused by images without set dimensions, late-loading banners and fonts that swap in.
How to check your scores
- PageSpeed Insights. Enter your web address. The top section shows field data from real visitors if Google has enough. The lower section is a lab test.
- Google Search Console. The Core Web Vitals report groups your pages into good, needs improvement and poor, based on real visitor data.
Focus on field data when you have it. Lab scores bounce around and are best for diagnosing problems.
What usually fixes problems
Images. Resize images to the size they’re actually displayed, use modern formats like WebP or AVIF, compress them, and give them set dimensions. This alone fixes a lot of LCP and CLS problems.
Fewer scripts. Every chat widget, popup, slider and tracking pixel adds code. Remove what you don’t use, and load what you need after the main content.
Better hosting. Pages served from a content delivery network, close to the visitor, arrive faster. Our sites are served from Cloudflare’s network for this reason.
Leaner builds. Many page builders and heavy themes load code for features you never use. A static site built for one purpose sends far less.
Font loading. Use a small number of fonts and load them in a way that doesn’t block or shift the page.
Why this matters for a Lubbock business
Most of your visitors are on phones, sometimes on a weak signal in a parking lot or on a job site. A fast page gets read. A slow one gets the back button, and that customer calls the next company in the results. Speed affects rankings a bit, but it affects whether people stay and call a lot.
What to do next
Run your home page and your top service page through PageSpeed Insights on mobile. If both pass, you’re in good shape. If not, start with images and scripts. If you want it handled, our page speed optimization service fixes what can be fixed on your current site, and tells you honestly when a rebuild would be faster and cheaper than patching. My next speed post covers how to run a website speed test and read the results.