In this article10 sections
When WordPress is slow on cPanel hosting, check five things in this order: the Resource Usage screen in cPanel, your PHP version, your plugins, your images, and your database and visitor traffic. Each check takes a few minutes, needs no coding, and points to a specific fix. Most slow sites turn out to have one dominant cause, and finding it first saves you from changing things that were never the problem.
This guide is written for cPanel shared hosting, where the account has set limits on CPU, memory and processes. For a server-level look at slow sites that includes SSH tools, read Why Is My WordPress Site Slow? If you already know the cause and want quick fixes, see how to speed up WordPress in 5 easy steps.
Before you start: test the right way
Open your site in a private or incognito window, not while logged in, because WordPress treats logged-in users differently. Run the same page through PageSpeed Insights twice and note the result of the second run. Write down the score, so you can compare after each fix. Slow in the dashboard but fast for visitors points to different causes than a slow front page, so note which one you are dealing with.
Check 1: Look at Resource Usage in cPanel
Shared hosting gives each account a share of the server. If your site reaches its share, it slows down, and in severe cases it shows errors. cPanel shows this directly.
- Log in to cPanel and open Resource Usage under Metrics.
- Look at the graphs for CPU, memory, processes and disk activity, and at the Faults count.
- Set the time range to cover when the site felt slow.
If a graph touches its limit line or you see faults, the account is being held back at that moment. That points to a heavy plugin, a traffic spike or bot traffic, covered in the checks below. If everything sits well below the limits, the cause is more likely page weight (images and scripts) than server capacity.
Tip. The limits depend on your hosting plan. If your site reaches them regularly even after the fixes below, that is the sign you have outgrown the plan, not that something is broken.
Check 2: Confirm your PHP version
An old PHP version is slower and less secure. In cPanel, open MultiPHP Manager, find your domain and look at the version. If it is several versions behind, tick the domain, choose the newest version your theme and plugins support, and click Apply. Then check the front page and /wp-admin. If either shows an error, switch back, update the plugin or theme that caused it and try again.
While you are in cPanel, open Errors under Metrics. A long list of repeating errors from one plugin is both a speed problem and a clue to which plugin to remove.
Check 3: Find a heavy plugin
One badly behaved plugin can slow the whole site. The fastest way to find it without special tools is to switch them off and see what changes.
- Make a backup in Backup Wizard first.
- In WordPress, go to Plugins and deactivate all plugins, except one that your site cannot work without if you rely on it.
- Test the front page again in a private window. Note the speed.
- Reactivate the plugins one at a time, testing after each one. When the speed drops sharply, you have found the heavy one.
Do this at a quiet time, because some features, such as forms or a shop, will not work while their plugins are off. Once you know the plugin, update it, replace it with a lighter alternative, or remove it. Sliders, social feeds, related-post widgets and page-builder add-ons are common culprits.
Check 4: Look at page weight and images
If your server is not struggling, the page may simply be heavy. In the PageSpeed report, look for Properly size images, Serve images in next-gen formats and Reduce unused JavaScript.
- Images: resize and compress them before you upload, using a free tool such as Squoosh (squoosh.app). A full-width image rarely needs more than about 1600 pixels or 200 KB.
- Disk usage: in cPanel, open Disk Usage under Files and look inside
wp-content/uploads. Very large folders point to oversized images or old files. - Scripts: each plugin can add its own styles and scripts. Removing plugins you do not use is the simplest way to cut them.
Check 5: Check the database and visitor traffic
Two quieter causes are a bloated database and unwanted traffic.
Database. Clear the obvious clutter from the dashboard: empty Comments, then Spam, empty the trash for posts and comments, and delete drafts you will never publish. To see how big the database is, open phpMyAdmin under Databases in cPanel and look at the size of your WordPress database. If it is far larger than your content would suggest, ask support or a developer to look at it.
Traffic. Open Visitors or Raw Access under Metrics. Many requests to /wp-login.php or /xmlrpc.php from the same address are a login attack, which uses resources even though nobody sees it. You can block a repeated address with IP Blocker under Security. If the traffic is spread across many addresses, contact support, because blocking one by one will not keep up.
Match what you found to a fix
- Resource graphs at the limit, one plugin to blame: remove or replace the plugin.
- Resource graphs at the limit, lots of login requests: block the addresses and ask support about bot protection.
- Graphs low, page heavy: compress images and remove unused plugins.
- Old PHP version: update it in MultiPHP Manager.
- Everything looks fine but the first load is slow: add a page cache, as in the 5-step guide.
Common mistakes to avoid
- Testing while logged in. You will see slower pages and different results from your visitors.
- Judging by one test. Speed tests vary. Run each one twice and compare like with like.
- Installing more plugins to fix a slow site. Each plugin adds load. Fix the cause first, then add only what you need.
- Skipping the backup. Deactivating plugins and changing PHP is safe with a backup and stressful without one.
- Ignoring the limits. If the graphs show you regularly reach the plan limits, tuning will only help so much.
When the plan is the problem
Sometimes a site is well set up and still slow, because it has grown past what its plan allows. Signs are resource graphs that touch their limits during normal traffic, or slowdowns that match your busiest hours. In that case, tuning gives small gains, and a bigger plan is the real fix. You can compare options on our shared hosting page, and our support team can help you read the Resource Usage screen if you are unsure.
Related guides: fixing WordPress emails going to spam.
If the checks point to the account’s limits, read how to fix the 508 Resource Limit Is Reached error on cPanel. If the site keeps outgrowing shared hosting, see when to move WordPress from shared hosting to a VPS.
Frequently asked questions
Why is my site slow only sometimes?
Often it is traffic or bots at certain hours, or a scheduled task running. Compare the Resource Usage graph with the times you noticed slowness.
Why is the WordPress dashboard slower than the front page?
The dashboard cannot be cached, so it shows the real cost of your plugins and database. Many heavy plugins are visible there first.
Will deactivating plugins delete my settings?
Deactivating keeps them. Deleting a plugin may remove its data, so deactivate first and delete only the ones you are sure about.
Do I need a speed plugin?
Not to find the cause. These checks use only cPanel and WordPress. A cache plugin helps after you have fixed the cause.
How do I know when to upgrade?
If the site hits its resource limits during normal traffic after you have removed heavy plugins and compressed images, the plan is the limit.
The short version: check Resource Usage first, update PHP, find a heavy plugin by switching them off, shrink images, clean the database and look at your traffic. Then match what you found to a fix, and upgrade only if the limits are still the problem.