At-a-glance comparison
| Provider | Entry price (approx.) | Path to ~1M visits | CDN option | Best fit |
|---|---|---|---|---|
| Cloudways | $11/mo+ | Scale to 4–8 vCPU, 8–16 GB RAM; Redis + page cache | CloudwaysCDN or Cloudflare | Managed WordPress/PHP |
| DigitalOcean | $6/mo+ | 4–8 vCPU, 8–16 GB RAM; add load balancer if needed | Cloudflare, DO Spaces + CDN | DIY stacks, APIs |
| Vultr | $6/mo+ | High-performance plans for heavy PHP/Node | Cloudflare | Low-latency apps |
| Akamai (Linode) | $5/mo+ | Balanced CPU, 8–16 GB RAM; object cache | Akamai/Cloudflare | Steady growth sites |
| Hetzner Cloud | €5/mo+ | High-CPU instances; CDN for global reach | Cloudflare | EU-heavy traffic |
| OVHcloud | $7–10/mo+ | VPS to dedicated as traffic grows | Cloudflare | Media/API scale |
| Hostinger VPS | $5–7/mo+ | Mid-tier VPS + LiteSpeed cache | Hostinger CDN or Cloudflare | Budget WP/Woo |
Right-size your server for real traffic
“One million visits” can mean many things. A well-cached blog can serve that on a 4 vCPU box. A heavy store with no cache may need much more. Watch these signals:
- CPU stays above 70% for long periods
- RAM swaps often
- Time to first byte (TTFB) rises under load
- Queue of PHP workers stays full
Fast stack recipes you can copy
WordPress
- LiteSpeed or Nginx + FastCGI cache
- Redis Object Cache + page caching
- Image compression and WebP
- CDN for static and HTML edge cache if possible
Node.js or API
- PM2 or systemd, cluster mode
- Reverse proxy with Nginx
- Rate limit and cache hot endpoints
- Use a read replica for heavy DB reads
Static or Jamstack
- Build static pages
- Serve from a global CDN edge
- Add serverless only for dynamic bits
Simple test plan before you scale
- Run load tests with k6 or Loader.io
- Test cached and uncached paths
- Measure TTFB, error rate, and 95th percentile latency
- Raise users per second until errors rise, then add resources or more cache
Cost-saving tips that keep speed high
- Cache HTML at the edge when possible
- Move images and video to object storage with a CDN
- Use HTTP/2 or HTTP/3 and gzip or Brotli
- Trim plugins and heavy scripts
- Back up offsite and monitor with alerts
Pick a host that fits your stack, turn on caching, and add a CDN. Start small, test hard, and scale only when the data says so. That is how you serve a million visits without breaking the bank.
