Website Speed: Why Core Web Vitals Cost You Customers

Core Web Vitals are Google's three measures of real-world page experience: loading speed (LCP), responsiveness (INP), and visual stability (CLS). When your pages miss the targets of 2.5 seconds, 200 milliseconds, and 0.1, visitors leave before they read a word or click a button. A slow site is not a technical footnote. It is lost revenue.

How much revenue? Google and SOASTA studied real mobile sites and found the probability that a visitor bounces climbs 32 percent as page load time goes from one second to three seconds (Google/SOASTA Research, 2017). For a Minneapolis business paying for ads or ranking hard for local search, a slow page quietly wastes the traffic you already earned.

What are Core Web Vitals, in plain English?

Core Web Vitals are three specific numbers Google uses to grade how your website feels to a real person on a real phone. Google reports them from actual visitor data, not a lab simulation, which is why they reflect the experience your customers get on Minneapolis coffee-shop wifi or a spotty cell signal on I-35W.

Each Vital answers a simple question:

• Largest Contentful Paint (LCP) answers "how long until the main content shows up?" This is the big headline, hero image, or main block a visitor is waiting to see.
• Interaction to Next Paint (INP) answers "when I tap or click, how fast does the page respond?" INP became an official Core Web Vital in March 2024, replacing the older First Input Delay metric. It measures the lag between a tap and something visibly happening.
• Cumulative Layout Shift (CLS) answers "does the page jump around while it loads?" You have felt this: you go to tap a button, an ad or image loads late, everything shifts, and you tap the wrong thing.

Together they cover the three ways a site frustrates people: it loads slow, it responds slow, or it moves under their thumb.

What are the Core Web Vitals thresholds I need to hit?

Google groups each Vital into good, needs improvement, or poor. You want every metric in the good column for at least 75 percent of your visitors. Here are the targets.

Metric	What it measures	Good	Needs improvement	Poor
LCP (loading)	Time until main content appears	2.5 seconds or less	2.5 to 4.0 seconds	Over 4.0 seconds
INP (responsiveness)	Delay after a tap or click	200 ms or less	200 to 500 ms	Over 500 ms
CLS (visual stability)	How much the layout shifts	0.1 or less	0.1 to 0.25	Over 0.25

The numbers are not arbitrary. Google set them by studying what real users tolerate before they perceive a page as slow or unstable. Hitting "good" on all three does not guarantee a top ranking, but failing them puts a ceiling on both your search visibility and your conversion rate.

How does a slow website actually cost me customers?

Speed does not cost you customers in an abstract way. It costs you at the exact moment someone was about to become one.

Picture a homeowner in Golden Valley searching "emergency plumber near me" at 9 pm with water on the floor. They tap your result. If your page takes four seconds to show a phone number, they have already hit back and tapped the next plumber. That is the Google/SOASTA finding in action: every extra second raises the odds the visitor is gone.

The damage compounds three ways:

• You lose the visit. A bounced visitor converts at zero, no matter how good your service is.
• You lose the ad spend. If you run Google or Meta ads, you paid for that click whether or not the page loaded fast enough to convert it. Slow pages make every campaign more expensive per customer.
• You lose ranking momentum. Page experience is a ranking signal in Google. Slow pages get shown less, so the problem feeds itself.

A fast site does the opposite. It banks more of the traffic you already worked to earn, which is usually cheaper than buying more traffic to make up for a leaky page.

Why does site speed matter for AI search too?

AI search assistants like ChatGPT, Perplexity, and Google's AI answers pull from pages their crawlers can fetch quickly and parse cleanly. A page that is slow, bloated, or unstable is harder for those systems to render, which makes it a weaker candidate to be quoted. The same clean, fast HTML that wins Core Web Vitals is the HTML that AI engines find easy to cite.

This is why we treat speed as part of visibility, not a separate chore. If you are new to the AI-search side, our plain-English guide to generative engine optimization explains how these engines choose what to recommend.

How do I find out if my site passes Core Web Vitals?

You can check in a few minutes with free tools before you spend a dollar on fixes:

1. PageSpeed Insights (pagespeed.web.dev) gives you lab scores and, if your site has enough traffic, real-world field data for all three Vitals.
2. Google Search Console has a Core Web Vitals report showing how many of your real URLs pass, grouped by mobile and desktop.
3. Chrome DevTools runs an on-demand Lighthouse audit of a single page.

Test on mobile first. Most Minneapolis local traffic is on phones, and phones are where slow sites hurt most because of weaker processors and cell connections.

What usually makes a small business site slow?

In our experience running and rebuilding sites, the biggest culprits are consistent and fixable:

• Oversized images uploaded straight from a camera at full resolution instead of compressed and correctly sized.
• Heavy page builders and plugin stacks that load scripts you never use.
• Third-party embeds like chat widgets, popups, and tracking scripts that each add weight.
• No caching or a slow host, so the server rebuilds the page on every visit.
• Layout shift from ads and late-loading fonts that push content around and wreck CLS.

You do not always need a full rebuild. Sometimes compressing images and cutting two plugins moves you from poor to good. But if your site is built on a heavy platform and every fix fights the tooling, a lean rebuild pays for itself. We break down when speed problems justify one in our piece on redesign cost and ROI, and if you are weighing that step, our Minneapolis website redesign service starts with a speed and structure audit before any design work begins.

Frequently asked questions

Is a good Core Web Vitals score enough to rank number one on Google? No. Speed is one ranking signal among many, alongside relevance, content quality, and local signals like your Google Business Profile. Think of Core Web Vitals as a requirement to compete, not a shortcut to the top. A fast page with weak content still loses, but a slow page with great content leaves rankings and conversions on the table.

How fast should my website load? Aim for your Largest Contentful Paint to happen in 2.5 seconds or less on mobile, measured on real visitor connections. That is the Google "good" threshold. Faster is better, and the first two seconds matter most, since that is where the steepest drop-off in visitor patience happens.

Do Core Web Vitals matter more on mobile or desktop? Mobile, for most local businesses. Google reports the Vitals separately for each, and the majority of "near me" and local service searches happen on phones. Phones also have slower processors and connections, so a site that feels fine on your office desktop can still fail on a customer's phone.

My site is on Squarespace or Wix. Can I still improve Core Web Vitals? Yes, within limits. You can compress images, remove unused widgets, and simplify your layout, and that often moves the needle. Hosted builders control much of the underlying code, though, so there is a floor you cannot get past. If you keep hitting it, a custom build gives you full control over speed.

Slow pages quietly drain the traffic you already paid for. If you want to know where your site actually stands with real customers and AI engines, check your AI visibility and we will show you what is costing you clicks.