Why a hosting page with positions, not a listicle
Most "best hosting" pages are affiliate catalogs, the recommendation is the commission. This page takes positions, names tradeoffs, and states what this practice refuses to build on, because hosting is the floor everything stands on: the slow-store triage and the Core Web Vitals rescue both start at the hosting tier more often than at the code. One disclosure: this site itself runs on an edge platform, chosen for this launch's requirements, not offered as a general recommendation for every WordPress estate.
The recommendations, by situation
- Business WordPress site (the common case): managed WordPress hosting. The Kinsta / WP Engine / Rocket-class tier, staging built in, server-level caching, daily backups, support that knows WordPress. Costs more than shared; worth it the first time an update needs a rollback or traffic spikes. The default recommendation for any site where the website is the business.
- Small brochure sites on real budgets: quality shared hosting. The SiteGround / Cloudways class, not the $2/mo estates. Honest boundary: shared runs a quiet brochure site fine; it does not run a busy store, and no maintenance plan can compensate for a starving server.
- Stores and applications: provisioned cloud matched to load. WooCommerce at volume and custom applications want dedicated resources, object caching and a database tier, the WooCommerce scale guide maps that ladder. Managed platforms (Shopify; edge platforms for static and headless) buy their keep by deleting whole categories of work.
- Static and headless builds: edge platforms. This site's pattern, static output on an edge network, is the fastest, cheapest shape when the build allows it. The trade: dynamic features need explicit architecture (the headless guides).
What we refuse to manage, plainly
- The $1–2/mo "everything unlimited" estates. Oversold servers are slow by design, backups are upsells, support is a script. Building there is quoting a future emergency.
- End-of-life stacks and abandoned panels. Hosting that no longer receives security updates puts the security work on sand.
- "Hosting and code" bundles from one vendor. When the host controls the code too, every performance conversation becomes an upsell and leaving becomes a project. Hosting and development are different contracts with different incentives, this desk hosts client sites where asked, but the separation is the point.
- Hosting you cannot leave. Proprietary builders and exit-hostile hosts contradict the ownership clause, the same rule that governs domains and email: everything in your name, always.
Migration between hosts is routine, scoped work, the migrations cluster covers the discipline, and the brief starts it with the current host and the complaint.