Why speed and Core Web Vitals matter for your business website

A slow website is like a shop with a door that sticks. People give up before they get inside — and you never find out how many. Speed isn't a technical curiosity for developers; it's one of the first things a customer experiences of your business.

What Core Web Vitals actually are

Core Web Vitals are Google's way of measuring how a page feels to a real person. It's not about how pretty the page is, but how it behaves while it loads. There are three measures, and you don't need to memorise them — just understand what they stand for:

• How quickly the main content appears. How long before the most important thing on the page is actually on screen.
• How quickly the page responds. When you tap a button, does something happen at once, or does it hang?
• How stable the page is while loading. Do the text and buttons jump around so you tap the wrong thing, or does everything stay put?

Together they tell you one thing: is this pleasant to use, or irritating?

Why it affects the bottom line

Google's own figures are clear: more than half of mobile visitors leave a site that takes longer than three seconds to load. Many small business sites take six to eight. That means the majority of mobile visitors — who are now the majority of all visitors — leave before they've seen what you offer.

That's not a small loss. It's customers who were interested enough to click, but not patient enough to wait. They don't call to say the site was slow. They just move on to the next result.

It affects where you rank, too

Speed is one of the signals Google uses when deciding who appears at the top. Two businesses with equally good content can land differently on the results page if one loads noticeably faster. So you're not just competing on what you offer, but on how smoothly your site feels.

What makes sites slow

The most common causes are surprisingly dull — and that's exactly why they're easy to fix:

• Large images. A photo saved at full camera resolution can be ten times bigger than it needs to be.
• Too many add-on scripts. Every chatbot, tracking pixel, and widget adds load time.
• Cheap shared hosting. When the server shares resources with a thousand other sites, you feel it.
• Heavy templates. Many ready-made themes load piles of code you never use.

None of these are complicated to solve. They just rarely get solved, because nobody has looked.

How to check your own site

You don't need a developer's tool. Do this now:

1. Open the site on your phone with Wi-Fi switched off, so you're on mobile data.
2. Count the seconds from the tap until the page is actually ready.
3. Tap a button or menu — does it respond at once?

For a more precise reading, run your address through a free tool such as Lighthouse or PageSpeed Insights. Below 50 on mobile is a problem. Below 70 means you're losing work. Above 90 is a reasonable standard to aim for.

Speed is rarely a big job

The good thing about speed is that it can usually be fixed without rebuilding everything. Compressed images, fewer unnecessary scripts, and better hosting often get you most of the way. On an existing site this is frequently the simplest improvement with the biggest effect — you're simply removing the brakes that stood between the customer and the contact form.

A fast site isn't a goal in itself. It's just the shortest path from someone clicking to someone getting in touch.