Skip to content
digitalaudits.com.au

Why is my website slow?

By · 5 min read · Published · Updated

Why is my website slow?

A homepage with a full-width photo straight off a phone, a gallery of twelve more, a chat widget and an embedded Google Map can easily weigh 10 MB. On a phone with patchy reception, that’s a long wait before the phone number appears, and most people give up after about three seconds.

The frustrating part is you’ll never know. People who leave a slow site tap back and call the next business in the results, so your enquiries drop without anything obviously breaking.

Most small business websites are slow for the same handful of reasons, and most of them are fixable without a new website. Find out which one is yours and fix it first, and you’ll usually get most of the speed back in an afternoon.

Big images are the usual suspect

Start here, because it’s the cause on most slow sites. Photos straight off a phone or camera are often 3 to 6 MB each and 4000 pixels wide, while your website might show them at 1200. Unless someone resized them, every visitor downloads the full file.

Resize each image to the largest size it’s shown at. A full-width banner rarely needs to be wider than 1600 to 2000 pixels. Then compress it, ideally into WebP, a modern image format that’s often around 30% smaller than JPEG at the same quality. Images further down the page can be lazy-loaded, meaning they only download when someone scrolls to them, and most website builders now do that for you.

Those changes alone often halve a page’s load time. Our guide to image optimisation for non-designers walks through them without any special software.

Too many plugins and scripts

Every chat widget, booking tool, tracking tag, slider, social feed and pop-up adds code the browser has to download and run before your page settles. Each one might add only a little, but together they add up, and some stop the page showing anything until they’ve finished loading.

WordPress sites collect these easily, because plugins take seconds to install and are easy to forget. Shopify stores collect them too, since apps you uninstalled months ago sometimes leave their code behind in your theme.

Go through what’s installed and ask of each one whether you still use it. Remove anything you don’t, and look for duplicates, such as two analytics tools or a plugin doing a job your theme already does. Then ask your web person to defer the scripts that remain, so they load after your main content.

Slow hosting

Before a page can load, your server has to answer. Cheap shared hosting can take a second or more just to respond, and that delay happens on every page. In your report it shows up as Server response, measured as Time to First Byte.

If your server answers in under about 0.8 seconds, your hosting is fine and the problem is elsewhere. If it’s slower, turn on caching first. Most hosts and WordPress caching plugins can serve a ready-made copy of each page, which skips the work of building it from scratch for every visitor. A content delivery network, or CDN, helps too, by keeping copies of your site on servers closer to your visitors, and many hosts include one free. If neither fixes it, better hosting usually costs a little more a month and pays for itself.

Heavy themes and things that load from elsewhere

Some themes and drag-and-drop page builders load a lot of code on every page, whether you use those features or not. Sliders and background videos look good in a demo and drag on a phone. A web developer can often trim a theme back, but if the theme itself is the problem, moving to a lighter one is one of the few times a rebuild makes sense.

Anything embedded from another company’s servers adds weight as well. Custom fonts, maps, YouTube videos and social media feeds each need their own connection, and an embedded Google Map or video on the homepage can add seconds on its own. Swapping a live map for an image that links to Google Maps, or showing a video thumbnail that only loads the player when clicked, keeps the look without the wait.

How to tell which problem you have

You don’t need to guess. A website speed test shows where the time goes. Ours loads your page from Sydney on a fast connection, once as a phone and once as a desktop computer, and lists the fixes in order of how much time each would save.

Read the results in a particular order. If the server response is slow, sort out hosting and caching first, because everything else waits on it. If the server is quick but the page is still slow, look at images and then scripts. A page that’s slow even on our fast connection from Sydney is too heavy for anyone on a phone, whatever their signal.

Fix one thing at a time and test again after each change, so you know what helped. If Google’s PageSpeed Insights has told you your site failed its Core Web Vitals assessment, our guide to Core Web Vitals in plain English explains what that means and which fix to start with. And if the fixes involve your hosting or theme, your report makes a clear brief for a web developer, or you can request quotes from top-rated providers straight from it.

Every second a page takes to load costs you visitors you’ll never hear from, and the usual causes are ordinary and fixable.

Start with the images.

Want the full picture? See what our free speed audit checks

Common questions

What counts as a fast website?

On a phone, aim for your main content to appear within about 2.5 seconds. Under 4 seconds is okay. Anything slower is losing you visitors.

Will better hosting fix it?

Only if your server is slow to respond. If your report says your server response is quick, the problem is the page itself, usually big images or too many scripts, and new hosting won't help much.

Does speed affect Google rankings?

Yes, a little. Google uses page experience, including speed, as one of many ranking signals. The bigger effect is on visitors, who leave slow pages before they see what you offer.

How do I check my speed?

Run a free website speed test. We load your page from Sydney on a phone and a desktop computer, explain the results in plain English and list the fixes in order.

Run a speed audit

See your real results and the fixes that matter most.