Only 3% of local business websites pass Google’s speed test. That means your competitors are almost certainly failing it. The question is whether you are too.
Here is why it hurts. Your site takes nine seconds to load while customers wait three. They tap your listing, stare at a blank screen, then call the next business. You paid for the ranking, and someone else got the customer.
The fix is easier than you think. This guide explains Core Web Vitals in plain English, shows their real effect on local rankings, and walks you through free fixes. No coding needed, just one afternoon.
Key Points:
- Core Web Vitals are three Google metrics: LCP (loading), INP (responsiveness), and CLS (visual stability).
- Good scores mean LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
- They do not directly affect Map Pack rankings, but act as a tie-breaker in organic results.
- Test free with PageSpeed Insights and Google Search Console, no coding needed.
- Most fixes are simple: compress images, upgrade cheap hosting, and remove heavy plugins or popups.
What Are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure how real visitors experience your website. They track loading speed, responsiveness, and visual stability. Google introduced them in May 2020 as part of its page experience system.
Think of them as a health check for your site. A doctor checks pulse, blood pressure, and temperature. Google checks how your page loads, reacts, and holds steady. The data comes from real Chrome users, not lab tests. So your scores reflect what actual customers feel on their phones.
What Metrics Does Google Include in Core Web Vitals?
Google includes three metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). LCP tracks loading, INP tracks responsiveness, and CLS tracks visual stability. A Whitespark study of 4,158 local landing pages found only 3% earned a “Good” mobile score, so passing these puts you ahead of most competitors.
Why Are Core Web Vitals Important for SEO?
Google uses three Core Web Vitals metrics to evaluate your website’s user experience. They are not the biggest factor, though. Content quality and relevance still come first.
Think of them as a tie-breaker. When two local businesses offer equal content and authority, the faster site wins. That small edge can decide who gets the call.
How Core Web Vitals Affect Search Rankings
Better scores give your pages a small but real ranking boost in organic search results. A Google and Deloitte study found that cutting load time by 0.1 seconds lifted conversions by up to 8.4%. AI tools like Google AI Overviews, ChatGPT, and Perplexity also favor fast, stable pages when picking sources.
Mobile Friendliness, HTTPS, and Intrusive Interstitials
Core Web Vitals work alongside three other page experience signals: mobile friendliness, HTTPS security, and popup control. Google judges your mobile version first, so a fast desktop site with a slow mobile version still fails. Avoid intrusive popups like full-screen offers and forced email boxes, while small banners and cookie notices remain safe.
Understanding the Three Core Web Vitals
The three Core Web Vitals are LCP for loading, INP for responsiveness, and CLS for visual stability. Each one grades a different moment in your visitor’s experience. Knowing what each metric measures helps you fix the right problem.
Your scores come from real visitor data over 28 days. Google looks at the 75th percentile, meaning most visits must pass.One good test result proves nothing.
Largest Contentful Paint (LCP)
LCP measures how long the largest element on your screen takes to load. That element is usually a hero image, a banner photo, or a big headline.
Interaction to Next Paint (INP)
INP measures how fast your page responds when someone taps, clicks, or types. It replaced FID in March 2024 and tracks every action, not just the first one. A good score stays under 200 milliseconds, so menus, forms, and buttons must react without delay.
Cumulative Layout Shift (CLS)
CLS measures how much your page content jumps around while loading. You have felt this when a button moves right as you tap it. Google wants a score under 0.1, and elements like ads, review widgets, and late-loading fonts cause most shifts.
First Input Delay (FID): The Legacy Metric
FID is the retired metric that INP replaced in March 2024. It only measured the delay before your first click, so almost every site passed easily. Many older local SEO guides still teach FID, so ignore any advice built around its 100 millisecond target.
Other Performance Metrics That Matter
Four supporting metrics reveal the causes behind poor Core Web Vitals scores: TTFB, FCP, TBT, and Speed Index. These do not affect rankings directly. Instead, they point to the root cause when a main metric fails.
The most useful one is Time to First Byte (TTFB). It measures how fast your server responds, and Google recommends 800 milliseconds or less. A slow TTFB usually means cheap hosting, and it drags down your LCP before anything even loads.
Here is what each metric tells you:
- TTFB (under 800 ms): Server speed. A high score points to hosting problems.
- FCP (under 1.8 seconds): When the first content appears. Elements like text, logos, or icons.
- TBT (under 300 ms): How long scripts block the page. Scripts like chat widgets, trackers, or booking tools.
- Speed Index (under 4.3 seconds): How fast the page becomes visible.
You do not need to memorize these. PageSpeed Insights shows them automatically under your main scores. Treat them as clues, not targets.
How Does Google Measure Core Web Vitals?
Google measures Core Web Vitals using real visitor data from the Chrome User Experience Report (CrUX). This data comes from actual Chrome users, not lab tests.Google takes the 75th percentile of visits over a rolling 28-day window, so at least 75% of your visitors must get a “Good” experience.
Real-world conditions shape your scores too. Factors like visitor devices, network speeds, and locations all affect the numbers. A page that feels fast on office WiFi may still fail on a customer’s 4G phone.
One thing catches many small businesses off guard. Low-traffic pages often have no CrUX data at all. When that happens, Google falls back on your domain-level “origin” scores instead.
How to Measure Core Web Vitals
You can test Core Web Vitals free using two tools: Google Search Console and PageSpeed Insights. Both need zero coding skills. Search Console shows site-wide problems, while PageSpeed Insights checks one page at a time.
Start with these two before anything else. Together, they tell you which pages fail and why. Everything else is optional.
Google Search Console Core Web Vitals Report
The Search Console report shows which pages on your site pass or fail, grouped by template. Pages like service pages, location pages, and blog posts get grouped together, so one fix often repairs many URLs at once. After fixing, click “Start Tracking” and Google validates your changes over 28 days.
PageSpeed Insights and Other Testing Tools
PageSpeed Insights combines real visitor data with a live lab test for any single URL. Always check the “field data” section at the top, since that is what Google uses for rankings. Advanced tools like GTmetrix, WebPageTest, and Chrome DevTools exist too, but most business owners never need them.
How to Improve Your Core Web Vitals
You improve Core Web Vitals by fixing images, hosting, scripts, and layout issues one metric at a time. Run PageSpeed Insights first to see which metric fails. Then apply the fixes below that match your problem.
To fix LCP (slow loading):
- Compress hero images under 200KB using formats like WebP or AVIF.
- Upgrade from cheap shared hosting if your server responds slowly.
- Never lazy-load your top banner image. It must load first.
To fix INP (slow response):
- Remove unused plugins like old sliders, popup makers, and social feeds.
- Delay scripts like chat widgets, trackers, and booking tools until someone interacts.
- On WordPress, one plugin like WP Rocket handles most of this.
To fix CLS (jumping content):
- Set fixed sizes for images, ads, and embedded review widgets.
- Load fonts with “swap” so text never disappears and reappears.
- Keep popups floating over content instead of pushing it down.
Start with images and hosting. The Whitespark study found local pages average 9.5 seconds for LCP, and oversized photos cause most of it. Compressing them is free, takes an afternoon, and often moves you from “Poor” to “Good” alone.
Do Core Web Vitals Affect Local Rankings?
No, Core Web Vitals do not directly affect your Google Maps or Local Pack rankings.A Whitespark study of 4,500 Google Business Profiles confirmed this. . Map Pack positions depend on three signals: proximity, relevance, and prominence.
Still, weak site performance hurts your organic authority, which quietly feeds the prominence signal. The bigger risk is conversions, since local pages average 9.5 seconds to load on mobile. You might win the Map Pack spot, then lose the customer before your page opens.
Common Core Web Vitals Mistakes Local Businesses Make
The biggest mistake local businesses make is embedding a live Google Maps iframe on every page. That single embed loads 1 to 2MB of scripts and can drop your mobile score below 80. Show a static map image instead, and load the real map only when someone taps it.
Other common mistakes include:
- Uploading raw phone photos over 4MB without compression.
- Using $5 shared hosting with slow server response.
- Stacking page builder addons like bloated Elementor setups.
- Running big sliders above the fold.
- Adding instant popups that shift content and hurt CLS.
None of these need advanced skills to fix. Compressing photos, upgrading hosting, and removing extras are all afternoon jobs.
FAQs
What Are Core Web Vitals?
Core Web Vitals are three Google metrics measuring loading speed (LCP), responsiveness (INP), and visual stability (CLS). They come from real Chrome visitor data.
What Is a Good Core Web Vitals Score?
LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. At least 75% of real user visits must pass all three metrics.
Why does my site pass on desktop but fail on mobile?
Phones use slower networks and weaker processors. Google judges mobile first, so that is the version to fix.
What happens if my Search Console report shows no data?
Your site has too little traffic to generate CrUX data. Google then uses your domain-level origin scores instead.
How long until my fixes show up in Google?
Up to 28 days, since Google measures a rolling 28-day window. Click “Start Tracking” in Search Console to monitor progress.
What happens if I ignore Core Web Vitals completely?
You lose customers before rankings. A slow site can win a Map Pack spot yet still lose the call or booking.
Conclusion
Core Web Vitals measure three things every visitor feels: loading speed, responsiveness, and visual stability. They will not directly improve your Map Pack rankings. Instead, they help break ties in organic results. Ignoring them costs you customers.
The bar sits low. Only 3% of local businesses pass on mobile. Most failures come from simple issues like oversized photos, cheap hosting, and heavy plugins. Fix the basics, and you jump ahead of nearly every competitor in your area.
Run your homepage through PageSpeed Insights today. It takes 30 seconds and shows you exactly what to fix first.
3 August 2026
