Hosting decisions are quiet. They tend to look small until something breaks during a launch week, and then they look enormous. The aim of these notes is to make the quiet part visible: which criteria actually decide whether a small site stays fast, stays online, and stays affordable when traffic shifts.
For a Ukrainian-language version of the same thinking, see Kriterii vyboru hostynha dlya saytu.
Static vs dynamic
The first useful question is whether the site needs a database at all. A surprising number of small sites do not. A static export with a sensible build pipeline is faster, cheaper, and harder to break. The trade-off is publishing flow: if non-technical editors will update copy directly, a dynamic CMS pays for itself quickly. If a single person will maintain the site from a repo, a static stack is usually the calmer choice.
DNS and SSL basics
DNS is the shortest list of records you can keep clean. An apex pointed at the host, a single CNAME for www, mail records if mail is needed, and nothing decorative. SSL should be issued automatically and renewed without intervention. If either of those needs hand-holding, the host is making your life harder than it needs to be.
Caching basics
Caching is the layer that absorbs the surprises. Edge caching for static assets is almost always a win. HTML caching depends on whether the site changes often enough to warrant short TTLs. The most common mistake is leaving everything default and then fighting stale pages on a launch day. The simplest fix is choosing one cache strategy early and writing it down somewhere boring.
A practical hosting checklist
- Server response under 250 ms on a typical page.
- Daily automated backups, 14 days retention, one-click restore.
- Modern runtimes available (current PHP / Node / Python lines).
- Free SSL with auto-renewal.
- Honest support, ideally with documented response targets.
- Renewal pricing visible before checkout.
- An unfussy migration path in and out.
Where this fits next
A hosting decision is the natural follow-on to a domain profile review. The checklists page keeps a printable form of the requirements list. For favicon and icon-related setup, see the favicon notes.