What "unlimited" really means
Sales pages promise unlimited sites, bandwidth and visitors. The server still has limits, and they decide how your site copes when it gets busy. These are the limits we measure on our own test site on each plan.
| Host · plan we test | PHP workers | Visitors at once | Memory | Run time | Upload | CPUs | Object cache | Blocklisted, 90 days |
|---|---|---|---|---|---|---|---|---|
| Hostinger Premium | — | — | — | — | — | — | — | — |
| Bluehost Starter | — | — | — | — | — | — | — | — |
| SiteGround StartUp | — | — | — | — | — | — | — | — |
| DreamHost Web Hosting Launch | — | — | — | — | — | — | — | — |
| Namecheap Stellar | — | — | — | — | — | — | — | — |
| Kinsta Single 20GB | — | — | — | — | — | — | — | — |
| WP Engine Essential | — | — | — | — | — | — | — | — |
| Cloudways Flexible Small (2 GB) | — | — | — | — | — | — | — | — |
What each limit means for your site
PHP workers are how many pages the server can build at the same moment. A cached page doesn't need one, but a shop's cart, a search, a logged-in visitor or the WordPress admin does. When they're all busy, the next visitor waits in a queue. Two workers are plenty for a blog; a busy shop wants more.
Visitors at once comes from our monthly load test on the uncached page: the most simultaneous visitors with 95% of pages built in under a second. Ordinary cached pages can go much higher.
Memory per request limits heavy plugins and page builders; WordPress itself needs about 64 MB, and many page builders ask for 256 MB. Run time caps how long one request may take, which matters for imports, backups and updates. Upload is the largest file you can upload through WordPress.
Object cache (Redis or Memcached) keeps database results in memory, which speeds up logged-in and uncached pages. Email blocklist days show how often the server's shared sending address was listed as a spam source; when it is, your site's emails are more likely to land in spam.
How we measure each one: methodology.