HOW TO: Fix High CPU usage in WordPress
By reading this article, you will learn to solve the problem of having high CPU usage in WordPress on your own. Besides, you can check out our Hosting services for more information. There are several ways that we recommend you to use:
1. Update WordPress
If you’re not using the latest version of WordPress update now. Make sure you backup your site first!
2. Update Plugins
Updating your WordPress plugins to the latest versions can often reduce high CPU usage. If you’re running an old version take a moment to update now.
3. Avoid beta versions of plugins
Whilst it’s cool to be at the cutting-edge, only use stable versions of WordPress plugins. Sometimes early release versions (also known as alpha or beta) can have bugs in the code which can cause CPU spikes.
4. Install a caching plugin
5. Disable WP-Cron
WP-Cron manages all the scheduled events on your WordPress site. WP-Cron is a very common cause of high CPU loads as it is called every time someone visits your website. Disabling WP-Cron and replacing it with a real cron job can drastically reduce CPU-load and prevent the chances your account is suspended due to exceeding your resources.
6. Only use plugins you really need
Do you really need that plugin that constantly checks for broken links? – The more WordPress plugins you have installed, the longer your site will take to load. Deactivate and delete any plugin that you don’t need. Aim for just a handful of plugins. This will speed up your site and keep your visitors happy.
If you’ve disabled plugins you don’t need, and still have high CPU usage you’ll need to try debugging each plugin to see if it’s the cause of the CPU spike. First make sure you’ve taken a backup of your entire WordPress site (files and database). Now try disabling each plugin one by one until the CPU load has been resolved. Once you’ve found the faulty plugin you should hopefully be able to reenable the others without seeing the CPU problems.
7. Avoid resource-hungry plugins
If using WooCommerce, or similar resource-hungry plugins, make sure your web hosting has sufficient resources.
If you’re running CPU and Memory intensive plugins on a standard shared-hosting, or budget VPS hosting you may find your site performs badly due to insufficient server resources. Symptoms include slow loading pages, database errors and increased visitor abandonment.
With many web hosts, if you try running CPU intensive WordPress plugins on a shared-hosting package you risk your site being suspended due to high-CPU loads.
8. Avoid buggy WordPress Themes
A badly written WordPress Theme or one written with demanding features such as server-side image resizing can be CPU intensive. To rule out problems with your WordPress theme try the following:
- Check error logs for problems. Login to cPanel and check the Error logs for errors.
- Contact the theme developer and ask if there’s any known issues.
- Disable any dynamic features built into the theme such as thumbnail resizing. Some WordPress themes have their own image resizing modules which can cause high CPU usage. If possible we recommend disabling them in favour of using the more efficient image resizing built into the WordPress core.
9. Ask the WordPress Community for help
You can disable WP-Cron by editing your wp-config.php and adding the following line;
You can create a cron job and run wp-cron.php every hour using the following command:
Replace www.yourwebsite.com with your web address
The cron job will ensure your WordPress site’s scheduled tasks get completed, such as scheduled posts, WP super cache garbage collection, etc.
10. Use PHP 7
Switching to PHP 7 can dramatically speed up your WordPress website, reducing loading time and freeing up CPU and memory. We recommend testing a staging version of your website with PHP 7 before changing the production version.
11. Increase PHP Memory Limit
Occasionally increasing the amount of memory available to your WordPress website can help fix high CPU errors in WordPress. We recommend increasing your PHP memory to at least 64MB, and recommend 256MB.