Hosting is the one purchase where the brochure and the bill describe different products. A plan sold as unlimited usually has a CPU limit, and a plan sold as fast usually means fast for a nearly empty site.
We tested a typical content site across three tiers: shared hosting, an unmanaged VPS and a managed WordPress plan. Same theme, same plugins, same database size. The results explain why so many launches go wrong at exactly the wrong moment.
What each tier is really selling
Shared hosting sells a slice of a server. You get disk, a database and a control panel, but CPU, memory and entry processes are shared with neighbours. It is the cheapest way to run a small site and the first thing to fail when a post gets picked up by a large newsletter.
A VPS sells a fixed slice of CPU and memory. You control the operating system, the web server and the database, which means you also own the patching, backups and security. It is excellent value if you have the skills, and a liability if you do not.
Managed WordPress sells operations rather than raw capacity. The host handles updates, caching, staging and often a CDN, and charges accordingly. The trade is money for attention, and the quality of that attention varies enormously between providers.
The numbers that force an upgrade
For a cached content site, shared hosting can usually serve a few thousand visits a day without complaint. The danger is not total traffic but concurrency: fifty people hitting an uncached page at once is a harder test than five thousand people reading a cached one over a day.
Dynamic sites with logged-in users, search or a shop hit limits much sooner. Every uncached request consumes PHP workers, and most shared plans cap those at a handful. When the cap is reached, requests queue, then time out. The site is not down, which makes the outage harder to explain to a client.
A VPS with two cores and 4 GB of memory will handle a well-cached WordPress site through most launch spikes. The constraint moves to the database and to whatever else you installed on the same box. Managed plans typically add edge caching and request-level protection, which is why they survive traffic a raw VPS of the same size would not.
How to test before you migrate
Ask the host three questions in writing. What is the CPU and memory limit per request? What happens when I hit it: throttling, a 503, or an overage bill? How many concurrent PHP workers do I get? A provider that cannot answer clearly is telling you something useful.
Then run a load test against a staging copy with caching disabled, because that is the state a logged-in editor or a comment form creates. Tools such as k6 or Locust can simulate fifty concurrent users without much setup. Watch time to first byte and error rate, not just requests per second.
The right hosting plan is the cheapest one that stays boring on your worst traffic day, not the fastest one on your empty staging site.
Key facts
- Shared hosting limits CPU, memory and concurrent PHP workers.
- Cached traffic is easy; concurrency and logged-in users are the real test.
- A 2-core, 4 GB VPS handles most small-site spikes if well cached.
- Ask what happens at the limit before you sign a yearly contract.
- Load-test with caching off to see the worst case.
When managed hosting earns its premium
Managed WordPress makes sense when your time is worth more than the difference in price, or when nobody on the team wants to own server security. It also makes sense for client sites where a 3 a.m. recovery is part of the service you sold. The premium is insurance with a support queue attached.
It stops making sense when the plan's visitor cap is lower than your normal month, or when the host's idea of support is a knowledge base. Read the renewal price, not the introductory one. Hosting companies compete on the first invoice and make their margin on the second.
A practical decision path
Start on shared hosting if you are launching a brochure site with fewer than a thousand daily visits and no login. Move to managed WordPress when you need staging, automatic backups and someone else to call. Choose an unmanaged VPS only if you can patch, monitor and restore without help, or if you have a developer who can.
Whichever tier you pick, put a CDN in front of it and cache aggressively. That single step does more for a small budget than doubling the server size. For the performance work that happens after hosting, read our Wi-Fi 7 field test; for analytics that tell you whether the upgrade worked, see cookieless measurement.
Bottom line
Buy for your worst concurrency, not your average pageview. Test the limit, read the renewal price and keep a migration path open. Hosting should be a utility you stop thinking about, not a monthly argument about why the site is slow.
