Measure first with a real tool, then fix in this order: oversized images, too much JavaScript, slow hosting, then everything else. Images alone are the single biggest cause of slow small business websites, and they are usually the easiest thing to fix. Before spending a cent, it helps to know what slowness actually costs — because the measured figures are bigger than most people assume.
What Slow Actually Costs
These are not vendor estimates. They are measured results published by Google's web.dev team:
- The BBC found it lost an additional 10% of users for every additional second its site took to load.
- Vodafone improved Largest Contentful Paint by 31% and saw sales rise 8%.
- A Google-commissioned Deloitte study across 37 brands and more than 30 million sessions found that a 0.1 second improvement in load time lifted retail conversion rates by 8.4%, travel booking rates by 10%, and — most relevant if you sell services — form submissions on lead generation sites by 21.6%.
That last figure is the one to sit with. If your website's job is to produce enquiries, a tenth of a second is worth real money.
Step 1: Measure Before You Change Anything
Guessing wastes effort. Two free tools tell you what is wrong:
- PageSpeed Insights — paste your URL in and it reports both lab measurements and, if you have enough traffic, what real visitors experienced.
- Google Search Console — its Core Web Vitals report shows how real users experience your site over time, grouped by page type.
Test your homepage and your most important service page, on mobile and desktop. Write the numbers down so you can prove whether your work helped.
The three numbers that matter
Google's Core Web Vitals are assessed at the 75th percentile of page loads — meaning three out of four visits need to hit the target, not your best-case test:
- Largest Contentful Paint (LCP) — the main content should appear within 2.5 seconds. This is usually the one small business sites fail.
- Interaction to Next Paint (INP) — the page should respond to a tap within 200 milliseconds.
- Cumulative Layout Shift (CLS) — content should not jump around; 0.1 or less.
CLS is the one visitors feel most viscerally without knowing its name: you go to tap a link, an image finishes loading, everything shifts down, and you tap an ad instead.
Step 2: Fix Your Images (Usually the Biggest Win)
On the majority of slow small business sites we look at, images are the dominant cause. A photographer sends 4 MB files straight off the camera, someone uploads them untouched, and the homepage now weighs 20 MB.
Resize to the size actually displayed
If an image appears 800 pixels wide on screen, it does not need to be 4,000 pixels wide. Resize before uploading. This one habit often halves page weight.
Use a modern format
WebP and AVIF produce dramatically smaller files than JPEG or PNG at equivalent visual quality. Most platforms will convert automatically; if yours does not, convert before uploading.
Compress
There is a wide band where file size drops substantially and nobody can see any difference. Aim for that band rather than maximum quality.
Lazy-load anything below the fold
Images further down the page should load as the visitor scrolls, not all at once up front. Most modern platforms do this by default — worth confirming yours does.
Always set width and height
Declaring dimensions lets the browser reserve the space before the image arrives, which is the single most effective fix for layout shift.
Step 3: Cut the JavaScript You Do Not Need
This is the second big offender, and on template-based sites it is often invisible to the owner.
Every plugin, tracking script, chat widget, popup tool, review carousel and font loader adds work the browser must do before your page becomes usable. Sites accumulate these over years and nobody removes them.
- Audit your plugins and apps. Deactivate anything you cannot name a current purpose for. Sites commonly carry a handful of plugins nobody has used in two years.
- Count your tracking scripts. Analytics, a pixel, a heatmap tool, a tag manager loading three more things. Keep what you genuinely read; remove the rest.
- Be deliberate about chat widgets. They are among the heaviest common additions. If yours generates enquiries, keep it. If it exists because it seemed like a good idea, remove it.
- Limit web fonts. Two weights of one family is usually plenty. Six weights of three families is a meaningful delay.
Step 4: Check Your Hosting
If your images are optimised and your scripts are lean and the site is still slow to start responding, hosting is the likely constraint.
Signs you have outgrown cheap shared hosting: the site is fine at 7am and sluggish at 7pm; response times vary wildly between tests; the host's own dashboard mentions resource limits.
For a New Zealand audience, where your server sits genuinely matters. A site hosted in New Zealand or Australia will feel more responsive to Kiwi visitors than one hosted in Europe. A content delivery network reduces this problem by serving static files from locations nearer the visitor, and most modern platforms include one.
Step 5: Enable Caching and Compression
Two settings with outsized effect:
- Caching stores a prepared copy of your page so the server does not rebuild it for every visitor.
- Compression (Gzip or Brotli) shrinks files in transit. It is usually a switch, and it is usually already on — but worth verifying.
When the Platform Itself Is the Ceiling
Sometimes there is nothing left to optimise. A heavily themed site built on a page builder, loaded with plugins accumulated over five years, can hit a wall well short of the thresholds — and every further fix buys milliseconds while costing hours.
The honest test: if you have optimised images, removed unused scripts, enabled caching and moved to decent hosting, and LCP is still well over 2.5 seconds, the build is the problem. At that point a rebuild on modern foundations is usually cheaper than another year of incremental work. That is the conversation our website redesign service exists for — but do the free fixes first, because sometimes they are enough.
Common Mistakes
- Optimising without measuring. You cannot tell whether you helped, and you may spend hours on something irrelevant.
- Chasing a perfect score. A score of 100 is not the goal; being comfortably inside the thresholds for real visitors is.
- Testing only on desktop over fast wifi. Test on a phone, ideally on mobile data.
- Installing a "speed optimisation" plugin and calling it done. These help at the margins; they cannot undo a 20 MB homepage.
- Deleting things blindly. Change one thing at a time and re-measure, or you will not know what worked.
- Judging by your own experience. Your browser has your site cached. It is faster for you than for anyone else.
Do This Today
- Run PageSpeed Insights on your homepage and your main service page, mobile and desktop, and record the numbers
- Open Search Console's Core Web Vitals report to see what real visitors experience
- Find your three largest images and resize, convert and compress them
- Confirm every image has width and height set
- List every plugin, app and tracking script, and remove what you cannot justify
- Verify caching and compression are switched on
- Re-measure and compare against your starting numbers
Where We Come In
Images, unused plugins and caching are genuinely DIY, and they are where most of the available gain sits — we would rather you captured it yourself than paid for it. Where we help is diagnosis when the cause is not obvious, and rebuilds when the platform has become the limit. Our free website audit will tell you which of those you are dealing with.
Frequently Asked Questions
How fast should my website be?
Aim for Google's Core Web Vitals thresholds, measured at the 75th percentile of real page loads: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds, and Cumulative Layout Shift of 0.1 or less. Hitting those consistently for real visitors matters far more than a perfect test score.
Does website speed affect sales or enquiries?
Yes, measurably. The BBC found it lost an additional 10% of users for every extra second of load time, and a Google-commissioned Deloitte study across 37 brands found a 0.1 second improvement lifted retail conversions by 8.4% and form submissions on lead generation sites by 21.6%.
Why is my website slow on mobile but fine on desktop?
Phones have less processing power and often slower connections, so heavy JavaScript and oversized images hurt far more. Your own experience is also misleading because your browser has the site cached. Always test on a phone, ideally on mobile data rather than wifi.
Will a caching plugin fix my slow website?
It will help at the margins, but it cannot compensate for the underlying causes. If your homepage loads 20 MB of unoptimised images and a dozen unused plugins, caching serves that same bloated page slightly faster. Fix the weight first, then cache.
Is it worth rebuilding a slow website instead of fixing it?
Only after the cheap fixes are exhausted. If you have optimised images, removed unused scripts, enabled caching and moved to decent hosting, and Largest Contentful Paint is still well beyond 2.5 seconds, the build itself is the ceiling and further tuning has poor returns. Until then, keep optimising — it is far cheaper.
Next in this series: How to Tell If Your Website Is Actually Working.