Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →There is no single visitor limit for WordPress. A site’s capacity is set mainly by how many requests bypass the cache, how long those PHP requests run, how many PHP workers and how much memory the server has, and whether visitors are logged in or checking out. A small, well-cached site can serve more anonymous pageviews than a much larger site whose pages are generated for every request.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
For planning, treat published traffic tiers as rough starting points rather than guarantees. Measure your own cache-hit rate, uncached response time, worker usage and memory under load. Those figures tell you when your WordPress site will queue requests, return 503 errors or need a larger architecture.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress For Dummies (For Dummies (Computer/Tech)) | $16.59 | Buy on Amazon |
| 2 |
|
WordPress All-in-One For Dummies | $25.40 | Buy on Amazon |
| 3 |
|
Wordpress for Dummies | $26.94 | Buy on Amazon |
| 4 |
|
WordPress Web Design For Dummies | $16.48 | Buy on Amazon |
| 5 |
|
WordPress Web Design For Dummies | $29.30 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat “traffic” means for WordPress capacity
Analytics usually report visitors, sessions and pageviews. Your server experiences HTTP requests, and those requests do not all cost the same amount. A cached article may be delivered without starting PHP or querying the database. A logged-in dashboard, shopping-cart page or uncached search result normally has to run WordPress code and occupy a PHP worker until it finishes.
That distinction explains why two sites with the same monthly pageviews can require radically different hosting. A video-game news site with thousands of anonymous readers opening cached stories has a very different workload from a membership site where every reader receives a personalized page.
#1 Best Overall
- Anonymous, cacheable requests: usually served by a page cache, server cache or CDN and largely kept away from PHP.
- Uncached requests: execute PHP, use database connections and consume a worker for the duration of the response.
- Logged-in and commerce requests: commonly bypass full-page caching because the response contains user-specific data, cart contents or account information.
The capacity equation: PHP workers and response time
Every uncached request occupies one PHP worker until it completes. A simple planning approximation is:
Workers needed ≈ uncached requests per second × average uncached response time in seconds.
For example, if four workers each handle a request that takes an average of 400 milliseconds (0.4 seconds), the theoretical throughput is about 10 uncached requests per second: 4 ÷ 0.4. Once arrivals exceed that rate, requests wait in a queue. As the queue grows, response times increase and the host may eventually return HTTP 503 errors.
This is a ceiling for the measured workload, not a promise that every WordPress installation will achieve it. Slow database queries, external API calls, plugin code, disk latency and uneven traffic bursts can reduce practical throughput. Averages also hide long-running requests; a small number of very slow operations can tie up workers while fast requests wait.
Why memory controls the worker count
RAM limits how many PHP workers can run safely. Hosting estimates commonly put a WordPress request at roughly 40–80 MB per worker. On a 2 GB server, that arithmetic might suggest 20–25 workers after the operating system and database receive their share. The estimate is workload-dependent: a page builder, image-processing job or import can use considerably more memory than a simple cached article.
Rank #2
Adding workers without reserving memory can make a site less stable. When RAM is exhausted, the operating system may swap or terminate processes, making response times and error rates worse. Size the worker pool together with available memory, database usage and the host’s runtime memory_limit, rather than choosing a worker number in isolation.
Page caching is the biggest capacity multiplier
A full-page cache stores the generated HTML for an anonymous URL. Subsequent readers can receive that file from the cache layer without running PHP. Server-level caches can perform the same job closer to the web server, and a CDN can serve cached assets or pages from edge locations. Cached delivery therefore avoids the PHP-worker ceiling that governs uncached traffic.
Cache effectiveness is measured by the cache-hit rate: the percentage of requests served from cache instead of reaching the application. A site receiving 100 requests per second with a 95% hit rate sends only about five requests per second to PHP. At a 50% hit rate, the same audience creates ten times as many dynamic requests. Purges, personalized cookies, query strings and cache exclusions can all reduce the hit rate.
Cacheable content must be designed deliberately. News posts, guides and patch-note pages are usually good candidates. Account pages, comment forms, carts and checkout pages need exclusions or private caching. A high headline pageview count can look harmless while a small logged-in feature consumes every worker.
Published traffic tiers—and their limits
The following figures come from hosting-industry planning guides published in 2026. They are estimates under stated configurations, not independent benchmarks or WordPress limits. Use them to frame a test plan, not to select a host solely by monthly visitor count.
Rank #3
| Workload or configuration | Indicative capacity | Qualification |
|---|---|---|
| 1 GB VPS, three PHP workers and page caching | About 10,000–30,000 pageviews per month | Priority Pixels estimate; assumes a cacheable workload and is not a guarantee. |
| Up to 20,000 monthly visits | 2 vCPU and 2–4 GB RAM with page caching | WebVibo planning tier; actual capacity depends on request cost and traffic bursts. |
| 20,000–100,000 monthly visits | 4 vCPU and 4–8 GB RAM with Redis | WebVibo planning tier; requires effective caching and a suitable object-cache setup. |
| More than 100,000 monthly visits | Add a CDN to the architecture | WebVibo recommendation, not a fixed server limit. |
| Mostly anonymous traffic on one tuned server | Roughly 1–5 million monthly pageviews | WebVibo estimate for server-level caching plus a CDN; logged-in traffic reaches limits much sooner. |
Another 2026 hosting guide places sites below 50,000 monthly visits on ordinary capable hosting when page caching is configured. It suggests server-level caching, a CDN and a current PHP release as traffic approaches 50,000–500,000 visits. These ranges overlap but are not directly comparable: one source describes visits, another pageviews, and each assumes different cache behavior and request complexity.
The absence of a primary WordPress.org or standards-body page that publishes a pageviews-per-server limit is important. WordPress is software that runs on many combinations of web server, PHP, database, plugins and infrastructure; it does not impose one universal traffic ceiling.
Logged-in users and WooCommerce have a lower ceiling
Full-page caching normally cannot serve a single shared response to a logged-in user. Membership features, personalized feeds, comment submission, account pages and shopping carts therefore send more work to PHP and the database. A site can appear comfortable during an anonymous news spike and fail as soon as a large audience signs in.
For WooCommerce, one 2026 hosting estimate quotes at least 8 GB of RAM, 20 or more PHP workers and object caching for a store handling more than 50,000 daily visitors. Treat that as a rough sizing example, not a required specification for every store. Product filters, payment callbacks, inventory operations and third-party integrations can make a smaller audience equally demanding.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Baseline software and memory requirements
WordPress.org’s requirements page recommends PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.0 or newer, and HTTPS. The Make WordPress Hosting Handbook recommends PHP 8.4 or later for production. The same handbook notes that WordPress 7.1 requires PHP 7.4 or later, which is a compatibility floor rather than a recommendation to run an old PHP release. Check the current requirements for your installed WordPress version and plugins before upgrading.
Rank #4
The Hosting Handbook gives these memory tiers:
- 128 MB: minimum for a basic, vanilla WordPress installation.
- 256 MB: recommended for a typical production site with several plugins.
- 512 MB or more: appropriate for WooCommerce, page builders, multilingual sites and import/export workloads.
Apache HTTP Server 2.4 and nginx are the handbook’s common web-server choices. Redis, Memcached and APCu are optional caching extensions; they are useful only when configured for the workload and supported by the host.
Developer-documentation excerpts report WP_MEMORY_LIMIT defaults of 40 MB (64 MB for Multisite) and WP_MAX_MEMORY_LIMIT of 256 MB. These WordPress constants do not override a lower PHP runtime ceiling: the host’s memory_limit in effect for the web process is the real cap. Confirm the values in current documentation and in your hosting environment before changing them.
How to calculate a realistic limit for your site
- Separate cached and dynamic URLs. List article pages, archives and media pages that can be public and cacheable. Mark account, search, preview, comment, cart and checkout routes as dynamic.
- Measure cache-hit rate. Use your host’s cache statistics or cache-plugin logs. Record the rate during normal days and during a promotion or breaking-news spike; a single monthly average can hide purge storms.
- Measure uncached response time. Capture average and high-percentile server response time under representative load. Test logged-in and commerce paths separately from anonymous articles.
- Estimate worker demand. Convert uncached requests to requests per second and multiply by response time in seconds. For instance, 1,000 uncached requests per minute equals about 16.7 per second; at 0.4 seconds each, the approximation is 6.7 busy workers before headroom.
- Check memory per worker. Observe the PHP process size and database memory while the test runs. Ensure the planned worker count leaves room for the operating system, web server and database.
- Load-test before a major event. Reproduce realistic URLs, cookies and login states. Increase concurrency gradually until latency or errors rise, then record the sustainable rate below that knee in the curve.
Load testing beats a generic “visitors per month” promise because it measures your theme, plugins, database, cache rules and content mix. Keep a safety margin for bursts rather than operating continuously at the first error threshold.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Scaling choices as traffic grows
Improve cache coverage first
Fix cache exclusions that are not required, reduce unnecessary purges and make sure static images, scripts and styles are cacheable. A CDN can absorb repeat delivery of public pages and large assets, reducing origin bandwidth and request volume.
Reduce the cost of each dynamic request
Find slow plugins, expensive database queries and remote API calls. Remove unused extensions, update PHP and WordPress components, and ensure database indexes and object caching are appropriate. Optimization is often safer than simply raising concurrency.
Best Value
Add capacity with evidence
Increase RAM when workers are memory-bound, add CPU when PHP execution is the bottleneck, and tune the database when queries queue there. Redis or another object cache helps repeated database reads but does not replace a full-page cache for anonymous content. For sustained high volume, separate the database or application tier only when monitoring shows that one component is limiting throughput.
Diagnosing WordPress 503 errors during a spike
- Check PHP-worker saturation: a full worker pool and rising queue commonly indicate that uncached requests are arriving faster than they finish.
- Check memory pressure: review RAM, swap and process kills before adding workers.
- Check cache status: a purge, cookie rule or cache bypass can suddenly turn public pages into dynamic requests.
- Check slow operations: disable or optimize the plugin, query or external call that holds workers longest.
- Check traffic type: separate anonymous pageviews from logins, searches, carts, checkout and API traffic.
- Retest after each change: confirm that latency, error rate and memory remain stable under the same load pattern.
Increasing PHP workers can clear a short queue only when sufficient RAM and database capacity remain. If the server is already memory-constrained, it can intensify failures. A CDN and stronger page-cache policy address a different problem: they prevent eligible requests from reaching PHP at all.
Free tools Windows power users keep installed
One-click scans. No signup required.
A practical target for a video-game site
For a gaming publication, start by classifying breaking-news stories, reviews, guides and patch notes as public cacheable content. Expect traffic spikes when a trailer, console update or major release lands, and test cache purges because editors often invalidate many URLs at once. Keep search, comments, user profiles, newsletter preferences and any members-only features dynamic.
Track at least cache-hit rate, uncached requests per second, PHP-worker utilization, response-time percentiles, database CPU and memory, and HTTP 5xx responses. Set alerts before workers remain saturated or RAM approaches the host limit. Re-run the load test after adding a plugin, changing the theme or introducing a new interactive feature; capacity is a property of the whole stack, not WordPress core alone.
Frequently Asked Questions
Does WordPress publish a maximum number of visitors?
No. WordPress.org publishes software and environment requirements, but no primary WordPress source sets a universal pageview or visitor ceiling. The limit comes from your infrastructure and workload.
Why can a site with fewer visitors need a larger server?
Visitor counts do not show how many requests bypass caching, how long PHP runs, whether users are logged in, or how much memory each request consumes. A dynamic store or membership site can therefore outgrow a heavily cached publication with a larger audience.
Recommended Free Tools
Should I add PHP workers whenever I see 503 errors?
Only after checking memory and database headroom. More workers help when requests are waiting and enough RAM is available; on a memory-bound server they can increase swapping and make 503 errors worse.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
