The Performance section in cPanel's Meridian theme is a single tab with a full read on your account's resource usage: bandwidth, visitor traffic, errors, and how close you're running to your plan's actual limits. If a tile is climbing toward the edge, that's your early warning before something starts failing.
Open it from the Meridian sidebar under Performance. If you're still on the classic Jupiter theme, switch with the "Try the new Meridian theme" button, or reach the equivalent classic tools (Resource Usage under Metrics) directly.
What's on the Performance tab
Four things live here, all scoped to your hosting account:
- Bandwidth: outgoing data transferred so far this billing period, plotted against your plan's cap.
- Visitors: traffic hitting your domains.
- Errors: recent error-log entries, useful for catching broken links or a misconfigured redirect before a customer reports it.
- Resources vs. plan limits: CPU, memory, entry processes, and I/O measured against what your plan actually allows.
The point of putting these on one screen is correlation. A spike in visitors that lines up with a spike in errors usually means a plugin or template is failing under load, not that the server is at fault.
Reading the resource limits correctly
Plan limits vary by account, so don't assume numbers from an old article or a different plan tier apply to yours. CPU percentage, entry processes, memory, and I/O on this tab are specific to what you're actually provisioned. For disk space and bandwidth against your cap, check the resource tiles in Services in the portal, where limits are shown against current usage. See Checking your hosting resource usage for a walkthrough of what disk, bandwidth, inodes, and concurrent processes mean and what happens when each one is exhausted.
Bandwidth: what actually counts against you
If you're seeing bandwidth climb faster than visitor count would explain, it's worth checking cache-hit behavior before assuming you need a bigger plan. For the full breakdown of how the server and edge layers work together, see How we make your site fast.
Errors: use it as a triage list, not just a log
A burst of errors that starts at a specific timestamp almost always maps to a specific change. Cross-reference the timestamp against anything you changed around then: a new plugin, a theme edit, a cron job that just started firing.
For WordPress sites, database bloat is a common general cause of slow or intermittent errors. See Optimizing your WordPress database for how to check and fix that.
When the numbers don't add up
If you're consistently pinned against a resource limit despite reasonable traffic, or the Performance tab shows usage that doesn't match what you'd expect from your visitor count, open a ticket from Support in the portal. A real person will look at the account directly. That's also the right move if you think you need a plan upgrade: the portal's Upgrade plan action handles the change, and support can help you figure out which limit is actually the bottleneck.