A slow website doesn't announce itself. Nobody emails you to say "your homepage took nine seconds to load, so I went to your competitor instead." They just leave, and you never know they were there. Most of the time the cause isn't one dramatic problem — it's a handful of small, easy-to-miss mistakes stacked on top of each other. Here are the ones we see most often on Australian small business websites, and exactly how to fix each one.
Uploading Photos Straight From Your Phone or Camera
This is the single biggest speed killer we see, and it's completely avoidable. A photo straight off a modern phone or DSLR can be 5–15MB. Put six of those in a homepage slideshow and you've built a page that has to download tens of megabytes before a visitor sees anything useful.
We once looked at a Hobart bakery's website where the homepage slideshow alone was over 15MB — beautiful photos of sourdough and pastries, all uncompressed, straight off an iPhone. On a good home internet connection that's slow. On a phone at the football or in a patchy regional mobile signal, it can take the better part of a minute, if it loads at all.
The fix:
- Resize images to the actual dimensions they display at (a banner doesn't need to be 4000px wide).
- Compress every image before uploading — modern formats like WebP or AVIF cut file size dramatically with barely any visible quality loss.
- Use a plugin or hosting feature that auto-optimises images on upload so you can't forget.
- Never upload a slideshow of full-resolution photos "because they looked nice on my phone."
Stacking Up Plugins and Third-Party Widgets
Every plugin, chat widget, booking tool, review badge and tracking pixel you add usually pulls in its own JavaScript file, its own stylesheet, and often its own call to an external server. Add enough of them and your site is having a dozen conversations with other companies' servers before it can even show your own content.
A Sunshine Coast physio clinic we reviewed had six different booking and chat tools all loading on every page — two live chat widgets from an old redesign nobody removed, a review pop-up, a Facebook pixel, a separate booking calendar, and a marketing automation script. Each one added its own delay, and together they made the site feel sluggish even though the actual page content was light.
The fix:
- Audit your plugins and embeds every six months. If you can't remember why something is there, it's a candidate for removal.
- Keep one chat tool, one booking tool, one review tool — not two of each from different eras of the website.
- Load non-essential scripts (chat widgets, review pop-ups) after the main page content, not before it.
- For WordPress sites specifically, our guide on how to speed up a WordPress website covers plugin auditing in more depth.
Choosing Cheap, Oversold Hosting
Hosting is one area where the cheapest option almost always costs you more in the long run. Budget shared hosting packs hundreds of websites onto the same server, all fighting over the same limited memory and processing power. Your site might load fine at 7am and crawl at 7pm when everyone else's traffic peaks too.
A Ballarat cafe on a $4-a-month hosting plan might look like a bargain until you realise the server also hosts hundreds of other small sites, none of which get priority when things get busy — like on a Saturday morning when locals are checking opening hours over breakfast.
The fix:
- Move to hosting built for the platform you use, with dedicated resources rather than oversold shared plans.
- Use a content delivery network so images and static files are served from a location close to the visitor rather than one server far away — our explainer on how a CDN works covers this simply.
- Ask your host directly how many sites share your server resources. A vague answer is a red flag.
Skipping Caching Altogether
Without caching, your server rebuilds every single page from scratch for every single visitor — running database queries and assembling the page fresh each time, even if a hundred people looked at the exact same page five minutes earlier. That's an enormous amount of unnecessary work.
The fix:
- Turn on page caching so a ready-made version of each page is served instantly instead of rebuilt each time.
- Use browser caching so returning visitors don't re-download your logo, fonts and stylesheets on every visit.
- If you're not sure what caching actually does or which type you need, our guide on caching explained breaks it down without the jargon.
Building for Desktop and Forgetting Mobile
Most visitors to an Australian small business website are on their phone — checking a tradie's number from the job site, booking a haircut on the bus, looking up a cafe's menu while deciding where to eat. If your site was designed and tested only on a desktop monitor, you're optimising for the minority of your traffic.
Common mobile mistakes include tiny tap targets, pop-ups that cover the whole screen with no obvious close button, and pages that load full desktop-sized images and font files onto a phone that didn't need them.
The fix:
- Test on an actual phone, on actual mobile data, not just a resized browser window on your laptop.
- Serve smaller images to mobile screens rather than shrinking a desktop-sized image with CSS.
- Read our mobile speed optimisation guide for a proper walkthrough of what to check.
Using Bloated Page Builder Themes
Drag-and-drop page builders and heavy "do everything" themes are popular because they're flexible — but that flexibility comes at a cost. Many ship with CSS and JavaScript for dozens of features you'll never use: sliders, mega menus, animation libraries, portfolio grids. All of that code loads on every page regardless of whether you use it.
The fix:
- Choose a lightweight theme built for speed rather than one built to do everything.
- Remove unused page builder modules and demo content rather than just hiding them.
- Periodically check for unused CSS and JavaScript using Lighthouse, which flags exactly what's loading but never being used on the page.
Autoplaying Video Headers and Background Video
A full-width autoplaying video across your homepage looks impressive in a design mock-up. In practice, video is one of the heaviest assets you can put on a page, and autoplay forces every visitor to download it whether they want to see it or not — including visitors on mobile data who are paying for every megabyte.
The fix:
- Replace autoplaying background video with a well-optimised image where possible.
- If video is essential, compress it heavily, keep it short, and don't autoplay it — let the visitor choose to press play.
- Host video through a proper video platform rather than uploading a raw file directly to your server.
Loading Too Many Web Fonts and Font Weights
Custom fonts make a site feel polished, but each font file has to be downloaded before the browser can display text in it. Sites that load four different typefaces, each in five weights (light, regular, medium, bold, black), are asking visitors to download dozens of font files just to read a paragraph.
The fix:
- Stick to one or two font families per site.
- Only load the specific weights you actually use in your design.
- Use modern font-loading techniques so text appears immediately in a fallback font rather than staying invisible while the custom font downloads.
Not Compressing or Minifying Assets
Every CSS and JavaScript file on your site is written by developers with spacing, comments and readable formatting — great for humans, unnecessary for browsers. Minification strips that out. Compression shrinks the files further for transfer. Skipping both means visitors download noticeably larger files than they need to, on every single page load.
The fix:
- Enable Gzip or Brotli compression on your server.
- Minify CSS and JavaScript, either through your hosting platform, a caching plugin, or your build process.
- Combine or defer scripts where sensible so the browser isn't juggling dozens of small requests.
Treating Your Website as "Set and Forget" After Launch
This is the mistake that lets all the others creep back in. A website that launches fast doesn't stay fast automatically. Every new plugin, every fresh batch of product photos, every marketing script added over the following two years chips away at performance — quietly, a little at a time, until one day the site just feels slow and nobody's sure why.
The fix:
- Check your site's performance every few months, not just at launch.
- Google PageSpeed Insights and Lighthouse are both free and give you a clear, specific list of what's slowing your site down right now — not vague advice, but named files and named problems.
- Treat speed as ongoing maintenance, the same way you'd treat cleaning shopfront windows or servicing a work vehicle.
- For a full walkthrough, our website speed audit checklist is a good starting point, and how to achieve a 90+ PageSpeed score covers the next steps once you know what's wrong.
Mistake, Fix and Impact at a Glance
| Mistake | Quick Fix | Typical Impact |
|---|---|---|
| Huge unoptimised photos | Resize and compress before upload | Often the single biggest speed gain available |
| Too many plugins/widgets | Audit every 6 months, remove duplicates | Fewer scripts, fewer server calls |
| Cheap oversold hosting | Move to hosting built for your platform | More consistent speed at peak times |
| No caching | Enable page and browser caching | Faster repeat visits, less server load |
| Ignoring mobile | Test on real phones, serve smaller assets | Better experience for the majority of visitors |
| Bloated page builder theme | Switch to a lightweight, purpose-built theme | Less unused code on every page |
| Autoplay background video | Replace with image or user-triggered video | Big reduction in data downloaded |
| Too many web fonts | Limit to 1–2 families, only needed weights | Fewer font files to download |
| Uncompressed assets | Enable Gzip/Brotli, minify CSS and JS | Smaller file sizes across the board |
| No ongoing testing | Check PageSpeed Insights and Lighthouse regularly | Catches new problems before they compound |
Key Takeaways
- Most speed problems are small mistakes stacked together, not one big issue.
- Oversized images and unnecessary plugins or widgets are the two most common culprits.
- Cheap hosting and missing caching quietly cap how fast your site can ever be.
- Mobile visitors deserve the same speed attention as desktop, if not more.
- Google PageSpeed Insights and Lighthouse will name your specific problems for free.
- Speed isn't a launch-day task — it needs a regular check-in.
Frequently Asked Questions
What's the single most common website speed mistake?
Uploading large, uncompressed images straight from a phone or camera. It's the mistake we see most often, and usually the one with the biggest and easiest speed win once it's fixed.
How do I know if my website has these mistakes?
Run your site through Google PageSpeed Insights or Lighthouse. Both are free and list specific problems — oversized images, unused CSS, render-blocking scripts — rather than just giving you a vague score. Our Core Web Vitals guide explains what the results actually mean.
Do I really need to remove old plugins I'm not using anymore?
Yes. Inactive-looking widgets and plugins often still load scripts on every page even if you never look at them. If you can't explain why a plugin is installed, it's worth testing your site with it disabled.
Is expensive hosting always faster than cheap hosting?
Not always, but oversold shared hosting is almost always slower under real-world load. The key question isn't price alone — it's how many other sites share your server's resources and whether that hosting is built for your specific platform.
How fast should my website actually load?
There's genuine nuance here rather than one magic number — read how fast a website should load for a proper breakdown, but as a rule of thumb, the main content should appear within a couple of seconds on mobile.
Can autoplaying video really slow a site down that much?
Yes. Video is one of the heaviest file types on the web, and autoplay forces every visitor to download it immediately, whether they watch it or not. A static, well-optimised image usually delivers most of the visual impact for a fraction of the cost.
How often should I test my website's speed?
At minimum, every few months, and after any significant change — a new plugin, a redesign, a new booking widget. Sites drift slower over time as small additions pile up, so regular checks catch problems early. Our best website speed testing tools guide covers which tools suit different needs.
Will fixing these mistakes actually bring in more enquiries?
A faster site keeps more visitors on the page long enough to read your offer, fill in a form or pick up the phone. Speed alone won't fix a weak offer or confusing layout, but a slow site will actively work against everything else you're doing.
Get a Website That's Built to Stay Fast
Fixing these mistakes one at a time helps, but they tend to creep back in without someone keeping an eye on things. If you'd rather have a website that's built properly from the ground up — optimised images, sensible hosting, clean code and no plugin clutter — and kept that way, have a chat with Pixel and Pine. We build and maintain Australian small business websites that load fast on day one and stay fast well after launch.
