Core Web Vitals: The Ranking Tiebreaker Most Local Businesses Ignore

I've lost count of how many times a small business owner in Shelby has asked me why a competitor -- with the same star rating, the same number of reviews, and the same Google Business Profile categories -- sits above them in the local three-pack. They point to identical backlink profiles. They point to comparable review velocity. Everything looks equal on paper. But the Map Pack is not a tie. Google doesn't flip a coin. It picks the faster site. That's what Core Web Vitals does. It's the ranking tiebreaker nobody in Cleveland County is paying attention to, and it's costing businesses their top-three position every single day.

Whitespark analyzed 4,500 local business GBP landing pages in 2025 and the results were brutal. Only 3% passed all three Core Web Vitals metrics on mobile. 83% failed LCP -- Largest Contentful Paint, the time it takes for the biggest visual element on the page to render. The average for local business sites: 9.5 seconds. Google's threshold for "Good": 2.5 seconds. That's nearly four times the acceptable limit.¹ If you're running a plumbing business, a law firm, a restaurant, or a retail shop in Shelby, Kings Mountain, or Boiling Springs, your site is almost certainly part of that 83%. Not because you're doing something wrong. Because almost nobody in the local business space is doing it right.

Core Web Vitals aren't a primary ranking factor the way backlinks or reviews are. But when primary factors are equal -- and in small-town markets like Cleveland County they frequently are -- Core Web Vitals function as the definitive tiebreaker. The faster site wins. Every time. I've watched it happen across dozens of local SEO audits. Two roofing companies in Kings Mountain. Identical profile optimization. Similar review counts. The faster site holds position two. The slower site sits at position four. The difference in calls per month? Measurable in thousands of dollars.

An extensive study analyzing 4,500 local business Google Business Profile landing pages found that a mere 3% of local businesses achieved passing mobile performance scores across all metrics. 83% of local sites suffer from exceptionally poor LCP, logging an abysmal average of 9.5 seconds for primary content to load - nearly four times the acceptable threshold.

The three Core Web Vitals that decide rankings

Let me break each one down specifically so you know exactly what you're measuring and what the target is. LCP, or Largest Contentful Paint, tracks the time from when the page first starts loading to when the largest visual element becomes visible. On most local business sites, the LCP element is either the hero image, a background image, or a large heading text block. Google wants that element visible in under 2.5 seconds to earn a "Good" rating. Between 2.5 and 4.0 seconds is "Needs Improvement." Over 4.0 seconds is "Poor."³ When I run PageSpeed Insights on local business sites around Cleveland County, I routinely see LCPs between 8 and 15 seconds. That's not a marginal failure. That's an entire category of ranking opportunity being surrendered. And it's almost always one oversized hero image causing the whole thing. One image.

INP, or Interaction to Next Paint, replaced First Input Delay as a Core Web Vital in March 2024. It measures the longest interaction latency a user experiences across the entire page visit -- taps, clicks, and key presses. The threshold for "Good" is under 200 milliseconds. If someone clicks your phone number button and there's a visible delay before anything happens, that delay gets measured and factored into your INP score. Most local business sites I audit in Shelby fail this metric because of bloated JavaScript -- sliders nobody asked for, third-party chat widgets that load synchronously, and page builder scripts that fire on every interaction before the browser can repaint. The fix is usually removing things. Not adding them.⁴

CLS, or Cumulative Layout Shift, is the one metric that infuriates actual users and business owners alike. It measures how much visible content shifts position during loading. Every time you've visited a website on your phone, started reading, and then had the text jump because an image loaded above it -- that's CLS. Google's threshold is 0.1 or less for "Good." The most common cause on small business websites: images without explicit width and height attributes, late-loading web fonts that reflow text, and third-party embedded content like Google Maps iframes that load asynchronously without reserved space. 61% of local business sites pass CLS, which means 39% fail it outright.¹ If you've ever rage-closed a site because the button you were about to tap jumped away, you already understand CLS.

Core Web Vitals aren't a dominant primary ranking factor on their own. If your site loads in 1.5 seconds and a competitor's loads in 9.5 seconds but they have 200 more reviews, a stronger backlink profile, and a fully optimized GBP, they'll still outrank you. The tiebreaker scenario is specific. It applies when the primary signals are comparable -- roughly equal local authority, roughly equal review profile, roughly equal on-page optimization. In a market like Cleveland County, that happens constantly. Two HVAC companies serving the same zip code. Two restaurants on the same block of Lafayette Street. Two law firms with offices within half a mile of the courthouse. When the primary signals converge, speed becomes the needle-mover.

0.1 seconds of speed equals 8.4% more conversions

The Deloitte study gets cited often in web performance circles but I rarely see local business owners connect it to their own operations.² A 0.1-second improvement produces 8.4% more retail conversions and 8.3% more lead gen form submissions. If your HVAC company's site gets 500 visitors a month and converts at 4%, that's 20 leads. An 8.3% improvement adds roughly 1.6 more leads per month -- 19 more booked jobs per year. At an average HVAC ticket of $600, that's $11,400 in additional annual revenue. From one-tenth of one second of speed improvement.

This is where the local business case for Core Web Vitals becomes financially unambiguous. Speed fixes produce two outcomes simultaneously -- higher Map Pack position (winning more tiebreaks against comparable competitors) and higher conversion rate on the traffic you already have. You're not choosing between ranking and conversion. You're improving both with the same set of optimizations. That's vanishingly rare in SEO. Most optimizations are tradeoffs. This one isn't.

The March 2026 update tied CWV tighter to GBP rankings

The March 2026 update changed the ground rules for local ranking in ways that directly reward the businesses that invest in site performance. Review recency now carries more algorithmic weight than total review count. A business with 40 reviews accrued over the past twelve months will outrank a competitor with 200 reviews that stopped receiving new ones two years ago. Hyper-local content -- pages about specific neighborhoods, service-area content that names Cleveland County communities explicitly -- now outperforms generic national content. And the speed of the landing page Google pulls from your GBP link now factors directly into the local pack ranking calculation.⁵ Three changes. All of them pointing in the same direction: site quality matters more today than it did yesterday, and it'll matter more tomorrow than it does today.

Your Google Business Profile links to your website. Google evaluates that website's Core Web Vitals. If your LCP is 9.5 seconds and your competitor's is 2.2 seconds, the March 2026 update widened the ranking gap between you. What was a tiebreaker is now approaching a persistent ranking disadvantage. Sites with consistently poor Core Web Vitals are beginning to accumulate a structural penalty -- not a direct algorithmic demotion, but a growing gap between them and the competitors who pass. The difference between position one and position four in the local pack isn't subtle. Position one captures roughly 32% of clicks. Position four captures under 8%. That gap represents a substantial percentage of Cleveland County customers finding your competitor instead of you.

I ran an audit last month for a pest control company in Boiling Springs. Their GBP was excellent -- fully optimized categories, strong review velocity, four service-area cities listed. Their website loaded in 11.2 seconds on mobile. Their LCP was a 4.7MB uncompressed hero image. Their INP failed because of an unoptimized chat widget. Their CLS was borderline. They were losing the Map Pack tiebreak to two competitors with weaker profiles but faster sites. The fix was mechanical: compress and resize the hero image to 200KB, lazy-load the chat widget, add explicit dimensions to all images, enable text compression on the server. PageSpeed Insights went from a mobile score of 23 to 81. LCP dropped from 11.2 seconds to 2.8 seconds. Three weeks later, they moved from position four to position two in the local pack. Same GBP. Same reviews. Same backlinks. The only variable that changed was site speed. The tiebreaker flipped in their favor. That's not luck. That's physics.

The practical next step is running PageSpeed Insights on your own site right now. Go to pagespeed.web.dev, enter your URL, and look at the Core Web Vitals Assessment section at the top. If it says "Failed" in red, you know exactly what to fix. LCP failures are almost always image-related on small business websites -- compress your hero image, use modern formats like WebP, preload the LCP element. INP failures are almost always JavaScript-related -- audit your third-party scripts, defer non-critical JS, remove abandoned widgets. CLS failures are almost always missing image dimensions or late-loading font swaps -- add width and height attributes to every image, preload your web fonts, reserve space for embedded content. None of these fixes require a developer. They require an afternoon of attention and the willingness to stop losing tiebreakers you didn't know you were in.³