Website slow: CPU, memory or process limit reached
On this page
Each hosting account has its own share of the server: processor (CPU), memory and a number of processes. When the account reaches its share, its websites are slowed down — other accounts are not affected. Resource Usage shows when that happens.
Symptoms
- Pages take several seconds, especially at busy times or in the admin area.
- Resource Usage shows Limits reached with entries like "slowed 25 min", "2× memory" or "3× processes".
- The first visit after a quiet period is slower than the next ones.
Causes
Most likely first:
- The account reaches its processor limit — heavy pages, many visitors, bots, or a cron job.
- Pages are built again for every visitor — no page cache.
- Many slow requests at the same time — each account can run a limited number of PHP requests at once; the next ones wait.
- A slow external service (an API, a font or script from another site) the page waits for.
- The first request after 5 quiet minutes starts PHP again for that site, which takes a moment.
Fix
See the limits
- Open Resource Usage (section Advanced).
- Under Server resources you see Processor, Memory and Processes (PHP, cron jobs, SSH) with their limits, and per day the CPU time, Peak memory, Peak processes and Limits reached.
"slowed … min" means the account used its full processor share for that long: pages were slowed down, nothing was stopped. Memory and processes entries mean a process was stopped or could not start (visitors may have seen errors; see 503 Service Unavailable).
1. Processor limit
- Find what runs at those times: Visitors (section Advanced) shows the most visited pages; a burst on one URL (search, login,
xmlrpc.php) is often a bot. - For WordPress, tick Block XML-RPC on the WordPress page unless an app needs it.
- Check Cron Jobs: a job every minute that does heavy work uses the same share as your websites.
- If your sites reach the limits every day with normal visitors, ask your host for a bigger plan.
2. Page cache
On the WordPress page, click Turn on under Page cache for each site. Visitors then get ready-made pages, many times faster; signed-in users and shopping carts always see live pages. For other applications, turn on their own cache.
3. Many slow requests at once
Open Errors (section Advanced) and look for Maximum execution time lines; one slow page can hold PHP processes that other visitors are waiting for. Fix or cache that page.
4. Slow external services
Test the page with your browser's developer tools (Network tab) to see what it waits for. Remove or replace the slow plugin or embed.
5. The first visit after a quiet period
To save memory, PHP for a website stops after 5 minutes without requests and starts again with the next visitor. This adds a moment to that one request only; it is not a fault.
Good to know
- Your account's PHP, cron jobs, SSH sessions and Node.js, Python or Ruby applications all share the same limits.
- Uptime (section Advanced) checks your websites every 5 minutes and emails you when one is down.
Still not working?
If Resource Usage shows no limits reached and the site is still slow, run Site Check: Answer on this server shows how long the server takes for the home page. If your host has turned on the AI assistant, click Ask the AI assistant what is wrong, or contact your host through Support.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Website shows 503 Service Unavailable (or 502, 504)
Why a site answers "503 Service Unavailable" (or 502/504) here: account limits reached, an application stopped, PHP not starting. How to check and fix it.
- PHP "Maximum execution time exceeded" error
Fix "Fatal error: Maximum execution time of 30 seconds exceeded": raise max_execution_time in the control panel, or move long jobs to a cron job.
- Cron job not running (or not doing anything)
Your scheduled cron job does not run or seems to do nothing. Check the schedule, command, paths and PHP binary, and log the output to see the error.