your site is slow. here's what it's costing you.

here's the uncomfortable thing about your website: you have never once experienced it the way a customer does. you load it on office wifi, on a laptop, with every asset already sitting in your browser cache, and it appears instantly. a customer loads it on a phone, on mobile data, on a street corner, having never visited before.

those are completely different experiences, and the gap between them is where a surprising amount of business quietly disappears.

why small business sites end up slow

it's rarely one catastrophic problem. it's an accumulation, and almost always some combination of these four:

• images straight off a camera. a photo can easily be four megabytes when the page needs a two-hundred-kilobyte version. this is the most common cause by a distance and the easiest to fix.
• plugin sprawl. every plugin loads its own scripts and stylesheets, on every page, whether that page uses the feature or not. twenty plugins is twenty tolls paid on every single visit.
• fonts loaded badly. pulling six weights of a typeface when the design uses two, and blocking the text from appearing until they arrive.
• third-party scripts. chat widgets, tracking pixels, review embeds, booking tools. each one is a request to somebody else's server, and your page is only as fast as the slowest of them.

test it properly, in two minutes

open google's pagespeed insights, put your url in, and read the mobile tab — not the desktop one, which will always look better and always matters less. then do the honest version: take your own phone off wifi, open your site as if you'd never seen it, and count.

if you find yourself mentally excusing the wait because you know what's loading, that's the answer. a customer extends no such courtesy.

the four fixes that recover the most

compress and resize every image. nothing should be wider than about twice its display size, and everything should be webp with a jpeg fallback. on most small business sites this alone cuts total page weight by more than half.

delete plugins you don't use. not deactivate — delete. then look hard at the ones you do use and ask whether the feature is worth the load it adds on every page.

subset your fonts and set a fallback. load only the weights the design actually uses, and make text visible in a system font immediately rather than leaving a blank space while a webfont downloads.

audit third-party scripts ruthlessly. the chat widget nobody has used in four months is costing you every visitor who arrives after it. remove it.

when it's not worth fixing

sometimes the honest answer is that patching a slow site is throwing money at a structure that will never be fast. if it's built on a heavy theme with a page builder and a stack of plugins holding it together, you can spend real money getting it from eight seconds to five — and it'll still be slow, and it'll drift back.

that's the point at which rebuilding is cheaper than maintaining. it isn't always the answer and we'll tell you when it isn't, but a site that fights you every time you touch it is a cost you're already paying, just in instalments.