Core Web Vitals: A Plain-English Guide for Small Business Owners

In 2021 Google made Core Web Vitals a ranking factor. Your site's performance on three metrics directly affects your Google search position.

The Three Core Web Vitals

LCP (Largest Contentful Paint): How fast does your page load? Under 2.5 seconds is "Good." The most common culprit is an unoptimized hero image. Compress images and ensure fast server response.

INP (Interaction to Next Paint): How quickly does your page respond to clicks and taps? Under 200ms is "Good." Usually caused by too much JavaScript loading simultaneously — analytics, chat widgets, and tracking pixels competing for browser resources.

CLS (Cumulative Layout Shift): Does your page jump around as it loads? Under 0.1 is "Good." Caused by images without defined dimensions, ads loading after content, and fonts loading late.

How to Check Your Scores

Google Search Console → Core Web Vitals report. Also run your URL through PageSpeed Insights (pagespeed.web.dev) for specific, actionable recommendations per page.

Practical Fixes for WordPress

Compress and size images correctly (fixes LCP), defer non-critical JavaScript (fixes INP), add explicit dimensions to all images (fixes CLS). WP Rocket handles many of these automatically. For persistent issues, our speed optimization service targets each metric specifically.

It's Not Just About Rankings — It's About Conversions

It's easy to treat Core Web Vitals as a pure SEO checkbox, but the underlying metrics measure something visitors feel directly. A slow LCP means someone is staring at a blank screen deciding whether to leave. A sluggish INP means a tap on your "Call Now" button doesn't respond right away, and a hesitant visitor abandons rather than waits. Layout shift means someone accidentally taps the wrong thing as content jumps around, which is a fast way to lose trust. Sites that fix Core Web Vitals issues consistently see improvements in both search rankings and on-site conversion rate — the ranking boost is really a side effect of fixing something that was already costing you visitors.

Why Your PageSpeed Score and Search Console Numbers Don't Match

A common source of confusion: you run your homepage through PageSpeed Insights, get a good score, then check Search Console's Core Web Vitals report and see a "Poor" rating for the very same page. Both tools measure Core Web Vitals, but they're pulling from different data. PageSpeed Insights runs a single simulated test from Google's servers on a fixed, throttled connection. It's useful for diagnosing what to fix, but it's one snapshot, not a real visitor's experience.

Search Console's Core Web Vitals report, by contrast, pulls from the Chrome User Experience Report (CrUX) — real, anonymized data from actual Chrome users who visited your site, aggregated over a rolling 28-day window. That number reflects the mix of devices, connection speeds, and locations your actual visitors have, which is almost always messier than a lab test run on a fast connection. A visitor on an older phone with patchy mobile data will post worse numbers than Google's lab test ever would, and enough of those visits will drag your field score down even when your lab score looks great.

This matters practically because fixing your lab score doesn't automatically fix your field score, and vice versa. If most of your traffic is mobile users on average connections, prioritize fixes that help the median real visitor rather than the best-case lab run: reduce total page weight, avoid loading anything non-essential above the fold, and test your actual mobile experience on a throttled connection instead of only trusting a clean lab result. A site with genuinely poor real-world Core Web Vitals scores rarely has one single cause — it's usually an accumulation of plugins, scripts, and unoptimized media that only shows up once real traffic, on real devices, hits the page.

Common Questions