Website Speed and Core Web Vitals: What a Slow Website Costs a Small Business

What are Core Web Vitals?

Core Web Vitals are the metrics Google uses to describe how a page feels to a real visitor. There are three, and Google assesses each at the 75th percentile of real visits, split by mobile and desktop:

• Largest Contentful Paint (LCP): how long until the main content appears. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much the page jumps around while loading. Good is 0.1 or less.

Interest in the topic is steady, with around 2,400 US searches a month for "core web vitals" (DataForSEO, 2026-10).

Do Core Web Vitals affect SEO and rankings?

Yes, as part of Google's page experience signals, though relevance and content quality still count for more. The bigger effect is often indirect. A page that takes six seconds to show on a phone loses people before they read a word, and every lost visitor is a lost call or form fill. Speed is one of the few SEO improvements that helps rankings and revenue at the same time. It also helps AI crawlers, which are less patient with bloated pages, as we explain in our AEO guide.

How slow is too slow for a small business website?

In audits we ran this year on local service-business websites, we measured mobile LCP between roughly 6.7 and 16 seconds on some homepages, with page weights from 9 to 17 megabytes. That is two to six times over the 2.5-second target. These were established companies with strong reviews, quietly losing mobile visitors to a heavy page.

You can check your own site free with PageSpeed Insights. Look at the mobile tab and at the real-user "Core Web Vitals assessment" if it appears, not only the lab score.

What makes small business websites slow?

• Oversized images. Uncompressed photos straight from a phone or camera are the number one culprit. Modern formats like WebP cut file size dramatically.
• Plugin and script bloat. Page builders, sliders, chat widgets, tracking pixels and fonts each add requests and code.
• Cheap shared hosting with slow server response.
• No caching or CDN, so every visitor waits on a distant server.
• Render-blocking code that holds up the first paint.
• Layout shifts from images without dimensions and late-loading ads or banners.

How do I speed up my website?

1. Compress and resize every image, convert to WebP, set width and height, and lazy-load anything below the fold. Always write descriptive alt text while you are at it.
2. Remove what you do not use: old plugins, duplicate analytics tags, unused fonts and sliders.
3. Preload the hero image and your main font so the largest element paints early.
4. Use a CDN and decent hosting, and turn on caching and compression.
5. Reserve space for images and embeds to stop layout shift.
6. Re-test on a real phone over mobile data, not just on office Wi-Fi.

Our web development and web design work bakes these in from the start, and ongoing technical SEO keeps them from slipping.

Why are static sites so fast?

A static site skips the slowest part of a typical page load: building the page on the server for every visitor. The pages are already built, so a CDN can hand them over almost instantly from a location near the visitor. Frameworks like Astro also ship minimal JavaScript by default. It is the same design choice that makes static sites safer, which we cover in Why Static Astro Sites Beat WordPress. Speed also supports the local-pack and mobile-search goals in our local SEO checklist.

What should I do first?

Run PageSpeed Insights on your homepage and your top service page, mobile tab. If either fails LCP, start with images and hosting. If you would rather have someone handle it, send us your URL and we will tell you what is slowing you down and what it would take to fix.

Frequently asked questions