Before a procedural walkthrough ships, every step runs on at least two brands when the task is host-specific, or twice on the same stack on different days when it is not. Console errors are captured, UI label drift between regions is noted, and copy is revised the moment a vendor moves a button. Screenshots and paths are spot-checked quarterly. Security-sensitive actions (DNS, SSL, billing) trigger recovery-option checks plus links to the host's own documentation for authoritative wording.
Analytics unique visitors × average page size suggests egress; heavy media multiplies needs.
Most visits should hit full-page cache. If everything is logged-in or cart-based, you need higher PHP worker headroom.
Page builders, LMS, and WooCommerce raise the floor. do not use bare-minimum tiers.
If the host publishes PHP workers or vCPU, compare honestly; if opaque, favour known performers (LiteSpeed, managed WP).
Ensure the tier includes daily backups or budget UpdraftPlus remote storage.
Pick providers where moving from shared → cloud/VPS is a known runbook, not a rebuild.