PHP Workers Explained: How Many Does Your Site Need?

PHP Workers Explained: How Many Does Your Site Need?

Some links on this page are affiliate links. If you buy through one, we may earn a commission at no extra cost to you. It never changes a recommendation. How this works.

A PHP worker is a server process that builds one uncached WordPress page at a time, so your worker count is how many uncached requests your site can handle at once. As of October 2026, Kinsta’s entry plans include 2 (it calls them PHP threads), Hostinger lists 40 to 100 by plan, Cloudways lists 100 per server on its Autonomous plans, and WP Engine and Liquid Web don’t publish a base count.

This guide is based on each host’s published plans, documentation and terms, checked in October 2026; it does not include our own tests.

What a PHP worker actually does

When a request hits your site, one of two things happens. If the page is in cache, the server hands back a pre-built copy, with no worker involved. If it isn’t cached (a logged-in user, a cart, a checkout, a search, a REST or admin-ajax call), a worker picks it up, loads WordPress, runs your theme and every active plugin, queries the database, assembles the HTML, and only then frees up for the next request. Kinsta’s PHP docs put it plainly: each thread “processes one request at a time,” and “cached content doesn’t require PHP threads.”

Think supermarket checkout lanes. Cached pages are the grab-and-go shelf by the door; everything else goes through a lane, and your worker count is how many lanes are open. With two workers, the third uncached request waits in line, no matter how powerful the rest of the server is.

How many PHP workers do you need?

Start with arithmetic. A worker that spends 1 second on an uncached request finishes at most one request per second; at 500 milliseconds, two. So at your busiest moment you need about your uncached requests per second multiplied by your average PHP response time in seconds, plus headroom. The real question is how much of your traffic bypasses the cache.

  • Brochure site or blog with full-page caching. Most pageviews come from cache. Cloudways’ PHP workers guide suggests 2 to 4 workers for a static site.
  • Busy blog with search, comments and logged-in authors. More requests skip the cache, so run the multiplication on your busiest hour.
  • WooCommerce, membership or LMS site. Kinsta’s pricing page recommends 4 or more PHP threads, and Cloudways calls 4 “a good starting point.” Cart, checkout and account pages bypass cache by design.
  • Busy store at sale time. Work from your peak: 6 uncached requests a second at 0.8 seconds each keep about 5 workers busy (6 × 0.8 = 4.8), before headroom.

The multiplication that trips people up: worker capacity and code speed are the same lever. Four workers at a 1-second average response clear about 4 uncached requests per second, or 14,400 an hour. Let a slow plugin drag the average to 3 seconds and those same four workers clear about 1.3 per second. Your capacity just fell by two-thirds, and you didn’t change plans.

PHP worker limits by host

Here is what each host publishes on its own pages as of October 2026.

Workers on entry planHow you get moreWhat happens at the limit
Kinsta2 on Single 35k ($35 a month); 4 on Single 65k ($50)Bigger plan, or the prorated PHP performance add-on ($10 per 500MB a month)Requests wait; Kinsta warns of timeouts and 503 or 504 errors, and MyKinsta charts how often the limit is hit
WP EngineNot published ($35 a month, or $28 for the first year billed annually)Not published; its 504 guide says to contact your account managerQueued requests are evicted with a 504; requests past 60 seconds are killed with a 502
Liquid WebManaged WordPress: not published. VPS: whatever you configureElite autoscales up to 40 on the largest plans (first 24 hours a month included); on a VPS you tune PHP-FPMManaged WordPress: not published. VPS: CPU and RAM set the ceiling
CloudwaysFlexible: not published. Autonomous (from $99 a month): 100 per serverFlexible: a bigger server. Autonomous: autoscaling adds serversNot published
Hostinger40 on Premium ($2.99 a month on a 48-month prepay, renewing at $10.99)Unlimited (60) or Cloud Startup (100)Not published

Notice the split. Kinsta and Hostinger publish a fixed count per plan (see our Hostinger review), and Kinsta lets you trade memory per thread for more threads. WP Engine and Liquid Web’s managed platform publish no base count, though Liquid Web‘s Elite tier adds workers during a surge. On a Liquid Web VPS or a Cloudways Flexible server you buy CPU and RAM, and Cloudways’ guide ties useful worker counts to CPU cores (a 2023 Cloudways post claims “up to 6000 PHP workers per site”; its pricing page gives no figure). That split is much of the argument in our Liquid Web vs Kinsta comparison.

Why too few workers causes 504 errors

The failure mode is a queue, not a crash. When every worker is busy, new uncached requests wait. Kinsta’s thread guidance for stores says that once requests outnumber threads, “the queue starts to reject new requests which could result in 502/504 errors.” WP Engine’s 504 guide is specific: when the workers and backlog are full, the oldest waiting requests are evicted with a 504, and requests still running after 60 seconds are cut off with a 502. On a plain nginx server, the default fastcgi_read_timeout is 60 seconds, so a request that waits longer for PHP ends in a 504.

The signature: errors arrive in bursts under load, CPU can look normal, and dynamic pages fail first, so checkout breaks while the cached homepage loads. Common triggers are a sale or email blast landing at once, bots crawling uncacheable search and filter URLs, wp-cron pile-ups, and slow external calls, like a payment gateway, holding workers open. Confirm it in your host’s dashboard (MyKinsta has a PHP thread limit chart) or look for “upstream timed out” in the error log.

How to need fewer workers

Before you pay for more workers, make the ones you have finish faster. Halve your average response time and the same workers handle twice the uncached requests.

  • Get full-page caching right. Audit what’s excluded. A rule that skips every URL with a query string can make all your UTM-tagged campaign traffic uncacheable.
  • Add object caching. Kinsta’s PHP performance docs say Redis can “reduce the need for PHP threads.” Liquid Web includes Object Cache Pro on every managed WordPress plan, Cloudways includes it free on 4GB servers and up, and Kinsta charges $100 per site a month for Redis.
  • Hunt slow plugins and queries. Query Monitor or your host’s APM tool will name the offender. One slow plugin taxes every uncached request.
  • Move wp-cron to a real cron job. WordPress checks scheduled tasks on every page load, per its developer docs, which show how to hand that to the system scheduler.
  • Rate-limit the bots. Crawlers love faceted search and add-to-cart URLs, which can’t be cached and earn nothing. WP Engine already queues known bots behind real visitors.

More workers, or a different host?

On a host with fixed counts, price the next plan before you stack add-ons. At Kinsta, moving from Single 35k (2 threads) to Single 65k (4 threads) costs $15 a month more. The PHP performance add-on is prorated, so it suits a sale weekend; if it becomes permanent, compare it with the plan above. A resource-based server drops the fixed count but makes capacity your job. That trade-off, managed guardrails versus raw headroom, is the honest version of the is managed WordPress hosting worth it question, and for stores our best WooCommerce hosting for small stores guide covers where the line falls.

For Kinsta against WP Engine, see Kinsta vs WP Engine; workers are only one line in that fight.

Frequently asked questions

What are PHP workers in WordPress?

PHP workers are the server processes that build uncached WordPress pages. Each handles one request at a time: loading WordPress, running plugins, querying the database and returning HTML. Your worker count is the number of uncached requests your site can process at once.

How many PHP workers do I need for WooCommerce?

Kinsta recommends 4 or more PHP threads for ecommerce, membership and LMS sites, and Cloudways calls 4 a good starting point. Busy stores need more: multiply your peak uncached requests per second by your average response time in seconds, then add headroom.

Do PHP workers matter if I use a caching plugin?

Less, but they still matter. Caching removes most anonymous pageviews from the worker pool, which is why a well-cached blog can run on a 2-worker entry plan. Logged-in users, carts, checkouts, search and API calls still bypass the cache.

Can too few PHP workers cause 504 errors?

Yes. When all workers are busy, new requests queue, and Kinsta and WP Engine both document 502 and 504 errors when that queue overflows or waits too long. The tell: errors on uncached pages during traffic spikes while cached pages still load.

Does adding more PHP workers make my site faster?

Not directly. Kinsta’s docs say “more PHP threads do not automatically mean better performance.” Workers add concurrency: a page takes as long to build with 2 workers as with 10. More workers stop requests from queueing; if pages are slow with no traffic, fix the code and the caching.

Want the guided version? Our free video courses are in production, starting with “Launch Your First Website with Claude.”

Last checked: October 2026. Prices and plans change; check the vendor’s page before you buy.