Free tools Windows power users keep installed
One-click scans. No signup required.
There is no universal visitor limit for WordPress. A site’s practical ceiling is set mainly by how many requests must execute PHP and query the database at the same time. Anonymous pages delivered from a full-page cache can handle vastly more traffic than uncached, logged-in or WooCommerce requests on the same server.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
As a rough planning reference, vendor estimates range from about 10,000–30,000 cached pageviews per month on a 1 GB VPS with three PHP workers to 1–5 million mostly anonymous monthly pageviews on a well-tuned server using server-level caching and a CDN. Those are not guarantees. Your cache-hit rate, response time, worker count, memory, plugins and traffic pattern determine the real number.
| # | 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.
Recommended Free Tools
What actually determines WordPress capacity
“Visitors per month” is a poor capacity metric by itself. One visitor loading a cached article may create one inexpensive request. Another visitor browsing a logged-in account, adding products to a cart or triggering a search may create several uncached PHP requests and database queries.
Every uncached request occupies a PHP worker until it finishes. If the average uncached response takes 400 milliseconds and a host provides four workers, the theoretical throughput before requests queue is approximately 10 uncached requests per second:
#1 Best Overall
workers ÷ response time in seconds = 4 ÷ 0.4 = 10 requests per second
As the queue grows, response times rise and the server can return HTTP 503 errors. Worker exhaustion is a common reason WordPress sites fail during a traffic spike. Memory limits how many workers can run: a vendor estimate puts a typical WordPress request at roughly 40–80 MB per worker, so a 2 GB server might support about 20–25 workers after the operating system and database receive their share. The exact figure varies with PHP settings, plugins and query load.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Cache hits and cache misses are different workloads
A page cache can serve a previously generated HTML response without starting PHP. Server-level caches, including configurations built around LiteSpeed, can absorb high volumes of anonymous traffic in the same way. A high cache-hit rate therefore makes a modest server appear extremely powerful.
Cache misses still execute WordPress. They occur when a page is new or expired, when a visitor is logged in, or when a request is personalized, such as a cart, checkout, account page, dashboard or many search results. Capacity planning must measure the uncached portion rather than multiply total pageviews by a server’s advertised monthly number.
Rank #2
Useful traffic ranges—and why they are only estimates
The following figures come from hosting-industry guidance published in 2026. Treat them as rough planning ranges, not service-level guarantees or benchmarks performed on your site.
| Workload or setup | Published planning figure | Important qualification |
|---|---|---|
| 1 GB VPS, three PHP workers and page caching | About 10,000–30,000 pageviews per month | Vendor estimate; assumes a cacheable workload and does not establish a peak requests-per-second limit. |
| Up to 20,000 monthly visits | 2 vCPU and 2–4 GB RAM with page caching | Vendor tier estimate; plugin efficiency and cache rate can move the requirement substantially. |
| 20,000–100,000 monthly visits | 4 vCPU and 4–8 GB RAM with Redis | Vendor tier estimate; server-level caching and a current PHP version are also advised for this range. |
| More than 100,000 monthly visits | Add a CDN | Vendor tier estimate; a CDN reduces origin requests but cannot remove dynamic PHP or database work. |
| Mostly anonymous, cached traffic on one tuned server | About 1–5 million monthly pageviews | Vendor estimate; the guide’s attribution is not precise enough to treat this as a universal limit. |
Another 2026 hosting estimate says sites below 50,000 monthly visits generally work on a decent host with page caching. Between 50,000 and 500,000 visits, it considers server-level caching, a CDN and a current PHP version increasingly necessary. These ranges describe monthly totals, not a promise that a site can absorb a sudden viral burst.
Why logged-in sites and WooCommerce hit limits sooner
Logged-in and commerce pages usually bypass full-page caching because the response depends on the user, session or inventory state. A store can therefore consume PHP workers and database connections even when its public blog pages are cached.
One vendor estimate for a store receiving more than 50,000 visitors per day calls for at least 8 GB of RAM, 20 or more PHP workers and object caching. Consider that a planning starting point, not a minimum guaranteed specification. Product filters, checkout extensions, payment callbacks, stock updates, order emails and customer dashboards can each change the workload.
Rank #3
- Mostly anonymous publication: page-cache hit rate is usually the dominant variable.
- Membership or community site: logged-in requests, notifications and profile pages reduce the benefit of page caching.
- WooCommerce: cart, checkout, account and many API requests are dynamic; database and object-cache performance matter as much as CPU.
- Import, export or reporting jobs: a small number of long-running requests can occupy workers and cause 503 errors even with modest visitor counts.
Baseline software and memory requirements
WordPress.org’s requirements page recommends PHP 8.3 or later, MariaDB 10.11 or later or MySQL 8.0 or later, and HTTPS. The Make WordPress Hosting Handbook recommends PHP 8.4 or later for production and notes that WordPress 7.1 requires PHP 7.4 or later. Because these statements do not align perfectly, choose a host that supports a currently maintained PHP release and verify compatibility for your WordPress version and plugins before switching.
The Hosting Handbook gives these PHP memory tiers:
| Workload | PHP memory guidance |
|---|---|
| Vanilla WordPress | 128 MB minimum |
| Typical production site with several plugins | 256 MB recommended |
| WooCommerce, page builders, multilingual sites or import/export jobs | 512 MB or more |
These are per-request PHP memory allowances, not total server RAM. A host may cap memory_limit at runtime; the effective php.ini value is the real ceiling. WordPress also exposes WP_MEMORY_LIMIT (reported defaults of 40 MB, or 64 MB for Multisite) and WP_MAX_MEMORY_LIMIT (reported default 256 MB), but increasing a WordPress constant cannot override a lower host-level limit.
Apache HTTPD 2.4 and nginx are the common web servers named by the Hosting Handbook. Redis, Memcached and APCu are optional caching extensions. They can reduce repeated database or object work, but they do not compensate for inefficient queries, a slow plugin or insufficient CPU.
How to estimate your own ceiling
Use measurements from your production configuration instead of relying on a generic “visitors per server” claim.
Rank #4
- Measure cache-hit rate. Use your host, reverse proxy or cache-plugin logs to separate cached anonymous responses from cache misses. Record the rate during normal days and during your busiest periods.
- Measure uncached response time. Test representative uncached URLs under realistic load. Record the average and high-percentile response time; a fast average can hide a slow tail that ties up workers.
- Estimate workers. Use
workers needed ≈ uncached requests per second × uncached response time in seconds. For example, 6 uncached requests per second at 0.5 seconds each requires roughly three simultaneously occupied workers before safety headroom. - Check memory. Confirm that the planned worker count, database, web server and operating system fit in available RAM. If each worker consumes 60 MB and 20 workers are active, PHP alone could use about 1.2 GB before other services.
- Load-test safely. Run a staged test against a maintenance copy or a controlled production window. Increase concurrency gradually, monitor PHP workers, CPU, RAM, database connections, cache hit rate, latency and HTTP 5xx responses, and stop before the server becomes unavailable.
- Model the peak, not only the month. Convert your analytics into peak requests per second. A month with 100,000 visits may be easy if traffic is even, yet fail if a large share arrives during one news event.
Load testing beats blog estimates because it includes your theme, plugins, PHP version, database, cache rules and actual URL mix.
Choosing hosting for a higher-traffic WordPress site
Compare hosts on the components that determine dynamic capacity, not on an isolated “unlimited visitors” label.
Outdated 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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Capacity question | What to verify before buying or upgrading |
|---|---|
| Cache layer | Whether full-page caching, server-level caching and CDN integration are included; how logged-in, cart and API paths are excluded. |
| PHP workers | The number of concurrent workers, whether limits are per site or shared, and what happens when the limit is reached. |
| RAM and CPU | Dedicated or shared resources, available vCPU, memory ceiling and whether bursting is temporary or guaranteed. |
| PHP and database versions | Support for a maintained PHP release, MariaDB 10.11 or later or MySQL 8.0 or later, and a straightforward upgrade path. |
| Object caching | Redis, Memcached or APCu availability, persistence behavior and whether the service is shared with other customers. |
| Traffic pattern | Documented support for logged-in users, WooCommerce, background jobs, webhooks and sudden bursts—not just cached pageviews. |
| Observability and recovery | Access to access logs, PHP slow logs, resource graphs, staging, backups and a way to raise worker or memory limits. |
A CDN can serve static assets and cache eligible HTML near visitors, reducing origin bandwidth and request volume. It cannot make personalized responses cacheable or eliminate database work at checkout. Configure cache exclusions carefully: caching a cart, account page or administrative response can expose incorrect or private data.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Diagnosing a WordPress 503 during a traffic spike
A 503 means the server could not handle the request at that moment; it does not identify the root cause. Use this order of checks:
Best Value
- Check resource graphs and logs. Look for PHP worker saturation, RAM exhaustion, CPU throttling, database connection limits and repeated slow requests at the failure time.
- Separate cached and dynamic URLs. If cached articles load while checkout, search or logged-in pages fail, focus on PHP, database and object-cache capacity rather than CDN bandwidth.
- Inspect recent changes. Roll back a newly added plugin, theme release, import, scheduled job or expensive query if its timing matches the incident.
- Protect the origin. Enable or repair page and server-level caching, put static assets behind a CDN, and apply rate limits to abusive crawlers or expensive endpoints.
- Increase capacity deliberately. Add RAM or vCPU and raise PHP workers only when memory and database capacity support them. More workers on an undersized server can increase swapping and make failures worse.
- Retest after each change. Repeat the same load scenario and compare latency, worker utilization, cache-hit rate and 5xx responses.
Planning targets that are safer than a visitor promise
Set an operational target such as “99 percent of anonymous article requests are cached and peak uncached traffic stays below 60 percent of measured worker capacity.” Keep headroom for cache purges, plugin updates, crawlers, backups and traffic bursts. For a store, set separate targets for product pages, cart, checkout, account requests and background jobs because they have different costs.
Review capacity after major changes: adding a page builder, enabling multilingual content, installing search or filtering, launching membership features, changing PHP versions or introducing new payment and analytics integrations can alter memory use and response time without changing visitor numbers.
Bottom line
WordPress can handle anything from a few thousand monthly pageviews on a tiny cached VPS to millions of mostly anonymous pageviews on a tuned server with a CDN. The deciding figure is not total visitors; it is concurrent uncached work. Measure cache misses, response time, PHP workers and memory on your own stack, then load-test the peak workload. Treat published traffic tiers as orientation only, and plan logged-in and WooCommerce traffic separately because their capacity is normally much lower.
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.
