ACT III · Build
Website Speed Optimization: The Basics Every Business Owner Should Understand
Not a developer deep-dive. The concepts explained simply enough to know what you're paying for.
Our trust-focused article on page speed covers why slow loading costs you visitors. This one is about the mechanics — what actually makes a site fast or slow, explained plainly enough that a non-technical business owner can understand what a developer is actually doing.
The biggest lever: images
Unoptimised images are, by a wide margin, the most common cause of a slow small business site. A photo straight off a modern phone camera can be several megabytes — completely unnecessary for how it'll actually display on a webpage. Proper optimisation compresses images and serves them at the right size for the device viewing them, often cutting load-relevant weight dramatically with no visible quality loss.
Hosting quality
Cheap, oversold shared hosting — where one server handles far more sites than it comfortably should — is a common, invisible cause of slow performance that has nothing to do with how well the site itself was built. This is part of why hosting quality is worth treating as a real line item, not just the cheapest option available.
Code efficiency
How a site is actually built matters — a site generated by a bloated page builder can ship far more code than the page actually needs, all of which the visitor's browser has to download and process before anything appears. This is part of the case for custom, clean-built sites covered in our Next.js article — less unnecessary weight, faster real-world performance.
Third-party scripts
Chat widgets, tracking pixels, embedded fonts from multiple sources, social media embeds — each one adds a request the browser has to make and wait on. They're often genuinely useful, but each one has a real performance cost that's worth weighing against its actual value, rather than adding every available tool by default.
- ■Compress and properly size every image before it goes on the site
- ■Choose hosting appropriate to the site's actual traffic and needs, not just the cheapest tier available
- ■Keep the underlying code clean and avoid unnecessary bloat from page builders or plugins
- ■Audit third-party scripts periodically — remove what isn't actually earning its performance cost
None of this is about chasing a perfect score for its own sake. It's about staying under the roughly 3-second threshold where, per Google's own mobile research, over half of visitors are already gone.
What to ask if you're not sure your site is fast enough
Ask whoever manages your site what its actual load time is, on mobile, on a real connection — not just "it feels fine on our office wifi." If nobody can answer that with a real number, that's usually a sign it hasn't been properly measured, let alone optimised.
Sources & further reading
Speed optimisation is built in, not bolted on
Every TFLYX package includes real image and speed optimisation as standard.
More from ACT III · Build
What a Website Maintenance Plan Actually Covers (And Why "Set and Forget" Is a Myth)
A website isn't a purchase you complete once. Here's what actually needs ongoing attention, and why.
Building CounterMate: Designing Software for Retail Counters, Not Boardrooms
The second blade of the SME toolkit — still in development, and being designed for a very different user than most business software assumes.
What Happens After You Book a Website Package — A Behind-the-Scenes Walkthrough
No mystery, no black box. Here's the actual process from booking to launch.