Back to journal
Performance4 min read

Why your website is slow and why it matters

By · Published · Updated

Laptop showing a slow loading website
Performance

More than half of mobile visitors leave a site that takes over three seconds to load. Here are the usual causes of slow small business sites and their fixes.

Why speed affects your enquiries

Google research found that 53% of mobile visitors abandon a site that takes longer than three seconds to load. Three seconds is less time than it takes to read this sentence. If your website is slow, you lose more than half of your mobile visitors before they see a single word about your business. Page speed also feeds into how search engines assess your site, so a slow site can hurt your visibility as well as your conversions.

For a trade business, this matters more than it does for most. People searching for an electrician or a plumber are often on their phone, often in a hurry, and often have a problem that needs fixing today. If the page takes too long to appear, they tap the next business in the results and call that one instead.

Four reasons small business sites are slow

Most small business websites load in five to eight seconds. They are slow for four main reasons, and all four can be fixed. The causes are not mysterious. They come from the hosting, the images, the scripts and the caching settings, and each one has a practical fix.

I go through each cause in the sections that follow, in the order I would check them on a site we were asked to review. Knowing the cause is the first step, because a site that is slow for one reason is usually slow for other reasons as well.

Cheap hosting and the distance problem

The first cause is cheap hosting. Most small business sites run on shared hosting that costs around $5 a month. The server sits in one location, shares its resources with hundreds of other sites, and usually has no content delivery network to help it.

Distance matters more than people expect. When someone in Perth visits a site hosted in Sydney, every image and script has to travel across the country. A CDN solves this by serving your files from the data centre closest to each visitor. Every Kerb site is on a global CDN by default, so the distance problem is handled before a visitor ever arrives.

If you are not sure where your site is hosted, ask your provider. It is a simple question, and the answer tells you a lot about whether the site was set up to perform.

Images that are far too large

A photo straight off a modern phone can be around 4 megabytes. A web page should serve that same image at about 150 kilobytes. Most DIY builders do not compress images automatically, and most site owners do not know that they need to do it themselves.

We compress every image and serve it in modern formats such as WebP and AVIF, at the size each screen actually needs. A visitor on a phone should not download the same file as a visitor on a large desktop monitor. If you upload your own photos, resize them before you upload them, and check the file size before you publish.

Scripts that hold up the page

WordPress sites are known for this problem. Each plugin adds its own JavaScript and CSS, and the browser has to download and read all of it before it can show the page. A typical WordPress site loads 20 to 30 scripts. A Kerb site loads one.

We build with static HTML and CSS, and we defer anything that is not needed for the first view. The practical lesson for your own site is to count the plugins and widgets you have installed. Each chat box, booking widget, social feed and tracking tag adds weight, and many of them are not earning their place. Test the site on a phone over mobile data, too, because a page that feels quick on an office desktop can be slow for a customer on the move.

Missing caching on repeat visits

When a browser loads your site, it should store the static files so it does not have to download them again on the next visit. Many small business sites send settings that stop this from happening, so every page load becomes a full reload from start to finish.

We set caching rules so that repeat visits are quick. You can check whether a site is caching properly by running it through PageSpeed Insights, or by asking your developer to look at the cache headers. If your site feels slow on repeat visits, this is worth checking first.

Why speed is an ongoing job

The fixes for all four causes are not complicated, but they need technical knowledge and regular attention. A site can slow down after a new plugin, a heavy photo gallery or a change of hosting plan, and most business owners will not notice until a customer mentions it, if they ever do.

That is what the subscription covers. We build the site to be fast, keep it fast and monitor it. If the site slows down, we know before you do and we fix it. That is a far better arrangement than finding out about a slow site from a missed enquiry. Check the speed again after any change, even a small one, because a single new widget can add seconds back to the load time.

If your current site takes more than three seconds to load, check it with Google PageSpeed Insights. Run the test on the mobile tab, since that is where most of the drop-off happens. If the score is poor, the fix is simpler than it looks, and it may cost less than what you are paying now for hosting that does not perform.