How to Reduce High Resource Usage in WordPress
To reduce high resource usage in WordPress, turn on page caching, find and remove the plugins that do the most work on each page load, move WP-Cron to a real server cron job, run a current PHP version and clean up your database. Start with caching: it stops WordPress from rebuilding every page for every visitor.
These steps are for WordPress 7.1 (current release 7.1.4) and the plugin versions available on 6 November 2026. The old version of this page recommended P3 (Plugin Performance Profiler) for finding slow plugins. We checked the wordpress.org plugin directory on 6 November 2026: P3 was closed on 13 October 2022 at its author's request and can no longer be installed. Query Monitor, covered below, is the maintained tool for the same job.
How do you find out what is using your server's resources?
- Check Site Health. Go to Tools > Site Health. The Status tab lists critical issues, such as an outdated PHP version or a failing loopback request, which can stop scheduled tasks from running properly.
- Install Query Monitor. Query Monitor adds a panel to the admin toolbar showing every database query on the current page, with slow, duplicate and failed queries flagged. It groups queries by the plugin or theme responsible, which tells you exactly which plugin is heavy. Open a few typical pages (home, a post, a shop page) and compare.
- Look at your host's statistics. If your control panel shows CPU and memory usage over time, note when the spikes happen. Spikes at the same time every day can point to a scheduled task or a backup plugin.
Remove Query Monitor when you are done. It is a debugging tool, not something to leave running.
Why does page caching reduce resource usage so much?
Without caching, every visit runs PHP and queries the database to build the page. A page cache saves the finished page and serves that copy instead. Use one caching plugin, not several:
- W3 Total Cache: page, object, database and browser caching in one plugin. See our guide to the best W3 Total Cache settings.
- WP Super Cache: simpler. It generates static HTML files that your web server sends to visitors who are not logged in, instead of running WordPress's PHP scripts.
- LiteSpeed Cache: the best choice if your host runs LiteSpeed or OpenLiteSpeed. Its server-level cache only works on those servers; its other features work anywhere. If you run your own server, see how to install WordPress on OpenLiteSpeed.
Do too many plugins cause high resource usage?
The count matters less than what each plugin does. One badly written plugin that runs slow queries on every page can cost more than many small ones together. Use Query Monitor to find the heavy ones, then:
- Deactivate and delete plugins you no longer use. An inactive plugin does not run, but deleting it removes code you would otherwise need to keep updated.
- Replace heavy plugins with lighter ones that do the same job, or with a feature WordPress already has.
- Check that every remaining plugin is still maintained. A plugin closed on wordpress.org gets no fixes.
Should you disable WP-Cron?
On a busy site, yes, but only if you replace it. By default, WordPress checks for scheduled tasks (publishing scheduled posts, update checks, plugin jobs) on page loads, as the WordPress Plugin Handbook explains. Moving that to your server's own scheduler makes the work run at fixed times instead.
- Add this line to
wp-config.php, above the line that says "That's all, stop editing!":define( 'DISABLE_WP_CRON', true ); - In your hosting control panel, create a cron job that requests
https://yoursite.com/wp-cron.phpon a regular schedule. The handbook's example useswget --delete-afterwith your site's URL. - Install WP Crontrol to see every scheduled event, when it last ran and when it is next due. It warns you if events have missed their schedule.
Do not just disable WP-Cron without adding the server cron job. Scheduled posts and theme and plugin auto-updates depend on it.
Does the PHP version affect resource usage?
Yes. WordPress's requirements page recommends PHP 8.3 or greater, with MySQL 8.0 or MariaDB 10.11 or greater. The Site Health documentation notes that newer PHP versions are built with performance in mind. Check your version under Tools > Site Health > Info > Server, and switch to a newer one in your hosting panel. Test on a staging copy first if your theme or plugins are old.
How do you clean up the WordPress database?
Old revisions, auto-drafts, spam comments and expired transients make the database larger and some queries slower.
- Back up first. Database cleanup cannot be undone.
- Limit revisions. WordPress keeps every revision by default. Add
define( 'WP_POST_REVISIONS', 3 );towp-config.phpto keep only the last three, an example taken from the WordPress wp-config documentation. - Clean what is already there. Advanced Database Cleaner removes old revisions, auto-drafts, spam comments and expired transients, with a preview before anything is deleted. WP-Optimize does the same and also includes caching and image compression, so do not run it alongside another caching plugin.
When is it time to change hosting?
If your site still hits its limits after caching, removing heavy plugins, fixing WP-Cron and updating PHP, the site has outgrown the plan. Ask your host which limit you are hitting (for example CPU or memory), then move to a plan or server with more of that resource.
FAQ
What causes high resource usage in WordPress?
Usually pages being built from scratch for every visitor (no caching), one or two heavy plugins, WP-Cron running on page loads, an old PHP version or a bloated database.
Is it safe to disable WP-Cron?
Yes, as long as you add a server cron job that calls wp-cron.php. Without it, scheduled posts and auto-updates stop running.
Which plugin shows which plugin is slowing my site?
Query Monitor. It groups database queries by the plugin or theme responsible and flags slow and duplicate queries.
Should I use more than one caching plugin?
No. Two page caches conflict. Pick one: W3 Total Cache, WP Super Cache or LiteSpeed Cache.

