Core Web Vitals for Non-Technical Agencies (2026 Plain-English Guide)
What LCP, FCP, CLS, and TBT actually mean, why Google uses them to rank pages, and how to spot and pitch fixes — without needing to be an engineer.
Most agency owners pitching small businesses on SEO have learned to nod knowingly when Core Web Vitals come up. This guide is for the ones tired of nodding. It covers what each metric is in plain English, why Google cares, and exactly how to talk about them with a non-technical small-business owner — without sounding like you're reciting a textbook.
What Core Web Vitals are (in plain English)
Core Web Vitals are Google's attempt to measure 'how it feels to use this page on a phone'. They're a small set of numerical metrics that proxy for the human experience: how fast you see something, how stable it stays, how responsive it is when you tap. Google built them because subjective 'feels slow' wasn't measurable, and unmeasurable things can't be ranked on.
The agency-friendly translation: Core Web Vitals are how Google decides whether your prospect's site is a pleasant or unpleasant place to land. Bad scores hurt rank; they also hurt conversion of the visitors who get there. Both halves of that hurt — independently and at the same time.
The four metrics that matter most
| Metric | What it measures | Plain English | Pass threshold |
|---|---|---|---|
| LCP — Largest Contentful Paint | How long until the biggest above-the-fold element appears | How long before the page 'feels loaded' | Under 2.5 seconds |
| FCP — First Contentful Paint | How long until anything appears at all | How long the screen stays blank | Under 1.8 seconds |
| CLS — Cumulative Layout Shift | How much the page jumps around while loading | How often you tap the wrong thing because stuff moved | Under 0.1 |
| INP — Interaction to Next Paint | How fast the page responds when you tap or type | How sluggish it feels to interact with | Under 200ms |
| TBT — Total Blocking Time | How long the page is frozen on JavaScript | Why the page is unresponsive even though it 'looks' loaded | Under 200ms (lab proxy for INP) |
Three of these are the official Core Web Vitals (LCP, CLS, INP). FCP and TBT are closely related metrics Lighthouse reports alongside them — useful for diagnosis, not directly the ranking signal. When agencies say 'we need to fix your Core Web Vitals', they usually mean all of them.
LCP is the one to start with. It's the single biggest driver of perceived speed and the easiest to explain. 'Your biggest image takes 5 seconds to appear' is intuitive; 'your INP is 320ms' isn't.
Why Google uses them to rank pages
Google's stated reason: searchers prefer fast, stable pages, and Google's job is to rank pages searchers prefer. The unstated reason: Google can measure these objectively from real-user data (Chrome reports them anonymously), so they don't have to guess at quality.
For local-services SEO specifically, Core Web Vitals matter more than they do for, say, a long-form article. Local searches are mobile-heavy and decision-driven. The Local Pack shows three results; rank #4 effectively means invisible. A slow site that gets penalized to #4 has lost most of its traffic, and the visitors who do arrive bounce because of the same slowness. Compounding penalty.
How to audit them yourself in 60 seconds
Two equally valid approaches:
- 1Google PageSpeed Insights (pagespeed.web.dev). Paste a URL, get the Lighthouse score plus real-user CrUX data. Most authoritative because it's Google's own tool.
- 2Our free real-Chromium audit. Same Lighthouse engine, same scores, but cleaner UI and lets you copy results into a client report. Built for agency workflows.
Both give you the four scores out of 100 (Performance, SEO, Accessibility, Best Practices), the specific failed audits, and the Core Web Vitals breakdown. For a single-site spot-check that's enough; for prospecting at scale, you want a tool that audits a whole city of one niche at once — audited lead lists do exactly that.
How to explain them to a client
Small-business owners don't care about LCP or CLS — they care about what the metrics mean for their business. Translation table:
| Don't say | Say instead |
|---|---|
| Your LCP is 4.7 seconds, which fails the Core Web Vitals threshold. | Your homepage takes nearly 5 seconds to feel loaded on a phone. Most customers leave by then. |
| Your CLS is 0.32, indicating significant layout instability. | Your buttons move around while the page loads, so customers tap the wrong thing and leave. |
| Your INP exceeds the 200ms threshold. | The site feels sluggish when customers tap things — they assume it's broken. |
| You need to optimize your largest contentful paint. | We need to speed up the main image on your homepage — it's the biggest single fix. |
The pattern: keep the metric out of the sentence; keep the customer experience and the business impact in. Save the technical names for the proposal where you justify the work.
Which fixes are no-code, which need a dev
Worth knowing which fixes you can sell as DIY tweaks and which need real engineering work:
| Fix | Skill level | Typical score impact |
|---|---|---|
| Compress hero/banner images, convert to WebP | WordPress plugin or Wix setting | +10–25 Performance |
| Remove autoplaying hero video | Site builder setting | +10–20 Performance |
| Lazy-load below-the-fold images | Plugin or theme setting | +5–10 Performance |
| Add explicit width/height to images | Theme tweak or developer | Big CLS improvement |
| Reduce third-party scripts (chat widgets, pixels) | Settings + judgment | +5–15 Performance |
| Defer non-critical CSS/JS | Developer | +10–20 Performance |
| Server-side rendering / static export | Developer / full rebuild | Large gains across the board |
| Switch to a faster host or CDN | Hosting change | +5–15 Performance |
For most small-business sites built on WordPress, Wix, or Squarespace, image compression alone moves the Performance score 15–25 points and takes 30 minutes. That's the easiest fix to bundle into a free first deliverable when you sign a client — quick win, builds trust, sets up the bigger work.
Don't promise a perfect 100 score. Most local-business sites won't hit it — and they don't need to. 'Good' across all Core Web Vitals (LCP <2.5s, CLS <0.1, INP <200ms) is the ranking-and-conversion target. Chasing 100 is a vanity project that burns hours.
For more on how to talk to local-business clients about technical work, see Google Maps leads for local SEO and how to find clients who need a website redesign.
Ready to extract your first leads?
Start with 500 free contacts every month. No credit card required.