Skip to content

Web · · 5 min read

Website Speed and SEO: Why a Slow Site Costs You Customers

How Core Web Vitals work in 2026, what Google says about speed and rankings, and a practical plan to make a slow small-business site fast.

Updated:

Illustration of a speed gauge at 99 next to a page that has finished loading

Key takeaways

  • Google says Core Web Vitals are used by its ranking systems, but a fast page doesn’t beat a more relevant one.
  • The targets are simple: main content in 2.5 seconds or less, responses to taps in 200 ms or less, and a layout that doesn’t jump around.
  • The median mobile home page now weighs about 2.5 MB, and images are the largest part of it.
  • Most speed problems come from a few fixable causes: heavy images, too much JavaScript, slow hosting and late-loading main images.

Your website might be losing customers before they see what you offer. A slow page frustrates people on phones, and it gives Google a reason to prefer a competitor when two pages are equally useful. The good news: speed is one of the few parts of SEO you can measure precisely and fix directly.

What Google actually measures: Core Web Vitals

Google measures real-world experience with three metrics called Core Web Vitals. In plain English:

  • Loading (LCP, Largest Contentful Paint) — how quickly the main content appears. Good is 2.5 seconds or less.
  • Responsiveness (INP, Interaction to Next Paint) — how fast the page reacts when someone taps, clicks or types. Good is 200 milliseconds or less. INP replaced the older FID metric as a Core Web Vital in 2024.
  • Visual stability (CLS, Cumulative Layout Shift) — whether the layout jumps while loading, like a button moving just as you tap it. Good is 0.1 or less.

Google judges these at the 75th percentile of real page loads, split by mobile and desktop. In practice, that means three out of four visits need to meet the target, not just your visit on fast office Wi-Fi.

Does speed really affect rankings?

Yes, but with an important limit. Google’s page experience documentation, updated in September 2026, states that Core Web Vitals are used by its ranking systems. The same page is clear that good scores don’t guarantee top rankings, and that Google will still show the most relevant content even when its page experience is weak.

So speed is not a shortcut past good content. It’s a tiebreaker and a multiplier: when your page is as helpful as a competitor’s, a faster experience helps you win the click and keep the visitor.

Why speed drives revenue, not just rankings

The bigger cost of a slow site is lost customers after they arrive. In a test published by Google’s web.dev team, Vodafone improved LCP by 31% on a landing page and saw 8% more sales, a 15% better lead-to-visit rate and an 11% better cart-to-visit rate compared with the slower version.

Your numbers will be different, but the logic holds for any small business: every extra second on a phone is another chance for the visitor to give up and tap the next result.

Fast is not a luxury. For a local business competing on a phone screen, it’s the price of admission.

Common culprits behind a slow site

The HTTP Archive’s 2025 Web Almanac puts the median mobile home page at about 2,559 KB. Images are the largest share (about 911 KB), followed by JavaScript (about 632 KB) and fonts (about 122 KB). Small-business sites often exceed those numbers because of:

  • Huge, uncompressed photos uploaded straight from a phone or camera
  • Page builders, heavy themes and plugins that load scripts on every page
  • Chat widgets, trackers and pop-ups that all compete for the same connection
  • No caching or content delivery network (CDN), so every visit starts from scratch
  • Cheap or overloaded hosting that slows the first response from the server
  • A main hero image that is lazy-loaded or injected by JavaScript, so it’s discovered late

How to fix it

Most speed problems are fixable without starting over. Google’s guide to optimizing LCP recommends a few concrete steps:

  1. Make the main image easy to find. Put it in the page’s HTML as a normal image, not only in CSS or JavaScript, and mark it with fetchpriority="high".
  2. Never lazy-load the main image. Lazy loading is great for photos further down the page, but on the LCP image it adds delay.
  3. Speed up the server response. Use a CDN, avoid unnecessary redirects, and cache pages wherever possible.
  4. Shrink what you send. Serve modern image formats at the size they’re displayed, and remove scripts and plugins you don’t need.

For older sites, a web modernization rebuild on a modern stack often delivers the biggest leap, because it removes the weight at the source instead of patching it.

What this looks like in real projects

Two examples from our own work, measured with the same tools you can use:

  • QuivalTech: in our October 2, 2026 audit, we cut the mobile homepage weight from 3.9 MB to 0.88 MB. See the project.
  • Macro Meals (prototype in development): in a lab test on October 1, 2026, the new version scored 97 in mobile Lighthouse Performance versus 32 on the current site, and showed its main content in 1.6 seconds versus 18.1 seconds. See the project.

A quick self-check

Run your homepage through Google’s PageSpeed Insights and read it in two parts:

  • Field data (top section): real visits from Chrome users over the previous 28 days. This is what reflects your Core Web Vitals. Small sites may not have enough traffic to show it.
  • Lab data (Lighthouse score): a single simulated load on a mid-range phone with a throttled connection. It’s best for finding what to fix. Scores of 90–100 are good, 50–89 need improvement and 0–49 are poor.

If your mobile LCP is above 2.5 seconds, or your mobile Lighthouse score is in the red, speed is likely costing you visitors — and it’s one of the highest-return things you can fix.


Speed touches rankings, user experience and revenue. Treat it as a business metric, not a technical afterthought. If you’d like us to check your site, send a WhatsApp or text to (805) 750-3255 or use our contact form.

Sources

Facts are based on the sources above as of the update date.

Want to talk about your project?

Websites from $250 · Proposal + 7 days free · Reply within 24 hours