What Core Web Vitals are
Google uses a set of measurements called Core Web Vitals to describe the experience of loading and using a web page. There are three of them right now: LCP, INP and CLS. Each one answers a simple question a visitor might ask without realizing it: Is it loading? Is it responding? Is it stable?
An important point up front: good scores won’t push a weak page to the top of Google. Relevance and quality still matter far more. But when two pages are similar, page experience can help, and a slow, jumpy site loses customers no matter where it ranks. Someone in Houston searching for an emergency plumber on a phone with two bars of signal won’t wait.
| Metric | Plain-English question | Google’s “good” threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long until I see the main content? | 2.5 seconds or less |
| INP (Interaction to Next Paint) | When I tap something, how fast does it react? | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | Does the page jump around while loading? | 0.1 or less |
LCP: how fast the main content shows
Largest Contentful Paint measures how long it takes for the biggest visible element, usually a hero image or a large headline, to appear. On most small business sites, the culprit behind a slow LCP is a huge, uncompressed hero photo or a slider loading five images at once.
Common causes of slow LCP:
- Hero images uploaded straight from a camera or phone at several megabytes.
- Slow or overcrowded shared hosting.
- Page builders and plugins loading lots of CSS and JavaScript before anything appears.
- Web fonts that block text from showing.
INP: how quickly the page responds
Interaction to Next Paint replaced an older metric (FID) in 2024. It looks at how quickly the page visibly reacts when someone taps a button, opens a menu or types in a form. If your mobile menu takes a noticeable beat to open, that’s INP.
Poor INP is usually caused by too much JavaScript: chat widgets, several tracking scripts, sliders, pop-ups and heavy themes all competing for the phone’s processor. Each one might seem harmless. Together they make the page feel sluggish.
CLS: whether things jump around
Cumulative Layout Shift measures unexpected movement. You’ve seen it: you go to tap “Call Now” and the button moves because a banner loaded above it. That’s frustrating, and on a service site it can mean a lost call.
Typical causes:
- Images without set width and height.
- Cookie bars, promo banners or ads that push content down after loading.
- Fonts that swap in and change text size.
- Embeds like maps or review widgets that expand after the page renders.
How to check your own site
You don’t need special software. Two free tools from Google cover most needs:
- PageSpeed Insights. Enter a URL and you’ll see field data from real Chrome users (when Google has enough of it) plus a lab test with specific suggestions. Always check the mobile results first.
- Search Console, Core Web Vitals report. Groups your URLs into good, needs improvement and poor, based on real-user data. Helpful for spotting templates with problems, like all your blog posts or all your city pages.
Test your homepage, your top service page and your contact page. Those are usually the pages that matter most for leads.
One thing that confuses many owners: the lab score (the big number out of 100) and the field data often disagree. The lab test simulates one load on a mid-range phone; field data reflects what real visitors experienced over the past 28 days. Google’s assessment is based on field data, so treat the lab score as a diagnostic tool, not a grade. A small local site may not have enough traffic for field data at all, and that’s normal. In that case, use the lab suggestions as a checklist and test on your own phone over cellular, not office Wi-Fi.
Quick wins that usually help
These fixes are worth trying before any big rebuild:
- Resize and compress images. A hero image rarely needs to be wider than about 1,600 pixels. Use modern formats like WebP or AVIF.
- Don’t lazy-load the hero image. Lazy-load images further down the page, but let the main one load right away.
- Remove what you don’t use. Old plugins, abandoned tracking pixels, a slider nobody looks at.
- Set image dimensions so the browser reserves space and nothing jumps.
- Use a caching plugin and a CDN if you’re on WordPress.
- Delay non-essential scripts like chat widgets until the visitor interacts or scrolls.
- Upgrade hosting if your server response time is consistently slow.
If those don’t get you into the green, the problem is often the theme or page builder itself. At that point a lean rebuild can be cheaper than endless patching. My WordPress development work starts with performance as a requirement, not an afterthought.
Not sure where your site stands? Send me your URL and I’ll tell you which of these issues are actually slowing it down.


