So… What the Heck Are PHP Workers?<\/h2>\n
Good question!<\/p>\n
Imagine you run a coffee shop. PHP workers are like your baristas. Each one can serve a request (make a coffee). More customers require more baristas. But if you don\u2019t have enough, customers (visitors) wait. On a shared hosting plan, you only get a limited number of these imaginary baristas. The moment you reach the limit, incoming requests just… wait.<\/p>\n
This waiting? It\u2019s called throttling<\/em>.<\/p>\n That\u2019s what happened to me.<\/p>\n At first, I thought it was my theme. Then maybe a rogue plugin. I tried clearing caches, deactivating things, reinstalling WordPress. Nothing worked. My host\u2019s support logs showed high CPU usage and something called \u201centry processes\u201d spiking. I was hitting the ceiling of my allocated PHP workers.<\/p>\n Shared hosting providers limit your PHP workers to keep things fair.<\/em><\/p>\n If your site starts using more than your fair share\u2014bam\u2014you get throttled. Boom, bottleneck.<\/p>\n This was the second part of my detective work. Here’s what I found were the main suspects:<\/p>\n My host used PHP-FPM (FastCGI Process Manager). It\u2019s a way to manage how PHP workers are handled behind the scenes. Thankfully, some shared hosting plans allow you to tweak these settings via a simple configuration panel. Mine did!<\/p>\n Three key settings you need to know:<\/p>\n I had no idea before, but I ended up diving deep into My site\u2019s config was set to dynamic<\/strong>. Sounds good, right? Turns out, the initial settings were terrible for my traffic pattern.<\/p>\n Here\u2019s what I changed:<\/p>\n These changes allowed more simultaneous PHP processes to handle requests during peak times.<\/p>\n Warning:<\/em> You can\u2019t just crank up all the numbers. You need to stay within your host\u2019s resource limits. Otherwise, you\u2019ll get suspended!<\/p>\n While PHP-FPM tuning helped a lot, nothing beat caching.<\/p>\n I installed a full-page caching plugin: LiteSpeed Cache<\/strong>. Since my host used LiteSpeed servers, performance skyrocketed. Instead of every visit waking up a PHP worker, many requests were served instantly from the cache.<\/p>\n It was like hiring a robot barista that could handle a thousand customers at once.<\/p>\n Other caching plugins I tried:<\/p>\n If you’re hitting your limits on shared hosting, here are some things that helped me:<\/p>\nHow I Discovered the Throttling<\/h2>\n
What Causes High PHP Worker Usage?<\/h2>\n
\n
Step 1: Getting to Know PHP-FPM<\/h2>\n
\n
php-fpm.conf<\/code>. It felt like popping the hood of a car and recognizing nothing\u2014until something clicked.<\/p>\nHere\u2019s How PHP-FPM Modes Work<\/h2>\n
\n
![\"\"](\"https:\/\/unitconversion.io\/blog\/wp-content\/uploads\/2025\/11\/a-computer-screen-with-a-line-graph-on-it-website-performance-php-workers-slow-website.jpg\")
\nStep 2: Process Manager Tuning<\/h2>\n
\n
The Real MVP: Caching<\/h2>\n
\n
![\"Why](\"https:\/\/unitconversion.io\/blog\/wp-content\/uploads\/2023\/05\/why-do-you-need-security-plugins-to-keep-your-wordpress-site-safe-scaled.jpg\")
\nMore Tips to Reduce PHP Worker Usage<\/h2>\n