Choosing a Web Host

The terminology around web hosting has been deliberately blurred by marketing departments for twenty years. “Managed WordPress hosting” is now used to describe everything from Kinsta (Google Cloud infrastructure, machine-learning malware detection, sub-24-hour expert support) to a shared host that installs WordPress for you and calls the auto-update cron job “management.” Understanding the difference between these categories is the entire exercise before you spend money.

Shared hosting is the baseline: you are on a physical server with dozens or hundreds of other sites, sharing CPU, RAM, and I/O. Your site’s performance depends partly on what your neighbours are doing, and “unmetered bandwidth” is a marketing term for a shared resource pool with implicit limits that emerge when you exceed what the host deems reasonable. Shared hosting from providers like SiteGround’s entry tiers works fine for low-traffic sites with modest WordPress installs. It is inexpensive — SiteGround’s introductory pricing starts at $3–4/month — but those are promotional rates; renewal pricing is materially higher and worth checking before you buy. Shared hosting is the correct choice for personal sites, development environments, and sites that see fewer than a few hundred visits per day.

Managed WordPress hosting describes a category where the host takes on the operational work of running WordPress well: automatic core and plugin updates, daily backups, malware scanning, a staging environment, and server configuration tuned for WordPress specifically (PHP-FPM, Redis object caching, custom NGINX rules). Kinsta does this on Google Cloud’s premium-tier infrastructure, which means your site sits on the same network as YouTube and Google Search — low-latency global routing that matters when your users are geographically spread. WP Engine has been the enterprise-standard managed WordPress host for over a decade, with strong agency tooling (multiple users, client billing integration, the Genesis theme framework included) and a well-documented track record for high-traffic sites. Both are priced accordingly — Kinsta from $30/month for a single site, WP Engine from $25/month — and the support quality at those tiers is categorically different from shared hosting: you are talking to engineers who know WordPress deeply, not a first-line support agent reading from a script.

Cloudways occupies the middle ground. It is not a host in the traditional sense; it is a managed platform that provisions virtual machines on DigitalOcean, Vultr, Linode, AWS, or GCP and layers a management interface on top. Starting from $11/month on DigitalOcean infrastructure, you get server-level control (PHP version, Redis, web server) with a panel that is accessible to non-sysadmins, plus team access, staging, and monitoring. The trade-off is that Cloudways requires more active management than Kinsta or WP Engine: you own the server patching cadence and some of the security decisions. That is a reasonable deal for developers and technically confident users who want managed-WordPress convenience at cloud-infrastructure pricing without the full abstraction layer.

The selection criteria that actually matter are: infrastructure quality (shared server pool vs. isolated cloud VMs), support tier (can you reach someone who can diagnose a PHP error at 2am?), staging environment quality (one-click copy, database sync, Git-deployable), backup frequency and restore workflow (daily is the minimum; hourly is better), and total renewal cost at your traffic tier. SiteGround is the sensible default for smaller sites where total cost matters most. Kinsta or WP Engine is the correct choice when a site generates revenue and downtime has a direct cost. Cloudways is the right call when you want cloud infrastructure without a full server-management commitment and have some technical confidence.

When to pick what: use SiteGround for starter and small-business WordPress sites where budget is the primary constraint and traffic is predictable. Use Kinsta when performance and support quality are the priority — agency client sites, e-commerce, media sites with traffic spikes. Use WP Engine when you are in an agency context and need multi-site management, enterprise support SLAs, and the ability to hand clients their own login. Use Cloudways when you want infrastructure-level control without paying full managed-host prices and are comfortable doing basic server hygiene yourself.