The Five Hosting Types Explained
Before comparing providers, you need to understand what you are actually buying. The five main hosting types represent very different underlying infrastructure, different levels of resource sharing, and very different price-to-performance trade-offs.
Shared Hosting
Shared hosting puts your website on a server alongside hundreds or thousands of other websites, all sharing the same CPU, RAM, and network resources. When another site on the same server gets a traffic spike or runs inefficient code, your site slows down too – this is called the “bad neighbor effect”. Shared hosting is cheap (often $3-8/month) but comes with significant limitations: CPU usage caps, memory limits, no root access, outdated PHP versions on some hosts, and performance that is inconsistent and hard to predict.
Shared hosting is the right choice for one specific use case: small websites in their earliest stage with very low traffic that need to keep costs to an absolute minimum. A personal blog, a small portfolio site, or a local business card site that gets a few hundred visitors per month can work fine on shared hosting. Once you start generating real traffic or running a business that depends on the site, you will hit the limits quickly.
VPS (Virtual Private Server)
A VPS gives you a dedicated slice of a physical server using virtualization. You get your own allocated CPU cores, RAM, and disk – no sharing with other customers. You also get root access, meaning you can install any software, configure the server however you like, and choose your operating system. The trade-off is management complexity: you are responsible for server security, software updates, and configuration. Unmanaged VPS hosting (from providers like DigitalOcean, Linode/Akamai Cloud, and Vultr) typically starts at $6-12/month for an entry-level instance.
Managed WordPress Hosting
Managed WordPress hosting is VPS-level (or better) infrastructure where the hosting provider handles all the server management, WordPress-specific optimizations, security patching, and often backups and staging. You get performance without the management burden. Providers like Kinsta, WP Engine, and Cloudways (managed cloud) offer this at price points from $15/month (entry-level) to $100+/month for high-traffic sites. The value proposition is simple: you pay more but get performance and peace of mind without needing a sysadmin.
Cloud Hosting
Cloud hosting is infrastructure distributed across multiple physical servers and data centers, allowing resources to scale dynamically based on demand. Unlike VPS hosting where you pay for fixed resources whether you use them or not, cloud hosting (particularly at AWS, Google Cloud, and Azure) can bill by the hour or even by the minute. The major advantage is elasticity – your site can handle traffic spikes automatically. The challenge is cost predictability: bills can spike unexpectedly if traffic or resource usage surges. Cloud hosting also typically requires the most technical expertise to set up and manage.
Dedicated Servers
A dedicated server is an entire physical machine reserved exclusively for your use. You get all the CPU, RAM, and storage on that hardware, with zero resource sharing. Dedicated servers start at $80-100/month for entry-level hardware and go up to $500+/month for high-performance configurations. They are appropriate for high-traffic sites (hundreds of thousands of monthly visitors), applications with very high CPU requirements, or businesses with strict data isolation requirements. For most WordPress websites, dedicated servers represent overkill – the same money spent on well-configured managed cloud hosting will deliver comparable or better results with more flexibility.
What to Actually Look For When Evaluating Hosting
Marketing pages for hosting providers look similar. Everyone claims 99.9% uptime, blazing fast speeds, and 24/7 support. Here is what actually matters and how to evaluate it:
PHP Version Support
PHP 8.2 and 8.3 offer significant performance improvements over older versions. WordPress has supported PHP 8.x since version 5.9. Yet some budget shared hosts still default to PHP 7.4 or even 7.2 – versions that are past end-of-life and no longer receive security updates. Before signing up, verify that the host supports PHP 8.1 or higher and allows you to choose your PHP version per site.
HTTP/2 and HTTP/3 Support
HTTP/2 enables multiplexing (sending multiple requests over a single connection) and header compression, which meaningfully reduces page load times compared to HTTP/1.1. HTTP/3 (based on QUIC) reduces connection setup time further. Most decent hosts now support HTTP/2. HTTP/3 support is still being rolled out but worth checking for. To verify, load your site and check the protocol column in Chrome DevTools network tab, or use tools like httpstatus.io.
SSH Access
SSH access lets you log into your server directly via the command line, which is essential for running server-side commands, troubleshooting, running database migrations, and deploying via git. Most managed WordPress hosts provide SSH access. Budget shared hosts often do not. If you are doing any serious WordPress development or management work, SSH access is a hard requirement.
Staging Environments
A staging environment is a copy of your live site where you can test plugin updates, theme changes, and code changes before pushing them to production. Without staging, every update is a live experiment on your real site. Managed WordPress hosts (Kinsta, WP Engine, Cloudways, Flywheel) include staging. Shared hosts typically do not. If your site is more than a personal blog, staging is not optional.
Uptime SLA
A 99.9% uptime SLA sounds excellent until you do the math: 99.9% uptime means 8.7 hours of downtime per year is within the acceptable service level. 99.99% uptime means 52 minutes per year. 99.999% (“five nines”) means 5 minutes per year. Most providers offer 99.9%. Premium managed hosts like Kinsta advertise 99.9% with more aggressive SLAs and credit policies. What matters more than the SLA itself is what compensation you receive if the SLA is breached – most providers offer service credits, not cash refunds.
Server Location
Physical distance between your server and your visitors adds latency. A server in Sydney serving visitors in London adds approximately 250-300ms of round-trip time that a London server would not. Most hosting providers let you choose your data center region. Choose the region closest to the majority of your audience. If your audience is global, supplement with a CDN (Cloudflare, Fastly, or the CDN included with managed hosts) to serve static assets from locations close to every visitor.
Provider Comparison: Shared Hosting
| Provider | Starting Price | PHP Version | Staging | SSH | Best For |
|---|---|---|---|---|---|
| SiteGround | $2.99/mo (promo) | 8.3 | No (shared plans) | Yes | Small sites, beginners |
| Bluehost | $2.95/mo (promo) | 8.1 | No | No | Very basic beginner sites |
| Hostinger | $1.99/mo (promo) | 8.2 | No | Yes (higher plans) | Budget personal sites |
| A2 Hosting | $2.99/mo (promo) | 8.2 | No | Yes | Speed-focused shared |
| DreamHost | $2.59/mo (promo) | 8.2 | No | Yes | Developer-friendly shared |
Promotional pricing for shared hosting is consistently 50-80% below the renewal price. Always check the renewal rate before committing. A plan that costs $2.99/month for year one often renews at $12-14/month.
Provider Comparison: Managed WordPress Hosting
| Provider | Entry Plan | Visits/Mo | Staging | CDN | Standout Feature |
|---|---|---|---|---|---|
| Kinsta | $35/mo | 25,000 | Yes | Yes (Cloudflare) | Google Cloud C2 machines, excellent dashboard |
| WP Engine | $25/mo | 25,000 | Yes | Yes | Mature platform, Genesis theme included |
| Cloudways | $14/mo | Pay per resource | Yes | Yes (add-on) | Choose your cloud provider (DO, AWS, GCP, etc.) |
| Nexcess | $13.30/mo | 30,000 | Yes | Yes | Good WordPress/WooCommerce focus |
| Rocket.net | $30/mo | 25,000 | Yes | Yes (Cloudflare Enterprise) | Cloudflare Enterprise CDN at this price point |
| Pressable | $19/mo | 30,000 | Yes | Yes | Good WordPress-specific tooling |
Kinsta vs WP Engine: The Direct Comparison
These two are most often compared head-to-head. Kinsta runs on Google Cloud’s premium tier with C2 compute-optimized machines and a global Cloudflare CDN integration. Their dashboard is genuinely excellent – clean, fast, and informative. WP Engine has a longer history, more mature enterprise features (like their DevKit local development environment), and a slightly lower entry price, but their infrastructure is showing its age compared to Kinsta’s more modern Google Cloud base. For a new site looking for top-tier managed hosting, Kinsta has the edge on pure performance benchmarks. WP Engine wins on ecosystem maturity and enterprise tooling.
Cloudways: The Flexible Middle Ground
Cloudways sits between unmanaged VPS and fully managed WordPress hosting. You choose your underlying cloud provider (DigitalOcean, Linode, Vultr, AWS, or Google Cloud), and Cloudways handles the stack configuration – Nginx, PHP-FPM, Redis, MySQL – and provides a control panel for managing your apps. The result is near-VPS performance at near-managed prices, starting at $14/month for a DigitalOcean 2GB droplet. The trade-off is that you are not getting the same degree of WordPress-specific optimization as Kinsta or WP Engine, and staging is functional but less polished.
Provider Comparison: Cloud and VPS Hosting
| Provider | Entry Plan | RAM | Storage | Bandwidth | Best For |
|---|---|---|---|---|---|
| DigitalOcean | $6/mo | 1 GB | 25 GB SSD | 1 TB | Developers, simple deployments |
| Linode (Akamai Cloud) | $5/mo | 1 GB | 25 GB SSD | 1 TB | Competitive pricing, good network |
| Vultr | $6/mo | 1 GB | 25 GB SSD | 1 TB | Many data center locations |
| AWS Lightsail | $5/mo | 1 GB | 40 GB SSD | 2 TB | AWS ecosystem, predictable pricing |
| AWS EC2 | ~$8/mo (t3.micro) | 1 GB | EBS billed separately | Pay per GB | AWS power users, autoscaling |
| Google Compute Engine | ~$7/mo (e2-micro) | 1 GB | 10 GB SSD | Pay per GB | GCP ecosystem, Google Cloud CDN |
For unmanaged VPS, DigitalOcean is typically the starting point for developers due to its excellent documentation, clean API, and large community of tutorials specifically for hosting WordPress. Linode offers comparable pricing with a strong network and has rebranded as Akamai Cloud Computing. Vultr distinguishes itself with the largest selection of data center locations (30+ locations as of this writing), useful if you need to serve a specific regional market from the closest possible geography.
WordPress-Specific Hosting Requirements
WordPress has its own performance and compatibility considerations beyond generic web hosting criteria. Here is what matters specifically for WordPress deployments:
PHP-FPM Over mod_php
PHP-FPM (FastCGI Process Manager) handles PHP requests more efficiently than the older mod_php Apache module, especially under load. It allows better memory management and process isolation. Most modern hosts use PHP-FPM. If you are evaluating a VPS setup, use Nginx + PHP-FPM rather than Apache + mod_php.
Object Cache (Redis or Memcached)
WordPress makes many database queries to render each page. An object cache stores the results of expensive database queries in memory, so repeat requests return cached data without hitting the database. Redis is the preferred option – it is persistent across restarts and supports more data structures than Memcached. Kinsta and many other managed hosts include Redis. For VPS setups, installing Redis and configuring the Redis Object Cache plugin is one of the highest-impact performance improvements you can make.
MySQL 8.0 or MariaDB 10.6+
WordPress requires MySQL 5.7+ or MariaDB 10.3+, but newer versions offer meaningful query optimization improvements. MySQL 8.0 includes better JSON support, improved indexing, and window functions. MariaDB 10.6 introduces important performance improvements for InnoDB. If you are setting up a VPS from scratch, installing MariaDB 10.6 or higher is the current recommendation from the WordPress performance team.
OPcache Configuration
PHP OPcache compiles PHP files to bytecode and caches them in memory, eliminating the need to recompile the same PHP files on every request. It is included with PHP 5.5+ and enabled by default on most hosts, but the default configuration is often conservative. For WordPress, increase the OPcache memory allocation (opcache.memory_consumption) and the maximum number of cached files (opcache.max_accelerated_files) to cover all of WordPress’s core files plus your plugins and themes.
Cost Breakdown by Traffic Level
| Monthly Visitors | Recommended Hosting Type | Example Provider | Approximate Monthly Cost |
|---|---|---|---|
| 0 – 10,000 | Shared or entry managed | SiteGround StartUp / Hostinger Business | $10 – $20/mo |
| 10,000 – 50,000 | Managed WordPress | Kinsta Starter / Cloudways DigitalOcean 4GB | $35 – $50/mo |
| 50,000 – 200,000 | Managed WordPress (mid-tier) | Kinsta Business 1 / WP Engine Professional | $100 – $200/mo |
| 200,000 – 1M | Managed WordPress (high-tier) | Kinsta Business 2-4 / Cloudways AWS | $200 – $500/mo |
| 1M+ | Dedicated or custom cloud | AWS EC2 / GCP / Custom | $500+/mo |
These are rough guidelines. Traffic alone does not determine hosting needs – a WooCommerce store with complex product queries at 30,000 monthly visitors may need more resources than a static blog with 100,000 monthly visitors. Consider the number of concurrent users, the complexity of your database queries, and whether you run resource-intensive plugins like membership systems or page builders.
When to Upgrade Your Hosting
Watch for these signals that you have outgrown your current hosting:
- TTFB (Time to First Byte) consistently above 600ms – even with caching enabled, slow server response is a hosting problem
- 503 or 500 errors during normal traffic – you are hitting resource limits (memory, CPU, or connection limits)
- Google PageSpeed Insights shows “Reduce server response times” as a top issue
- Shared hosting CPU or bandwidth warnings from your provider
- Database connection errors during traffic spikes (hitting MySQL connection limits)
- You are selling products or services – a slow or unreliable store costs real money per minute of downtime
Server Location Strategy
Physical proximity between server and visitor affects latency – the delay between a request being sent and the first byte of response being received. Every 100 miles of fiber adds roughly 1 millisecond of round-trip time. While CDNs handle static assets (images, CSS, JS) from locations close to visitors, the initial HTML document request (and any uncached dynamic requests) still hits your origin server.
If your audience is primarily in one region, put your server there. If your audience is global, choose a central US location (like Chicago or Dallas) as a compromise point that is no more than 150ms from any major global market. Then layer a CDN on top to bring static assets within 20-40ms of every visitor worldwide. Cloudflare’s global Anycast network is the gold standard here and is free to use.
How to Migrate to a New Host
Migrating a WordPress site to a new host does not have to be risky if you follow a structured process. The key is doing the work before changing your DNS so you can verify everything works before any visitors are affected.
Migration Steps
- Back up everything first – create a complete backup of your database and all site files before touching anything. Use a plugin like All-in-One WP Migration, Duplicator, or UpdraftPlus, or do a manual backup via phpMyAdmin and FTP. Verify the backup is complete and downloadable before proceeding.
- Set up the new server environment – install PHP, a web server, MySQL, and WordPress on the new host. Most managed hosts handle this automatically through their control panel or onboarding flow.
- Transfer your site files – upload your content directory and site configuration to the new server. Be careful not to overwrite the new server’s configuration with your old one until you have updated it with the new environment’s details.
- Import the database – restore your database backup on the new server via phpMyAdmin or a database management tool provided by the host. Most managed hosts have one-click import tools for this.
- Update the site configuration with the new server’s database connection details – the database name, your database username, and the host address. These will be different from your old server.
- Test everything before switching DNS – use the temporary URL or IP address provided by your new host to preview your site before it is live. Test pages, forms, checkout flows, and logged-in functionality. Most managed hosts provide a staging URL for this purpose.
- Lower your DNS TTL in advance – before migration day, reduce your domain’s DNS TTL to 300 seconds (5 minutes). This means when you point DNS to the new server, the change propagates globally within minutes rather than hours.
- Switch DNS to the new server – update your nameservers or A records to point to the new host’s IP address. With a low TTL, most visitors will be on the new server within 5-10 minutes.
- Verify after DNS propagation – check SSL certificate status, contact forms, payment processing, email delivery, and anything else that was working on the old server.
- Keep the old server running for 48 hours as a fallback. Most managed hosts allow you to keep the old plan active for a short period after migration. Only cancel the old account after you have confirmed everything is working correctly on the new host.
Common Hosting Mistakes
| Mistake | Consequence | The Fix |
|---|---|---|
| Staying on shared hosting too long | Slow site, lost conversions, poor SEO | Move to managed hosting once traffic exceeds 10K/month |
| Not using a CDN | Slow global load times | Add Cloudflare free tier at minimum |
| No staging environment | Updates break the live site | Use managed hosting with staging or set up manually |
| Choosing based on year-1 promo price | Renewal sticker shock | Always calculate total cost of ownership over 3 years |
| Server in wrong region | High latency for target audience | Choose server closest to majority of your visitors |
| No object caching | Database overloaded, slow TTFB | Enable Redis or Memcached object caching |
| Outdated PHP version | Security vulnerabilities, slower performance | Always use PHP 8.1+ for WordPress |
Series Navigation – Website Owner’s Toolkit
This post is part of the Website Owner’s Toolkit – a 21-part series covering every essential service and skill you need to run a professional website. View the full series index here.
- Previous in series: Part 1 – How to Pick the Perfect Domain Name and Protect It from Hijacking
- Next in series: Part 3 – Free vs Paid SSL Certificates: Do You Really Need to Pay for HTTPS?
- Part 11 – How to Make Your Website Faster with CDN, Caching, and Optimization
- Part 14 – The 3-2-1 Backup Strategy for Your Website
- Part 20 – Website Disaster Recovery Playbook
