See the picks

Hosting limits, in plain words

PHP workers explained: the number that decides how many shoppers your store can serve at once

Every hosting plan hides one number that matters more than the storage size on the sales page: PHP workers. It decides how many shoppers your store can work on at the same moment. When a store feels fine at noon and falls over during a sale, this number is usually why.

A worker is a pair of hands

Picture your store as a shop with a small crew behind the counter. A PHP worker is one pair of hands. Each time a page has to be built fresh, one worker picks it up, does the work, and puts it down. A worker handles one job at a time. Two workers means two jobs at once. When a third fresh page arrives and both hands are busy, it waits in line.

Most pages never need a worker at all. A guest reading a product page usually gets a saved copy from the cache, the way a flyer gets handed out at the door. Workers get called for the work that cannot be pre-made: adding to cart, checking out, logging in, searching the store, and every screen in your admin.

Why stores feel this limit before blogs do

A blog's readers mostly read. A store's shoppers act. Every action, cart, coupon, checkout step, account page, runs through a worker. So a store with modest traffic can still run out of hands at the worst moment: a sale, an email blast, a payday rush, when twenty shoppers all reach checkout inside the same minute. Their pages queue. Queued pages feel like a frozen store, and some shoppers leave before a hand frees up.

The same queue explains a slow admin. When you open the orders page during a rush, your screen waits in the same line as your shoppers. Owners often blame the store or a plugin. Often it is arithmetic: more fresh work than hands.

The worker counts that matter here

Host and planPHP workersWhat the host itself says
Kinsta, entry plan ($35/mo)2Kinsta points stores to its 65,000-visit tier, with 4 workers, for ecommerce
Pressable, Signature 1 ($250/yr)5Sold as a WooCommerce plan from the start, with workers to match
WP Engine, entry plansNot publishedThe plan page does not print a worker count; ask before you buy

Checked November 19, 2026 on each host's own pages. A host that will not publish its worker count is not hiding a scandal, but the question is fair, and a good support chat will answer it in one message.

Read the Kinsta row slowly. Two workers is a thin crew for a store doing real checkout volume, and Kinsta's own guidance agrees: it steers stores to the tier with 4. That is a big part of why our comparison of the two prices Kinsta stores on the higher tier, and why the entry price on the sales page is not the price a busy store actually pays.

How to tell if your store is short on workers

Two fixes work, and both are cheaper than a redesign. Move up one tier, where the worker count rises with the visits. Or cut the fresh work itself: object caching (Redis) answers repeat database questions from memory, so each worker's job finishes faster and the line moves quicker. The right order is usually workers first, cache second, because a queue with too few hands stays a queue.

Questions owners ask about PHP workers

How many PHP workers does my store need?

There is no single right number, but there is a useful test: at your busiest minute, how many shoppers are doing something fresh at once, checking out, logging in, searching? You need at least that many workers, plus one for you in the admin. A quiet store runs fine on 2 to 4. A store with sale-day rushes should be looking at 4 or more, and at the host's own ecommerce tier rather than its entry plan.

Is a PHP worker the same as CPU or RAM?

No. CPU and RAM are the size of the workshop. Workers are the crew working in it. A big workshop with two people in it still serves two customers at a time. Plans advertise the workshop because the numbers look bigger. Ask about the crew.

Why does my host not list its worker count?

Some hosts manage the pool for you and treat the count as an internal detail. That can work fine in practice. But for a store, the count is the clearest sign of what a plan can handle at rush hour, so ask support directly and keep the answer. If a host will not say, price the plan as if the count is low.

Can plugins fix a worker shortage?

Plugins can reduce the work, and a good cache setup helps every worker finish faster. No plugin adds hands. When the line is the problem, the fix is a tier with more workers, or a host whose entry plans staff a bigger crew. Our comparison page reads each host on exactly that basis.