"Resource limit is reached" is not a traffic cap. It is a ceiling on how many PHP requests your account may run at the same instant, and most hosts never tell you the number. Here it is printed on the plan card, with the memory, CPU, I/O and inode limits next to it, so you can size the move before you make it.
What the error is telling you
Shared hosting runs every account inside a CloudLinux container with a fixed set of limits. The one that produces the 508 page is the entry process limit: the number of PHP requests allowed to execute at the same moment. Three things decide whether you ever hit it.
Every uncached page view, admin action, cart update, search and form post occupies one worker for as long as PHP takes to build the response. If the ceiling is 10 and the eleventh request arrives, it is refused. A slow site hits the ceiling with far fewer visitors than a fast one.
Apache with CloudLinux refuses the request instantly with a 508. LiteSpeed queues it for up to two minutes first and only returns a 503 if a worker never frees up. Same cause, different symptom. Our shared platform runs LiteSpeed, so a short spike queues instead of failing.
A page served from the LiteSpeed cache is answered by the web server and never starts PHP, so it uses no entry process at all. On most WordPress sites that is the bulk of traffic. The published ceiling applies to the genuinely dynamic remainder, which is a much smaller number than your page views.
Want the long version? Our guide to the 508 resource limit error on WordPress walks through the concurrency math, the LiteSpeed queue and a calculator that turns your peak traffic into a worker count.
Printed, not hidden
These are the CloudLinux values applied to the account, the same numbers cPanel shows you under Resource Usage. Compare them with what your current host enforces before you move.
| Plan | Entry processes | Memory | CPU | Processes | Disk I/O | IOPS | Inodes |
|---|---|---|---|---|---|---|---|
| WP Bronze | 30 | 2 GB | 200% (2 cores) | 200 | 10 MB/s | 1,024 | 250,000 |
| WP Silver | 40 | 3 GB | 300% (3 cores) | 300 | 20 MB/s | 2,048 | 400,000 |
| WP Gold | 50 | 4 GB | 400% (4 cores) | 400 | 30 MB/s | 3,072 | 600,000 |
| WooStart | 40 | 3 GB | 300% (3 cores) | 300 | 20 MB/s | 2,048 | 400,000 |
Limits apply to the whole cPanel account, not per website. WooStart is the WooCommerce plan and sits at Silver-level concurrency because cart and checkout requests are never cached. A site that needs more than 50 workers on a sustained basis belongs on a VPS, and we will say so rather than sell you Gold.
Why the same site hits the ceiling less often here
The limit is only half the story. What matters is how many of your requests have to count against it, and whether anyone else on the server can spend your allowance.
The LSCache plugin is pre-installed and active. Cached pages, including the front page, posts and category archives, are served without starting PHP. On a typical site that removes most page views from the entry process count before you tune anything.
CloudLinux isolates each account. A neighbour's traffic spike, runaway cron job or broken plugin consumes their workers and memory, not yours. A busy server does not lower your ceiling; only your own requests do.
cPanel shows current usage and any faults for entry processes, memory, CPU and I/O under Resource Usage, with history. If a plugin or a bot starts eating workers you see it the same day, instead of discovering it through a 508 page.
Three sizes
Size by concurrent dynamic requests, not by monthly visitors. Workers and memory are the deciding pair and both are marked on each card. Staging, daily offsite backups, free SSL and a dedicated IP are on all three.
A site that hit the limit on a 10 to 20 worker plan elsewhere.
US$100.44 due today for 36 months
Renews at the same price, no increase
Pick this if: Content sites and small WooCommerce stores whose spikes are short, where caching will absorb most of the traffic.
Choose WP Bronze30-day money-back guarantee
Membership sites, busy blogs and stores with real logged-in traffic.
US$136.44 due today for 36 months
Renews at the same price, no increase
Pick this if: The usual answer for a site that was throttled on another host: a third more workers than Bronze and 3 GB for heavier plugins.
Choose WP Silver30-day money-back guarantee
The most concurrency shared hosting here offers.
US$172.44 due today for 36 months
Renews at the same price, no increase
Pick this if: Sites with long uncached requests, large catalogs or several busy sites in one account. Beyond this, a VPS is the honest next step.
Choose WP Gold30-day money-back guarantee
Not sure which? Open a ticket with your current host's name and the plan you are on, or a screenshot of its resource usage page, and we will tell you which tier covers your peak with headroom, or whether it is a VPS question.
Moving from a host that throttles you
Migration is free and done by our team. The point of moving is to stop seeing the error, so the process ends with a measurement, not with a DNS change.
cPanel or FTP plus database access on the current host is enough. Keep the source site online; nothing is deleted there.
Files, database and email are moved, LSCache is enabled and the site is checked on a temporary URL before you change anything.
cPanel Resource Usage shows entry process, memory and CPU peaks against the published limit. Faults should read zero through your usual busy hours.
Switch DNS when you are satisfied. The old host stays reachable until you cancel it, so there is a way back if anything was missed.
Before you order
Reviewed by Adnan Canturk, Founder of Ahosting with 24 years in web hosting. Last updated:
Ready when you are
Every limit is printed, the cache keeps most of your traffic off the counter, and the migration is free. If your site is genuinely too big for shared hosting we will tell you that too.
Published-limit WordPress hosting from
$2.79 /month
WP Bronze on a 36-month term. Renews at the same price, no increase.
Prices exclude applicable taxes. Refunds are governed by the current Terms of Service.