Most advice about high traffic WordPress hosting starts with a monthly pageview number. That number is close to useless. A site doing two million cached pageviews a month can run happily on a small VPS. A membership site doing a tenth of that, with every visitor logged in, will bring a shared plan to its knees. What decides whether your hosting is big enough isn’t traffic volume. It’s how much of that traffic is uncached, and how much of it arrives at once.
This guide covers what breaks first on a busy WordPress site, what the server actually needs, and when the honest answer is “move it to a dedicated server”. We sell dedicated servers, so read with that in mind. We’ll also say when a dedicated box is overkill.
What “high traffic” means to a server
A web server doesn’t experience monthly pageviews. It experiences concurrent requests. Ten thousand visitors spread evenly over a day is about seven requests a minute, which almost anything can serve. The same ten thousand arriving in the hour after a newsletter or a product drop is a different workload entirely.
Then there’s the split between cached and uncached requests. A page cache (a plugin, a server-level cache, or a CDN) turns a WordPress page into a static file that costs almost nothing to serve. Generating a page costs a PHP worker for anywhere from 50 milliseconds to a couple of seconds, plus a stack of MySQL queries. The cache only helps when the page is the same for everyone. It can’t help with:
- Logged-in users: members, subscribers, students, forum regulars, anyone with a WordPress cookie.
- WooCommerce cart, checkout and account pages, which are per-shopper by design.
- Site search, filtered archives and anything with a query string the cache was told to ignore.
- Admin traffic, including editors publishing and cron jobs firing.
- The first request after any cache purge, which happens every time you publish.
So the question is simple: of the requests arriving in your busiest ten minutes, how many are uncached, and how many PHP workers do you have to serve them? When those numbers get close, you’re on the edge. When the first is bigger, you’re already seeing symptoms.
What breaks first, and in what order
Busy WordPress sites fail in a predictable sequence.
1. PHP workers run out
Every uncached request occupies a PHP-FPM worker until the page is built. Shared hosting caps you at a handful of concurrent processes; small VPS plans aren’t much better because RAM limits how many workers you can run. When the workers are all busy, new requests queue. Queue long enough and the web server gives up, which is where the 504 gateway timeout comes from. If you see 503s and 504s only during spikes, this is almost certainly your problem.
2. MySQL becomes the wall
Add more workers and the next thing to saturate is the database. WordPress is query-heavy, plugins make it worse, and WooCommerce makes it worse again. On shared hosting the database lives on a shared MySQL server with per-account connection limits. On a small VPS it shares RAM with PHP, so the InnoDB buffer pool is tiny and every query hits disk. Symptoms: slow admin, slow search, checkout timing out, “error establishing a database connection” under load.
3. Disk and memory
Once CPU and database are sized properly, the remaining limits are disk I/O (large media libraries, backups running during peak) and RAM (object cache, buffer pool and PHP workers all want it). Both are easy to fix on hardware you control and hard to fix on a plan where someone else sets the limits.
If your site is slow all the time, not just under load, the cause is probably elsewhere. Our post on why websites are slow covers the theme, plugin and front-end causes that hardware won’t fix.
WordPress server requirements for a busy site
WordPress.org’s published minimums describe a site with no visitors. For a site with real traffic, these are the things that matter.
| Resource | What it does for WordPress | What to look for on a busy site |
|---|---|---|
| CPU cores | Each PHP worker needs a core to run on; MySQL needs its own share | Enough cores to run as many PHP workers as your peak uncached concurrency, with headroom for the database |
| RAM | PHP workers, the MySQL buffer pool and an object cache (Redis or Memcached) all live here | Enough to hold your whole database in the buffer pool plus 50 to 100 MB per PHP worker |
| Storage | Media library, database files, backups, logs | SSD or NVMe. Spinning disks are the wrong answer for a database |
| Network | Serving images and files, especially without a CDN | Unmetered or generously metered. Overage bills during your best month are a bad surprise |
| Isolation | Whether other tenants can take your resources | Single tenant if your traffic is spiky or uncached |
The honest answer to “how much CPU and RAM” is “measure your peak”. Check your PHP-FPM status page or resource graphs during the last spike, count uncached requests per second, and size from there. If you can’t see those numbers on your current plan, that’s a sign in itself.
Shared, VPS or dedicated: where each one stops
Here is how the three hosting types behave against the failure sequence above. We’re comparing the type, not any particular vendor.
| Shared hosting | VPS | Dedicated server | |
|---|---|---|---|
| PHP workers | Capped per account, usually single digits | Limited by the RAM you bought | Limited by the physical cores and RAM, which you chose |
| Database | Shared MySQL server, connection limits | Your own MySQL, small buffer pool | Your own MySQL, buffer pool sized to the catalog |
| Spikes | Throttled or suspended | Handled until the slice is full; neighbors can still interfere | Handled until the hardware is full; no neighbors |
| Caching control | Whatever the host allows | Full, with root | Full, with root |
| Good up to | Small, mostly anonymous sites | Mid-size sites with a high cache hit rate | Busy sites, logged-in audiences, stores, agency portfolios |
A VPS is the right call more often than hosts like us would like to admit. If 95% of your traffic is anonymous and cached, a VPS with a decent cache layer will take you a long way. Our piece on WordPress on a VPS versus a dedicated server covers when each wins.
When a dedicated server is the right call
Move to a dedicated server when one or more of these is true.
- A large share of your traffic is logged in. Membership sites, LMS platforms, communities, publishers with paywalls. Cache can’t save you, so you need the CPU.
- You sell things. WooCommerce checkout is uncached, database-heavy and the worst possible place to fail. Our WooCommerce hosting on a dedicated server page covers the store-specific mechanics.
- You host many sites. Agencies with dozens of client sites, or a multisite network, where one site’s spike shouldn’t take the rest down.
- Your spikes are big and unpredictable. Press mentions, product drops, viral posts. You want hardware that’s yours during the hour that matters, not a slice that a neighbor can squeeze.
- You’ve been throttled. Resource-limit emails, CPU throttling, entry-process limits and 503s during campaigns are your host telling you the plan is done.
At GigeNET a WordPress dedicated server on an Intel Xeon starts at $126/mo with $0 setup and month-to-month billing. Every server includes 4 Gbps of DDoS protection and R1Soft backups with 1 TB of space. The Xeon D-1541 Special at $159/mo adds 1 Gbps unmetered bandwidth in any of our three regions (Chicago, Ashburn, Los Angeles), which matters if you serve a lot of images without a CDN. In-stock builds are delivered the same or next day.
What “managed” should and shouldn’t mean
High traffic hosting pitches use the word managed in two different ways, and it pays to know which one you’re buying.
Managed WordPress hosting means the host controls the stack and the WordPress install, and you get what they chose. That’s fine until you need a PHP setting they don’t expose, or you exceed the visit tier they bill on.
A managed dedicated server means the host runs the hardware and the operating system and you run the application. That’s what our Enterprise Server Management plan is: $99/mo (or $79/mo on a server with a cPanel license), covering OS patching and advanced monitoring, with US-based engineers on tickets and phone 24/7. WordPress core, plugins, themes and caching plugins are yours or your developer’s. We say that plainly because plenty of hosts don’t, and the gap usually shows up during an outage.
For a busy site with a developer or agency behind it, the second model is normally the better fit. You keep the layer that makes your site yours and hand off the layer nobody enjoys at 3 a.m.
Before you buy
Pull your peak uncached requests per second from the last two spikes, count logged-in sessions in that window, note your database size on disk (that’s the buffer pool you want in RAM), and pick the region closest to your readers. Send those answers in the quote form and we’ll come back with a build and a price. If the answer is “a VPS would do”, we’ll tell you that too.
FAQ
How much traffic can a WordPress site handle on shared hosting?
Far more cached traffic than most people expect and far less uncached traffic. A well-cached brochure site can serve hundreds of thousands of pageviews a month on shared hosting. A membership site with a few hundred logged-in users online at once will hit PHP process limits on the same plan.
Is a dedicated server faster than a VPS for WordPress?
For cached pages, barely. For uncached pages under load, yes, because you have more cores and RAM to put behind PHP and MySQL, and no neighbors competing for the physical host. If your bottleneck is a slow theme or plugin, neither will fix it.
Do I still need a CDN and caching on a dedicated server?
Yes. Caching and a CDN reduce the work the server does; a dedicated server increases how much work it can do. Use both. The server is for the requests that can’t be cached.
Does GigeNET set up WordPress on the server?
Our engineers manage the server and operating system. You or your developer install and run WordPress, plugins and caching. If you need more than that, ask in the quote form and we’ll say whether we can do it and quote it.
What does a high traffic WordPress dedicated server cost?
Entry Intel Xeon builds at GigeNET start at $126/mo with $0 setup, month to month. Add $99/mo for server and OS management ($79/mo with a cPanel license) and $49.50/mo for cPanel/WHM if you want it. DDoS protection and 1 TB of R1Soft backups are included.