What hosting actually buys you

Across 10,164 leads carrying a follow-on opening, hosting is the single largest at 1,017, just ahead of maintenance at 928. People come back about hosting more than about anything else, which is interesting given how little attention it gets when a site is first built.

Part of the reason is that hosting is invisible while it works. The difference between a good host and a poor one is entirely undetectable on an ordinary Tuesday, and completely obvious on the one day a year when something goes wrong.

What the price is actually buying

Hosting comparison tables lead with disk space and bandwidth. Both are effectively free at the scale most sites operate at, which is precisely why they are at the top — they let a provider offer generous-sounding numbers that cost them nothing.

Restore speed deserves particular attention because it is the one that determines your actual exposure. A host that takes a backup nightly and can restore it in fifteen minutes gives you a very different risk profile from one that takes the same backup and needs a support ticket and four hours to put it back.

Shared hosting is fine, actually

There is a persistent idea that shared hosting is a compromise you graduate out of. For a large proportion of sites it is simply the correct answer, and paying for a dedicated environment that sits at three per cent utilisation is money spent on reassurance rather than performance.

The honest signals that you have outgrown it are specific: the site slows at predictable times of day, you are hitting resource limits in the control panel, or you need something at the server level that the platform does not permit. Absent those, more expensive hosting will not make a well-built site faster, and a badly built site will be slow on any hosting you buy.

The specifics that do move performance

• Where the server physically is. If your customers are in one region and your server is on another continent, you are paying a latency tax on every request, and no amount of caching fully removes it.
• Whether caching is handled at the platform level or left to a plugin. Platform-level caching is faster and one less thing to break.
• Whether a content delivery network is included and actually configured, as opposed to available as an upsell.
• The version of the underlying runtime. Hosts that keep it current are meaningfully faster and more secure than those still offering versions that reached end of life years ago.

The first is the one most often overlooked and most easily fixed. It is a decision made once at setup, usually by whoever had an existing account with a provider, and it silently affects every visit thereafter.

Who owns the account

One structural point that matters more than any performance consideration: the hosting account should be in your name, with your billing details, and you should have the login. An agency-owned hosting account is a hostage situation waiting for a disagreement, and it converts an ordinary supplier change into a migration project.

It is entirely reasonable for a supplier to manage the account on your behalf. It is not reasonable for them to be the only party who can access it. The distinction costs nothing to arrange at the start and is often impossible to arrange later, which is precisely when it becomes urgent.