Hosting in Plain Language
What hosting actually is, what a practice site genuinely needs, the overpaying patterns to recognise, and the three questions that matter more than any feature list.
Hosting is where websites physically live — a computer somewhere, always on, serving your pages to whoever asks. That's the entire concept, and its simplicity is worth holding onto, because the hosting industry's pricing pages work hard to make it feel like aerospace: tiers, add-ons, acronyms, "performance" packages. For a practice site, nearly all of that complexity is someone else's business model.
What a practice site actually needs from hosting: it loads fast (visitors and machines both judge slowness), it stays up (boring, measurable, non-negotiable), it's secured with the basics (the padlock certificate — standard and free-of-charge almost everywhere now — and current software), and it's yours to leave (your account, your files exportable, no hostage geometry). Everything beyond these four is either included anyway, or a question mark to interrogate.
The honest landscape
Modern practice sites live in a few habitats, each fine when matched to the site: managed platforms (the site-builder subscriptions) bundle hosting invisibly — you're paying for the whole appliance, hosting included, and the real questions are about ownership and exit, not servers; managed hosting for common site systems takes the update-and-security burden off you for a modest premium — usually the right call for a practice with a conventional site and no technical appetite; modern app hosting (where newer custom-built sites deploy) is often startlingly cheap-to-free at practice scale and extremely fast — the relevant questions live with whoever built the site; and the legacy shared-hosting account — the $30-a-month plan from 2014, renewed annually by inertia — is where the overpaying mostly lives.
The overpaying patterns
Paying premium prices for commodity hosting. The decade-old plan, never re-examined, at several times today's market rate for the same thing. A once-every-few-years sanity check on renewal invoices is the whole defence.
Paying for the padlock. Certificates ("SSL") are free and automatic on modern platforms; a separate yearly line item for one is a legacy toll.
Paying for capacity theatre. "Unlimited bandwidth" tiers and performance add-ons sized for traffic a practice site will never see. Your site serves hundreds of important visitors a month, not millions of idle ones.
Paying twice for backups you've never tested — an add-on worth having only if restores actually work, which is a thing to verify, not purchase.
The test that cuts through all of it: three questions to whoever hosts you — what am I paying monthly, all-in? when did someone last update the software this site runs on? if I left next month, exactly what do I take and how? Confident, specific answers: you're fine, price permitting. Fog: the foundations audit has found something.
Questions practices actually ask
Is cheap hosting risky for a professional practice? Cheap and modern is fine — the price of good hosting has genuinely collapsed. The risk lives in stale: old software on any tier is how sites get hacked and delisted, and staleness happens on expensive plans too.
Does hosting affect my Google and AI visibility? Through speed and uptime, yes — both are table stakes for being read. Past "fast and up," hosting exotica moves nothing; the content and record do.
Should the hosting account be mine or my web person's? Yours, with them invited in — the ownership rule, verbatim. "It's easier under our agency account" is convenient right up until the relationship isn't.
How do I know if my site is slow? Load it on a phone, off wifi, and count honestly — then use any of the free speed-test tools for the number. If either embarrasses you, ask your provider why before buying anything: the cause is more often a bloated site than thin hosting.
Part of The Foundations — the ground everything stands on.