How to Read Your cPanel Resource Usage and Spot Problems Early
Your website was fine yesterday. Today it is slow, or an occasional page throws a "503" or "Resource Limit Reached" error, or you cannot upload a file because "disk quota exceeded". Nothing has changed, you think. But something has: the resources your site uses, such as processing power, memory, disk space and connections, have crept up, and you have hit a limit.
The good news is that cPanel shows you what is going on, if you know where to look. This guide teaches you how to read your cPanel resource usage, what each number means, the early warning signs that something is wrong, and the practical fixes that keep your site fast and online.
Key takeaways
Shared hosting accounts have resource limits so that many sites can share a server fairly. Limits are not a punishment, but you need to know where yours are.
cPanel's Resource Usage page shows CPU, memory, entry processes, number of processes, I/O and IOPS against your limits, and counts faults, the times you hit a limit.
Slowdowns usually come from CPU, I/O and IOPS limits. Errors such as 500, 503 and 508 come from memory, process and entry-process limits.
Disk space, inodes (file count), bandwidth, email storage and error logs also deserve a regular look.
Spot trends early. Usage that sits near its limit, repeated faults or a steadily rising baseline all signal trouble ahead.
Most problems are fixed by caching, removing heavy plugins, blocking bad traffic and cleaning up. If you still hit limits, it is time to upgrade.
Why Shared Hosting Has Resource Limits
On shared hosting, many websites run on one physical server. To stop one busy or badly behaved site from slowing everyone else down, hosts set limits on each account. Many shared servers use technology such as CloudLinux to enforce those limits and to show you how much of each one you are using.
That is why honest hosts publish their limits, and why "unlimited" claims deserve suspicion. SteboHost publishes concrete limits on each plan page. See the plan limits for your plan.
When your site hits a limit, it is not usually suspended. Instead, the server slows your processes down, queues new requests or rejects them for a moment, which is what you and your visitors notice as a slow site or an error.
Where to Find Your Usage in cPanel
Log in to cPanel and look at the Metrics, Files and Email sections. Exact names and locations can differ slightly between cPanel versions and hosts.
Tool | Where | What it tells you |
|---|---|---|
Resource Usage | Metrics | CPU, memory, processes, I/O and IOPS against your limits, plus faults |
Disk Usage | Files | Which folders and databases use your storage |
File usage (inodes) | Statistics panel on the cPanel home page | How many files and folders your account holds |
Bandwidth | Metrics | Data transferred, by domain and by type of traffic |
Visitors, Awstats or similar | Metrics | Who visits, what they request and how much traffic they generate |
Raw Access | Metrics | Downloadable access logs for detailed investigation |
Errors | Metrics | The most recent entries from your site's error log |
Email Disk Usage | How much space each mailbox uses | |
Track Delivery | What happened to messages sent from your account | |
Process Manager or Terminal | Metrics or Advanced | Running processes, if available on your plan |
If you cannot see the Resource Usage tool, your host may not enable it, so ask support how to view resource usage on your plan.
The Six Resource Metrics Explained
Metric | What it measures | What happens at the limit | Common causes |
|---|---|---|---|
CPU | How much processing power your account uses | Scripts are throttled and pages slow down | Uncached WordPress, heavy plugins, bots, traffic spikes |
Physical memory (RAM) | Memory used by your processes | Processes can be terminated, causing 500 or 503 errors | Memory-hungry plugins, imports, image processing |
Entry processes (EP) | How many requests are being handled at the same moment | New visitors may see 503 or 508 errors | Slow PHP requests piling up, bots, busy admin screens |
Number of processes (NPROC) | The total processes your account runs, including background tasks | New processes cannot start, which can cause errors | Overlapping cron jobs, runaway scripts, many SSH sessions |
I/O | How fast your account reads from and writes to disk | Disk operations slow down | Backups, large file operations, heavy database activity |
IOPS | The number of separate disk read and write operations per second | Operations pause briefly until the next second | Thousands of small files, cache churn, logging |
In practice, CPU and entry processes are the limits that busy WordPress and WooCommerce sites hit most often. The others tend to rise together: an uncached site that is burning CPU is usually also running database queries that push up I/O.
How to Read the Resource Usage Page
Open it. In cPanel, go to Metrics and click Resource Usage. If an alert about reaching limits appears at the top, click its details link.
Look at the current usage table. For each resource you will see usage now, your limit and a count of faults. Some views use columns labelled A for actual usage, L for limit and F for faults.
Check the faults first. A fault means that, at that moment, your account hit the limit. A few faults at an odd time may be a one-off. Faults that repeat every day, or that appear when visitors complain, are your clue.
Open the graphs. Choose a time range, such as the last 24 hours or longer, and compare usage with the limit line. Note when usage peaks, and whether it climbs and falls in a pattern.
Look at the snapshots or processes view, if you have one. It lists what was running when usage was high: the commands, and how much CPU and memory each used. That often points to the culprit.
Compare with your visitors and your schedule. Does the peak match a traffic spike, a backup, a cron job or a marketing email?
What patterns tell you
What you see | What it usually means | What to do |
|---|---|---|
Short spikes that clear quickly | Normal bursts of traffic or a single heavy task | Usually nothing, but watch whether they become more frequent |
Usage sitting close to the limit for long periods | Your site is too heavy for its plan, or something is wasting resources | Optimise first. If that does not help, consider upgrading |
Spikes at the same time every day | A scheduled task such as a backup, import or cron job | Move it to a quieter hour, or make it lighter |
A baseline that rises week after week | Growth, a bloating database or a growing number of plugins | Clean up, and plan your next plan or server size |
Sudden jump with no change in real visitors | Bots, a brute-force attack, a scraper or malware | Check access logs, block bad traffic and scan the site |
Faults on one resource only | One specific bottleneck | Fix that resource first, using the table above |
Disk Space and Inodes
You can run out of space in two ways: bytes and files.
Disk space is the total size of everything in your account: website files, databases, backups, email and logs.
Inodes count how many files and folders you have, regardless of size. Thousands of small cache files, session files and stored emails can use up your inode limit long before the disk is full.
When either limit is reached, you may be unable to upload files, save changes or even receive new email.
How to find what is using the space
In cPanel, Disk Usage shows the biggest folders. If you have SSH or the Terminal tool, these commands help (see our guide to SSH and command-line tools for more):
du -sh * | sort -h
find . -type f | wc -l
ls -lhS | headThe first lists folder sizes, the second counts files in the current folder and the third lists the biggest files first.
Common space hogs
Old backups stored inside your account, and plugin-generated backup archives
Large error_log files that grow when something is repeatedly failing
Cache folders and temporary files
Old staging or test sites that you no longer need
Unoptimized images and video in your media library
Email, especially large attachments and unread spam
Unused themes, plugins and old websites
Bandwidth and Traffic
Open Bandwidth and Visitors (or Awstats) to see where your traffic comes from. Warning signs include:
A sudden spike with no marketing campaign to explain it
A single IP address or user agent making thousands of requests
Many requests to login pages such as wp-login.php or xmlrpc.php, which suggests brute-force attempts
Other websites loading your images directly (hotlinking)
Large downloads or video files using more bandwidth than expected
The Raw Access logs let you dig deeper. Bots and scrapers can account for a large share of requests on any site, so blocking abusive traffic often frees a surprising amount of resources. A web application firewall helps. See website security.
Email Usage
In Email Disk Usage, look for mailboxes that are nearly full, since full mailboxes bounce messages. In Track Delivery, look for large volumes of outgoing mail you did not send, which can mean a compromised mailbox or a hacked website sending spam. Sudden growth in bounced messages is another warning sign. Change passwords and scan your site immediately if you suspect abuse.
Database Health
Databases quietly grow, especially on WordPress and WooCommerce. Problems you can spot early:
A database that keeps growing, even though your content has not
Piles of post revisions, expired transients, spam comments and old sessions
Plugins that store large amounts of data, or run heavy queries on every page
Slow admin screens and slow search or filtering on your store
Check database sizes in cPanel's MySQL tools. Use a trusted cleanup plugin carefully, and always take a backup first. Tools such as the Query Monitor plugin can show slow queries, but try them on a staging copy of your site. Managed WordPress hosting with staging, such as managed WordPress hosting, makes that safer.
Errors and Logs
The Errors page in cPanel shows recent entries from your site's error log, and your site folders may also contain error_log files. Look for repeated messages, because they often identify the plugin or script that is failing.
Know what the common errors mean:
500 Internal Server Error: a general failure. Often a plugin or theme problem, a PHP error, a memory limit or a bad .htaccess file.
503 Service Unavailable: the server could not handle the request at that moment, often because a limit such as entry processes was reached.
508 Resource Limit Reached: your account has hit one of its resource limits.
"Allowed memory size exhausted": a PHP script used more memory than allowed.
If you see these errors, open Resource Usage and see which metric faulted around the same time.
12 Early Warning Signs
Your pages feel slower than they used to, especially the admin dashboard
Faults appear in Resource Usage, even if rare
CPU or entry processes sit near their limits for long periods
Visitors report occasional 503 or 508 errors
Disk usage or inode count is above about 80% of your limit
error_log files are growing quickly
Bandwidth use jumps without a clear reason
Many requests hit wp-login.php, xmlrpc.php or odd URLs
Cron jobs overlap or take longer each time
Mailboxes are almost full, or bounced mail is increasing
The database keeps growing
Your site slows down at the same time every day
The 80% figure is a rule of thumb. The point is to act before you hit 100%.
Common Causes and Fixes
Uncached pages
Without caching, every visit runs PHP and database queries. Use a caching plugin that suits your server, such as LiteSpeed Cache on LiteSpeed servers. Caching is the single biggest lever for CPU and entry processes.
Heavy or too many plugins
Deactivate and delete plugins you do not use, and replace plugins that are slow or badly maintained. Test changes on staging, and update to a current PHP version, since newer versions run code more efficiently. Our guide to PHP versions and website speed explains why.
Bots and attacks
Block abusive IPs, rate-limit login attempts, restrict xmlrpc.php if you do not use it, and use a web application firewall. Keep software updated and protect admin accounts with strong passwords and two-factor authentication.
WordPress scheduled tasks (WP-Cron)
By default, WordPress triggers its scheduled tasks when someone visits a page, which can cause extra load. A common improvement is to turn off that behaviour in wp-config.php and run the task from a real cron job at a regular interval instead:
define('DISABLE_WP_CRON', true);If you do this, you must add a cron job that calls wp-cron.php regularly, or scheduled posts, backups and other tasks will not run. Ask support if you are unsure.
Backups and heavy tasks at busy times
Backup plugins, imports, image regeneration and large exports use a lot of CPU and I/O. Schedule them for quiet hours, such as the middle of the night, and avoid running several at once. Host-level backups, such as SteboHost's daily backups, take that load off your site.
Large, unoptimized images
Big images use I/O, bandwidth and disk space. Compress and resize them, use WebP or AVIF and lazy loading. Our guide to image optimization shows how.
Cron jobs that overlap
If a job takes longer than its schedule interval, new copies stack up and use more processes. Lengthen the interval, make the script faster or add a lock so it does not run twice at once.
Traffic spikes from campaigns
A successful promotion, a viral post or a sales event can briefly multiply visits. Cache aggressively, optimise your heaviest pages beforehand and warn your host about major events. If your traffic is growing steadily, plan an upgrade.
Malware or hacked sites
Unexplained high CPU, unknown processes, strange files, spam being sent or traffic to odd URLs can indicate a compromise. Scan your site, restore a clean backup, change all passwords and update everything. Malware scanning on your hosting plan helps catch problems early.
Build a Simple Monitoring Routine
Weekly (about 10 minutes)
Open Resource Usage and look at the past week's graphs and faults
Check disk usage and inodes
Skim the Errors page and any large error_log files
Look at bandwidth and visitors for anything odd
Check for pending updates
Monthly
Review your largest folders and delete what you no longer need
Check database sizes and clean up where safe
Review plugins and remove the unused ones
Check mailbox sizes and spam
Test your backups by checking that a restore works
Look at how usage has changed since last month
Alerts and external monitoring
Resource Usage shows you the past, so also set up alerts. Use an uptime monitor that checks your site every few minutes and emails or messages you if it goes down, and turn on any usage alerts your host offers. SteboHost's monitoring watches uptime, resources and security events around the clock, and you can follow incidents on the system status page.
Optimise or Upgrade?
Always try to optimise first, because it is cheaper and makes your site faster. But some growth is simply growth.
Optimise first if: the spikes are caused by bots, an uncached site, heavy plugins, scheduled tasks or oversized images.
Consider upgrading if:
You have already optimised and still see regular faults
Your traffic and orders have grown steadily
You run an online store or application with many logged-in users
You need more storage, mailboxes or websites than your plan allows
You need dedicated resources and full control
On SteboHost, you can start on shared hosting and scale to a VPS when you need dedicated CPU and RAM, with an upgrade in minutes and no downtime, paying only the difference. You can compare plans and pricing any time.
How to Get Useful Help From Support
If you cannot find the cause, contact support and include:
The domain and what is going wrong
The date and time, with your timezone, when the problem occurred
Screenshots of Resource Usage, showing which metric faulted
Any error messages, and what you changed recently
What you have already tried
Specific details let the team check server-side logs for exactly that window.
Why SteboHost
SteboHost is built so that you can see, understand and stay inside your limits:
Concrete resource limits published on every plan page, with no vague "unlimited" claims. See the plan limits.
24/7 infrastructure monitoring of uptime, resources and security events, and a 99.9% uptime SLA.
WAF, Imunify360 malware scanning and DDoS mitigation on every plan, which helps filter out bad traffic before it uses your resources. See website security.
Fast technology: LiteSpeed web servers and NVMe storage, with LiteSpeed caching on managed WordPress hosting.
Daily backups with 7-day retention and one-click restore.
Easy growth from shared hosting to VPS and cloud when you need more power.
Free migration on annual plans, so you can bring an overloaded site to a better setup.
Support in your timezone on +254 703 610 464 during East Africa Time business hours, with 24/7 urgent monitoring, support options listed on each plan page, and billing in KES by M-Pesa, card or bank transfer.
Current plan and renewal prices are shown on the pricing page, and checkout confirms any active promotion, currency, taxes and terms. Explore SteboHost web hosting, or browse the knowledge base for more performance guides.
Conclusion
Your cPanel resource usage is an early-warning system. Check it weekly, learn what each metric means, watch for faults and rising baselines, and act while the problem is small: add caching, trim plugins, block bad traffic, clean up files and schedule heavy tasks for quiet hours. If your site has genuinely outgrown its plan, move up on your own terms, before your visitors notice.
Need help reading your usage or choosing the right plan? Contact the team or call +254 703 610 464, and SteboHost will help you find the cause and the right fix.
Frequently Asked Questions
Where do I find resource usage in cPanel?
Log in to cPanel and open the Metrics section, then click Resource Usage if your host provides it. You can also check Disk Usage under Files, Bandwidth, Visitors and Errors under Metrics, and Email Disk Usage under Email. If you cannot find Resource Usage, ask your host how to view it on your plan.
What are "faults" in cPanel resource usage?
A fault is recorded each time your account reaches one of its limits. CPU, I/O and IOPS faults usually slow your site down, while memory, process and entry-process faults can cause errors such as 500, 503 or 508. Occasional faults are common, but frequent faults mean you should optimise or upgrade.
What are entry processes?
Entry processes are the number of requests your account is handling at the same moment, such as visitors loading uncached pages or admin screens. If they hit the limit, extra visitors may see 503 or 508 errors until some requests finish. Caching, blocking bots and speeding up slow scripts reduce them.
What does the "508 Resource Limit Reached" error mean?
It means your account hit one of its resource limits, such as entry processes or CPU, so the server could not handle the request at that moment. Open Resource Usage to see which limit faulted, then reduce load with caching, plugin clean-up and bot blocking, or upgrade if your site has outgrown its plan.
What is an inode, and why does it matter?
An inode counts a single file or folder in your account, whatever its size. Thousands of small files, such as cache files and stored emails, can use up your inode limit even if you have plenty of disk space left. When you hit it, you may be unable to upload files or receive email.
How often should I check my resource usage?
A quick look once a week is enough for most sites, with a deeper check once a month. Check more often after installing new plugins, changing your site or running a marketing campaign, and combine it with uptime monitoring so you hear about problems quickly.
How do I know when to upgrade my hosting plan?
Upgrade when you have already optimised your site, with caching, a lean plugin list and bad traffic blocked, and you still see regular faults, or when your traffic, storage or business needs have clearly grown. On SteboHost, you can move from shared hosting to a VPS with an upgrade in minutes and no downtime.
Written by Mercy Chepkemoi
SteboHost engineering and operations team. We write practical guides on hosting, domains, email and security for African businesses — based on what we see in the field, not marketing copy.
Ready to get started?
Browse our hosting plans or contact our team for help choosing the right one.