Website speed and Core Web Vitals: why speed sells

Website speed affects sales because every moment of waiting is another chance for a visitor to tap back and choose a competitor. Core Web Vitals are the three measurements Google uses to describe that experience: how quickly the main content appears, how quickly the page responds to a tap, and how stable it stays while loading.

The good news is that slow small business sites tend to suffer from the same handful of problems, and most of them can be fixed without rebuilding anything. You do not need to read code to know what to check.

Why does website speed affect sales?

Because a slow site loses people before they have seen your offer. Someone browsing on a phone, on a train or between meetings will not wait patiently. They go back to the results and pick the next business.

The effect shows up in several places:

• First impressions: a site that loads slowly and jumps around feels less trustworthy, even when the service is excellent
• Forms and checkout: every delay at the moment of enquiry or payment is another reason to give up
• Paid ads: you pay for each click, and a visitor who leaves before the page loads is budget gone. Google Ads also considers landing page experience when it evaluates your ads
• Organic search: page experience, including Core Web Vitals, is one of the signals Google uses. It will not outrank better content on its own, but it is part of the picture

To be honest about it: speed alone will not bring customers to a site that does not answer their question. But it can certainly drive customers away from one that does. That is why speed is one part of conversion rate optimisation, not a substitute for it.

What are Core Web Vitals?

Core Web Vitals are three metrics Google defined to describe real browsing experience, based on data from actual Chrome users. Each one measures something visitors feel, even if they would never call it by name.

LCP: how fast the main content appears

Largest Contentful Paint measures when the biggest element near the top of the page, usually the hero image or the headline, shows up. Google’s guidance treats 2.5 seconds or less as good.

INP: how fast the page responds

Interaction to Next Paint measures the delay between a tap, click or keypress and the page visibly reacting. Good is 200 milliseconds or less. A page that looks ready but ignores taps is especially frustrating.

CLS: how much the page jumps

Cumulative Layout Shift measures unexpected movement while the page loads. You are about to tap a button, a banner loads, and the button slides away. Good is 0.1 or less.

How do you test your website speed?

Use a few free tools that complement each other, and always start with mobile:

1. PageSpeed Insights: enter a page address to see real user data (when the page has enough traffic) and a lab test with recommendations. Look at the mobile results first.
2. Search Console: the Core Web Vitals report groups your pages into good, needs improvement and poor.
3. A real phone: open your site on your own phone over mobile data. Notice when you can actually read and tap, not just when something appears.
4. The pages that matter, not only the homepage: a service page, a product page, a campaign landing page and the contact page.
5. Retest after every change: a new plugin, a new hero image or a new widget can undo earlier work.

Lab data or field data: which should you trust?

Both, for different jobs. Lab data is a single simulated test on one device and connection. Field data is what actually happened to your visitors over time, on their own phones and networks, and it is what Google relies on when it assesses page experience.

So a lab test may show a weak score while real visitors have a reasonable experience, or the other way round. Use the lab test to find what to fix, and field data to confirm the fix worked. A new or low traffic site may not have field data yet; then the lab test and your own phone are what you have.

What slows down most small business websites?

Usually the same suspects:

• Oversized images: photos uploaded straight from a camera, many times larger than they are displayed
• Too many plugins and scripts: sliders, social feeds, several ad pixels and chat widgets, each one adding weight
• Weak hosting: a server that responds slowly before the page even starts loading
• No caching: every visit rebuilds the page instead of serving a ready copy
• Lots of fonts: several font families, each in several weights
• Background video: impressive on a desktop, heavy on a phone
• Late banners: pop-ups and top bars that load late and push the content down

Important tools such as cookie banners, accessibility tools and chat should still load in a way that does not block the page or shift it.

How do you improve website speed?

Start with what gives the most for the least effort, on the pages that bring the most enquiries. This is the order we recommend:

Compress and resize images

Upload images at the size they are actually shown, in modern formats such as WebP or AVIF, and lazy load images further down the page. On many sites, this single change makes the biggest difference.

Remove plugins and scripts you do not need

Go through every plugin and third party script and ask: does anyone still use this? A pixel from a finished campaign, a slider nobody scrolls, a tool you replaced long ago. Load whatever remains as late as you can.

Add caching and a CDN

Caching serves each visitor a ready made page instead of building it again. A content delivery network serves your files from a location closer to the visitor.

Upgrade hosting when needed

If the server itself is slow to respond, no other optimisation will fully make up for it.

Reserve space for every element

Set dimensions for images, videos and banners so the layout does not jump as they load. That is exactly what improves CLS.

Example: a neighbourhood restaurant

A family restaurant has a beautiful website: a full screen video of the kitchen at the top, a menu uploaded as a large PDF, an Instagram feed, a booking widget and two ad pixels. On the office computer it looks great.

On a phone over mobile data, the story is different. The video takes a while before anything useful appears, the booking button jumps as the feed loads, and the menu opens as a file that has to be downloaded and zoomed. The fixes are simple: a still photo replaces the video on mobile, the menu becomes a normal web page, the Instagram feed goes, and the booking widget gets a fixed space. The site still looks like the restaurant, and on a phone it now feels quick from the first tap.

A website speed checklist

• Key pages tested in PageSpeed Insights, mobile first
• The Core Web Vitals report in Search Console reviewed
• Every image compressed and sized for how it is displayed
• No plugins or scripts that nobody needs
• Caching switched on
• Space reserved for images and banners, so nothing jumps
• Campaign landing pages tested separately
• Someone retests after every significant change

Speed is part of the design

Website speed is not a technical detail for developers only. It decides whether a visitor ever gets to see what you offer. At Kaede Digital we build small business websites with speed planned in from the start: modern image formats, caching, a minimum of plugins and testing on real phones, because that is where your customers meet you. To see what else a site needs to bring in enquiries, read 9 things every lead generating website needs, and if you run campaigns, our guide to landing pages that convert.

FAQ

What PageSpeed Insights score should I aim for?

You do not need to chase 100. It matters more that your Core Web Vitals from real users are in the good range and that pages feel fast on a phone. The lab score helps you find problems; it is not the goal itself.

Does website speed affect Google rankings?

Yes, page experience is one of the signals Google uses, but it does not replace relevant, useful content. In practice, speed has its biggest effect on visitors themselves: how many stay, read and get in touch.

Is WordPress slower than Wix or Shopify?

Not necessarily. Any platform can be fast or slow, and it depends mostly on how the site is built: the theme, plugins, images and hosting. A well built WordPress site can be very fast, and a site on a hosted platform can be heavy.

How long does it take to see speed improvements?

Lab tests show improvements as soon as a fix goes live. Field data in Search Console is based on recent weeks of real visits, so improvements appear there gradually.