What's Lurking Under the Bonnet: The Backend Costs Your Web Agency Never Told You About

There's a conversation that almost never happens between a web agency and their client. It's not about colours, fonts, or whether the logo should be a bit bigger. It's about what's actually running underneath the thing — the server setup, the database structure, the hosting environment, the tangle of dependencies that hold the whole show together.

Most businesses never hear this conversation because, frankly, most agencies don't want to have it. It's easier to sell a beautiful homepage than explain why your PHP version is three releases behind and your database is doing full table scans on every page load.

But ignorance here isn't bliss. It's expensive.

The Bit Everyone Ignores Until It Breaks

Let's be direct about something. When UK businesses commission a new website, the conversation almost always centres on design. That's understandable — design is tangible, it's visible, it's the thing you can show your colleagues and get a thumbs up on. Backend infrastructure, by contrast, is invisible until it isn't.

And when it stops being invisible, it tends to announce itself in the worst possible ways: a site that crawls under modest traffic, an e-commerce checkout that drops transactions during busy periods, a hosting bill that mysteriously creeps upward, or a security breach that costs far more to clean up than it ever would have cost to prevent.

The uncomfortable truth is that a visually stunning website running on a poorly configured server is a bit like a freshly painted house with damp in the walls. It looks fine right up until it really, really doesn't.

Hosting: Where Good Money Goes to Die Quietly

Shared hosting is where a lot of small and medium-sized UK businesses end up, usually because it's cheap at the point of purchase. And for a simple brochure site with light traffic, it can be perfectly adequate. The problem is that businesses often outgrow it without realising, or they're put onto shared infrastructure that was never right for their needs in the first place.

The hidden cost isn't just performance — though that matters enormously, and Google's Core Web Vitals assessments make it matter commercially. The hidden cost is in what shared hosting can't do. It can't scale cleanly when you run a campaign that drives traffic. It can't isolate your site from a noisy neighbour on the same server. And when something goes wrong at 11pm on a Friday, you're often on your own with a ticket queue.

Managed cloud hosting, properly configured, costs more upfront. But when you factor in the engineering time spent firefighting on cheap infrastructure, the calculus often shifts dramatically.

Databases That Nobody Ever Cleaned Up

Here's something that will be familiar to anyone who's ever inherited a WordPress site that's been running for a few years: the database is almost certainly a mess.

Post revisions piling up in the thousands. Transient options that were never cleared. Tables from plugins that were deactivated years ago but never properly removed. Log entries from automated processes that nobody thought to cap. None of this is catastrophic on its own, but collectively it adds weight — and that weight slows things down.

More importantly, nobody tells clients this is happening. The site was built, handed over, and the ongoing hygiene work was either never discussed or quietly dropped from the scope. So the database bloats, queries take longer, and the hosting bill edges up as resource usage climbs.

A proper backend audit will surface all of this. The fix is usually not dramatic — a scheduled cleanup process, some query optimisation, removing the ghost data from long-dead plugins. But you can't fix what you don't know is there.

The Code You're Paying to Maintain Without Knowing It

Custom code is where things get genuinely murky for non-technical business owners. When an agency builds something bespoke — a booking system, a product configurator, an API integration — that code becomes part of your infrastructure. And code has maintenance costs.

Dependencies go out of date. Libraries that were current in 2021 have security patches in 2024. Integrations with third-party services break when those services update their APIs. Functions that were written to work with one version of a framework need revisiting when the framework moves on.

The agencies that are straight with you will explain this upfront. They'll talk about technical debt, they'll discuss a maintenance retainer, they'll give you a realistic picture of what it costs to keep bespoke code healthy over time. The ones that aren't straight with you will hand over the keys and disappear, leaving you to discover the ongoing costs yourself — usually at an inconvenient moment.

What a Real Backend Audit Actually Looks Like

If you've never had a proper backend review of your website, here's roughly what it should cover:

Server and hosting configuration — Is your PHP version current? Is caching configured properly at the server level? Are you on infrastructure that matches your actual traffic and usage patterns?

Database health — How large is your database relative to what it should be? Are indexes in place on frequently queried columns? Are there orphaned tables from removed plugins or old migrations?

Code quality and dependencies — Are your third-party libraries and frameworks up to date? Are there known vulnerabilities in your current stack? Is the custom code documented in a way that any competent developer could pick up and work with?

Deployment and backup processes — How does code get from development to live? Are backups running, and have they ever been tested by actually restoring from one? Is there any kind of staging environment?

Security posture — Beyond the SSL certificate that everyone has now, are there proper controls in place? Are admin interfaces protected? Are file permissions sensible?

None of this is exotic. It's the kind of thing that a good technical agency should be reviewing as a matter of course. But in practice, a lot of UK business websites have never had anyone look at them this carefully.

The True Cost of Ownership Question

When you're evaluating what a website actually costs, the build price is only the beginning of the story. The ongoing cost of ownership — hosting, maintenance, security, performance — is where the real money lives over a three-to-five year horizon.

A site built cheaply on fragile infrastructure, with no documentation, no maintenance plan, and no thought given to the backend, will cost you more in that window than a properly engineered solution with a clear support structure. Not in dramatic, visible ways necessarily — but in the accumulated friction of slow performance, the odd afternoon lost to a broken plugin, the emergency developer call when something critical fails.

At WebDorking, this is the conversation we'd rather have at the start than the end. Surrey businesses deserve to know what they're actually buying — not just what it looks like, but what's running underneath it and what it's going to cost to keep it running well.

The design is the easy bit. The backend is where the real craft lives.