Choosing hosting, explained without the jargon

We end up explaining this on discovery calls often enough that it deserved writing down. Here is choosing hosting without the vocabulary that usually surrounds it.

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Check it against what you would want a competitor's site to get wrong.

The short version

Match the hosting to the site, not to the price alone. Getting it slightly wrong is survivable. Ignoring it entirely is not. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. In practice this is a scheduling problem more than a technical one.

Static sites need far less than most people buy. Small and consistent beats large and occasional here. It rarely shows up as a line item, which is exactly why it slips.

A reasonable first step

Support quality matters most on the day something breaks. The teams that handle this well are rarely the ones with the biggest budgets. The version that survives contact with a real deadline is the simple one.

The short version

Performance work is mostly subtraction, which makes it unpopular and effective. Three things worth confirming about choosing hosting before you move on:

• Someone can say what the current setup is without going to look
• Static sites need far less than most people buy — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you want a second opinion on how yours is set up, ask.