What makes a small business website genuinely fast, in plain English

Customers do not notice a fast website. They just use it, buy the thing, and leave. But they absolutely notice a slow one, and usually, they notice it by hitting the back button and going to your competitor.

The web did not get worse over the last decade, but our expectations got Amazon-shaped. We expect everything to load instantly on a dodgy 4G connection while sitting on a train.

When a business owner comes to me complaining about a slow site, they usually assume they need to pay for more expensive hosting. Sometimes that is true, but throwing a faster server at a badly built website is like putting a Ferrari engine in a tractor. It is still going to handle terribly.

Here is what actually makes a website fast, translated into plain English.

The Ryanair bag of image formats #

The number one reason small business websites run like treacle is massive, uncompressed photos. I regularly see sites where a plumber has uploaded a 6-megabyte photo directly from their iPhone to the homepage.

If you try to take a massive suitcase onto a Ryanair flight, they will charge you a fortune and hold up the queue. The internet works the same way. Every megabyte your customer's phone has to download costs them time.

The fix is modern image formats. We no longer use giant JPEGs or PNGs. We use formats like WebP and AVIF. They look exactly the same to the human eye, but they take up a fraction of the file size. Compress once, load fast forever.

Time to First Byte (the server's reaction time) #

You will see the acronym TTFB thrown around a lot. It stands for Time to First Byte.

Imagine you are at a restaurant. TTFB is the time it takes between you placing your order and the waiter nodding to acknowledge it. If the waiter stands there staring blankly for three seconds before walking to the kitchen, the service feels slow, even if the food eventually comes out quickly.

If your web hosting is cheap, overcrowded, or located in a dodgy data centre in another continent, your TTFB will be high. Your customer's phone is shouting "Can I have the homepage please?" and your server is taking two seconds just to reply "Yes, hold on." Good UK/Irish hosting fixes this overnight.

Death by a thousand trackers #

Third-party scripts are the silent killers of web performance.

This is what happens when you add a Facebook Pixel, a Google Analytics tag, a live chat widget, a cookie popup, and a fancy font to your site. Every single one of these scripts forces the customer's phone to go to a different server, ask for permission, download a file, and execute some code.

• Keep analytics lean
• Remove the chat widget if you never reply to it anyway
• Use system fonts where possible

Every script is a tax on your user's battery life and patience.

Caching (remembering the answer) #

If I ask you what 12 multiplied by 12 is, you do not need to do the maths in your head. You just know the answer is 144 because you memorised it.

That is what caching does for your website. Without caching, every time someone visits your homepage, your server has to rummage through the database, stitch the header, footer, and content together, and hand it over. It is exhausting.

With page caching, the server does the hard work once, takes a snapshot of the finished page, and just hands that snapshot to the next thousand visitors instantly. At Tidalux, we use LiteSpeed server-level caching. It isn't a flex, it is just the baseline for how the modern web should work.

Common questions #

Stop letting massive images and bloated code steal your customers. If you want to know exactly what is slowing you down, run your site through WaveCheck and we will tell you the truth.