PHP Workers Explained for WordPress Hosting
PHP workers process uncached PHP requests. They matter most when many dynamic requests need to run concurrently.
PHP workers matter more for dynamic work than cached HTML
A CDN can serve cached assets quickly, but checkout, account areas, search, admin requests, APIs, and other uncached paths may still need PHP execution.
What to compare
- Published worker limit
- CPU/RAM available to those workers
- Queueing under load
- Object/page caching
- Autoscaling or upgrade path
- Workload concurrency
Common mistakes
- Treating worker count as a universal speed score
- Ignoring database bottlenecks
- Comparing worker numbers across different architectures as if they were identical
How to use this in a hosting decision
Turn the concept into a requirement. Write down what your site actually needs today, what could change over the next year, and which limits would create a forced upgrade. Then compare providers using current documentation rather than marketing labels alone.
Use the hosting selection checklist. Compare managed WordPress hosting. See how WPX fits the criteria.