Your hosting plan comes with quotas — disk space, bandwidth, CPU, memory, concurrent processes. The portal shows you where you stand against each limit so you can spot creeping growth before it bites.
At a glance
Open your service detail page in Services and click your hosting. Under Information, you'll see:
- Disk usage — files and databases combined, against your storage cap.
- Bandwidth — outgoing data this billing period.
- Inodes — file count, which has its own limit on shared plans.
- Concurrent processes — peak active processes recently.
If you're approaching any limit, the relevant tile turns yellow at 80% and red at 95%.
Detailed CPU and memory
For deeper analysis, cPanel has a Resource Usage tool:
- Open cPanel from your service.
- Find Resource Usage under Metrics.
- View 24-hour graphs of CPU, memory, I/O, and entry processes.
This is the tool to use when you want to answer "is my site causing spikes?" or "which hour of the day is busiest?"
What each limit means
Disk space
Combined size of all files in your account: website code, media, databases, email, backups stored locally. Counts against your plan's storage quota.
When you're near the limit:
- New file uploads start failing.
- Email delivery may slow.
- Backups can't complete.
To free up space: clean up old files, delete unneeded backups (keep them off-server), prune email storage. The file manager has a "size" sort that helps find big offenders.
Bandwidth
Outgoing data transferred from your hosting to visitors. Counts against your plan's monthly cap. Resets at the start of each billing month.
Most plans have generous bandwidth (often advertised as "unlimited" up to fair-use levels). For most sites, you won't get close.
If you do approach the cap:
- Visitors may see slow loads as we throttle.
- Some plans hard-stop traffic until next month.
The Cloudflare CDN we run in front of your site significantly reduces bandwidth used at the origin server — most static asset delivery happens at the Cloudflare edge.
Inodes
An inode is roughly "one file" — every file, folder, email, and database entry counts. Most shared plans cap inodes around 200,000–500,000.
You'd hit this if you have a lot of small files: tens of thousands of email messages, a CMS with millions of cached files, a sprawling Git repository with full history.
To reduce: clean up email (especially spam folder), prune old backups, remove unused WordPress themes/plugins, vacuum your CMS's cache directories.
CPU
Your account's share of the server's processor. Measured in "CPU seconds per second" — basically, how much of one CPU core you're allowed to use sustained.
Hitting the limit:
- Traffic spikes get throttled.
- Some long-running scripts get killed.
- Visible as "504 Gateway Timeout" or slow responses.
WordPress sites that hit CPU limits are usually running heavy plugins, doing real-time queries on a slow database, or being scraped by bots. The fixes:
- Install a caching plugin (LSCache is already there — make sure it's active).
- Identify and disable slow plugins.
- Block bad bots via Cloudflare.
- Or upgrade to a plan with more CPU.
Memory
How much RAM your account can use at any moment. Each PHP request takes a slice; if you exhaust the pool, new requests get rejected with errors.
Common cause: a script that loads too much into memory at once (importing huge datasets, generating large reports, processing big images). Either chunk the work or upgrade.
Concurrent processes / entry processes
How many active HTTP requests can be in flight simultaneously. If you hit this limit, new visitors get queued or rejected briefly.
Caused by:
- Traffic spikes that exceed the plan's concurrency.
- Slow PHP that holds connections open.
- DDoS or bot attacks.
LSCache and Cloudflare both help by serving requests without involving PHP at all.
When you're consistently near limits
Time to upgrade. The portal's Upgrade flow shows you which plans have higher limits across the board. Upgrading typically resolves all limits at once (better plans give more of everything).
For specific bottlenecks:
- CPU/memory consistently maxed → consider VPS, where you have dedicated resources.
- Disk space crawling up → may need a plan with more storage; or audit what's actually using it.
- Bandwidth blowing past limits → either you're getting popular (good problem) or you have unusually heavy assets that should be on a CDN.
Power-user note
The "entry processes" limit is the one most likely to bite a busy WordPress site. Most plans cap around 20–50. With aggressive LSCache and Cloudflare proxy mode, even high-traffic sites stay under because cached requests don't count toward the limit.