Every shared hosting account has resource limits, and cPanel shows you exactly how close you are to them. Almost nobody looks at this until they get a warning email saying they’ve hit a limit — at which point the graphs suddenly matter a great deal and nobody knows how to read them.
Here’s what the numbers actually mean, what normal looks like, and what a spike usually indicates.
Where to Find It
Log into cPanel and look for Resource Usage under the Metrics section — sometimes it’s simply visible on the cPanel home screen as a summary widget. Click into it for the full graphs.
You’ll see several metrics tracked over time, usually with options to view the last hour, day, week, or month. The four that matter most:
CPU Usage
This measures how much processing power your account is using. Every PHP script that runs, every database query, every image being processed — all of it uses CPU. Shared hosting allocates a percentage of the server’s total CPU capacity to your account, shared fairly with everyone else on the same server.
What normal looks like: brief spikes when pages load, generally low and settled between requests. A site with modest traffic should show mostly quiet graphs with small bumps.
What a sustained high reading means: something is running continuously and expensively. Common causes: a plugin doing something inefficient on every page load, a cron job that’s misconfigured and running too frequently, or a bot/crawler hammering your site with rapid requests.
Normal usage pattern vs a problem spike
Entry Processes
This tracks how many simultaneous PHP processes your account is running at any given moment. Every visitor loading a page, every background task, every AJAX request on your site consumes an entry process while it’s running. Shared hosting limits how many you can run at once.
What normal looks like: for most small business sites, entry process usage stays well under the limit almost all the time. A handful of concurrent visitors doesn’t usually push this high.
What hitting the limit means: either you’re getting a genuine traffic surge — worth celebrating, but worth talking to us about upgrading if it’s sustained — or something is holding processes open too long. A slow database query, a plugin that hangs, or a script waiting on an external API that’s timing out are common culprits. When entry processes max out, new visitors can get temporary errors because there’s no process available to handle their request.
I/O Usage
Input/output measures how much data is being read from and written to disk. This includes serving files, writing to log files, database operations, and any file uploads or generation happening on your account.
What normal looks like: low and steady for most content sites. E-commerce sites and sites with heavy image/file uploads will naturally run higher.
What a spike means: often it’s a backup process running (yours or ours), a large file transfer, or — less commonly — a compromised account being used to read or write large amounts of data. If you see an I/O spike you can’t explain and it’s not backup-related, that’s worth a support ticket to rule out a security issue.
Physical Memory Usage
This tracks RAM usage by your account’s processes. WordPress and its plugins load into memory to execute, and the more plugins you’re running — and the heavier they are — the more memory each page load consumes.
What normal looks like: memory usage that rises during active page loads and drops back down between them.
What consistently high memory means: usually too many active plugins, a memory leak in a specific plugin (some poorly coded plugins don’t release memory properly), or a WordPress installation with a lot of large, complex pages being built dynamically. This ties directly into what we wrote about plugin bloat — fewer, better-chosen plugins usually means lower memory usage across the board.
What to Do When You Get a Warning Email
If you receive a resource limit warning, don’t panic — it’s informational, not a suspension notice (those are separate and much less common). Here’s the order of operations:
- Check which resource triggered it. The email will specify — CPU, entry processes, I/O, or memory.
- Look at the graph for that specific resource over the last 24-48 hours. Is it a single spike or sustained high usage?
- If it’s a single spike: check if it coincides with something you did — a bulk import, a plugin update, a manual backup. If you can identify the cause and it was a one-time event, no action needed.
- If it’s sustained: this is worth investigating. Check your active plugins for anything recently added or updated. Check your cron jobs for anything running too frequently. Check your traffic logs for unusual bot activity.
- If you can’t identify the cause, open a support ticket with the resource type and time period from the warning. We can look at what’s actually consuming the resource from our end and tell you specifically what’s happening.
When It’s Time to Consider Upgrading
If your resource usage is consistently near the limit during normal operation — not spiking occasionally, but regularly running high even after you’ve optimized what you can — that’s a genuine signal you’ve outgrown shared hosting for that account. This is different from a misconfiguration causing artificially high usage; it’s actual legitimate demand exceeding what shared hosting is designed to provide.
We covered the tiers in this post — VPS is the natural next step when shared hosting resource limits become a real constraint on legitimate traffic and usage, rather than a symptom of something fixable.
The short version: check your resource graphs occasionally, even when nothing’s wrong, so you know what normal looks like for your site. That way, when something is wrong, you’ll recognize it immediately instead of discovering it through a warning email.