Identifying the Cause of Website Overload Using Resource Usage in cPanel
If you notice that your website's loading time is suddenly increasing or showing "508 Resource Limit Reached" errors, it usually indicates a resource overload. A website becomes overloaded when its scripts, plugins, or traffic exceed the allocated hosting limits. You can easily diagnose the exact cause inside cPanel by following these steps.
Step 1 – Access the Resource Usage Dashboard
Log into your HostGete cPanel account, scroll down to the Metrics section, and click on Resource Usage. You can also quickly find this by typing "Resource Usage" in the cPanel top search bar.
The main dashboard will instantly show one of the following statuses regarding your account health over the past 24 hours:
- Your site had no issues in the past 24 hours: Your website is perfectly optimized and running within safe limits.
- Your site has been limited within the past 24 hours: This indicates that your website suffered an overload. cPanel will highlight which exact resource (CPU, RAM, or Entry Processes) hit the ceiling.
- Your site might hit resource limits soon: Your current traffic or active processes are pushing the boundaries, and your site is on the verge of slowing down.
Step 2 – Check Resource Usage Details and Graphs
To find out what triggered the excessive usage, click on the Details button or navigate directly to the Current Usage tab. Here, you will see historical charts broken down by CPU usage, physical memory, inodes, and I/O speed.
By default, these graphs display resource usage on an hourly basis for the current day. If you want a more precise look during a specific crash time, click on the Timeframe and Time Unit drop-down menus to change the view to minutes or look back at the previous week.
Step 3 – Inspect Snapshots to Find the Bad Script
The most powerful feature for diagnosing an overload is the Snapshot tab. When your site hits a limit, cPanel takes a "snapshot" of the exact server processes running at that critical second.
Under the Process List, you will see four key columns:
- PID: Process ID (backend system identifier).
- CMD: The actual name or path of the script running (e.g.,
index.php,wp-cron.php). - CPU: The percentage of CPU power that specific process was hogging.
- MEM: The amount of RAM memory consumed by that process.
Example: If you see a process named bad-plugin-script.php showing 103% CPU usage, it tells you exactly which script or WordPress plugin is broken and dragging down your entire website's performance.
Pro Tip: Don't forget to look at the Database Queries and HTTP Queries tabs within the Snapshot section. They will show you if a slow database query or a sudden brute-force attack on your login page is responsible for the server spike.
