WordPress 508 Resource Limit: Causes and Next Steps
A WordPressWordPress is free software for building and editing a website in your browser. It is written in PHP, so it builds each page when someone visits. 508 message saying Resource Limit Is Reached means your hostingWeb hosting is the service that keeps your website's files on a computer that is always online, so visitors can open your site at any time. account has reached its allowance for computing power, memory or concurrent processes.
More about this
The server temporarily refuses new requests.
This is especially common on shared hosting.
What the message means
Hosts set account limits for CPU, memory and concurrent processes. When your site reaches one, additional requests cannot run. This is account load, rather than necessarily broken website code.
Common causes
Which PHP version does your site report?
We read only what your site already sends in public: the headers and the top of the homepage. No scan, no login.
A spike in visitors or bots, a heavy pluginA WordPress plugin is an add-on you install in WordPress to give your site extra features, such as contact forms, SEO tools or a webshop., overlapping scheduled tasks, missing cachingA cache is a store of ready-made copies, such as finished pages, so a website or browser can show something instantly instead of building it again. or a script caught in a loop can reach the limit. Multiple sites on one account may share the allowance.
How to check safely
Review CPU, memory and process graphs or limit logs in the hosting panel. Check access logs for unusually frequent requests from one source or to one file. Back up before making changes.
Ask the host which process or file reached the limit.
What you can try
Enable caching if missing. Temporarily disable the newest or heaviest plugins and check whether load falls. Ask the host to filter unwanted bot traffic.
Repeated peaks may need a larger hosting plan or a different site setup.
PHP and prevention
A newer supported PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing. may run more efficiently, but test before changing versions. Review resource graphs monthly and after major changes. Remove unused plugins and schedule backups or large imports at quiet times.
Consider separating a busy site so it cannot exhaust the allowance for all your sites.
When to get help
If you cannot identify the plugin or traffic behind the load, ask for help. A person replies within 1 working day. Emergency repair starts from £315, excluding VAT.