Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix High CPU Usage in WordPress

Short answer

High CPU usage in WordPress usually comes from a heavy plugin, repeated WP-Cron or Heartbeat requests, a security scan, or pages with no cache. Find the cause with Query Monitor and your host CPU graph, then fix that cause first. Start with the plugin or task that uses the most CPU, not with a larger hosting plan.

Key takeaways

  • A heavy plugin is the most common cause, and Query Monitor shows which plugin caused the most query time.
  • WP-Cron checks for due jobs on every visit, so a real server cron job every 5 or 15 minutes cuts that work.
  • Heartbeat sends requests every 15 to 60 seconds, so raising the interval to 60 seconds cuts admin-ajax.php load.
  • Set each Wordfence scan stage to 15 seconds and turn on low resource scanning to lower peak CPU.
  • A page cache serves saved HTML instead of building each page with PHP, which removes most repeat CPU work.
  • Change one thing at a time and compare host CPU before and after, or you cannot tell which fix helped.

What does high CPU usage mean in WordPress?

High CPU usage means WordPress is asking the server processor to do more work than the plan allows.

CPU usage is the share of processor time your site uses. Your host sets a limit for your plan, and WordPress uses CPU each time PHP builds a page or runs a database query.

When that work stays above the limit, pages load slowly and the host may throttle the site. A short spike during a backup or scan is normal, but a steady high line means something runs on every visit or far too often.

What usually causes high CPU usage in WordPress?

A heavy plugin, a busy cron schedule, repeated admin-ajax.php calls, a security scan, or uncached pages cause most high CPU usage.

A plugin can run slow database queries on every page. WP-Cron can start background work on page visits.

The Heartbeat API can send repeated requests from open admin tabs. A security scan can read thousands of files at once. Uncached pages force PHP to build each page from scratch.

CauseUsual signFirst check
Heavy plugin or themeSlow pages after an updateQuery Monitor, Queries by Component
WP-CronSpikes at set timesTools → Site Health, scheduled events
Heartbeat APIMany admin-ajax.php requestsAccess log, open admin tabs
Security scanSpikes during a scanWordfence → Scan activity log
No page cacheEvery visit hits PHPCache plugin or host cache status
Bot trafficSudden request surgeHost analytics, access log

How do you find what is using the CPU?

Start with your host graph, the access log, and Tools → Site Health, then confirm the cause with Query Monitor.

Open your host dashboard and note when CPU rises. A rise that matches a scan, a backup, or a traffic peak points to that event.

Next, open Tools → Site Health → Status. Site Health checks whether scheduled events run as intended, and it reports a failed or late event when WP-Cron is not working.

The Site Health scheduled events test says a failed event may mean WP-Cron is not working or orphaned events remain from older code.

Then look at the access log for repeated requests to wp-cron.php and wp-admin/admin-ajax.php. Many entries for those two files point to cron or Heartbeat work.

Note the times before you change anything, so you can compare them after the fix. For plan limits, see how to read a hosting plan's CPU and RAM limits.

How do you find a heavy plugin with Query Monitor?

Install Query Monitor, load a slow page as an admin, and open Queries by Component to see which plugin caused the most query time.

Query Monitor is the developer tools panel for WordPress and WooCommerce. It shows database queries, PHP errors, hooks, enqueued scripts, and HTTP API calls for the current page.

It groups database queries by the plugin, theme, or function that caused them, so you can spot a poorly performing plugin fast. Version 4.1.1 was released on 27 October 2026, and the plugin page says it is actively tested up to PHP 8.5 as of November 2026.

Follow these steps on a staging copy first when you can.

  1. Go to Plugins → Add New, search for “Query Monitor”, install it, and activate it.
  2. Load a slow page while logged in as an admin.
  3. Click the Query Monitor menu in the admin toolbar and open the Database Queries panel.
  4. Open Queries by Component and sort by total time.
  5. Open Slow Queries and Duplicate Queries to see single slow queries and queries that repeat on one page load.

A plugin that owns a large share of total query time is your first suspect. Query Monitor only shows output to admins on a single site by default, and it does not store the data it collects.

It adds a small amount of load itself, so deactivate it when you finish. If the heavy plugin is not needed, remove it.

How do you fix high CPU from WP-Cron?

Replace page-load WP-Cron with a real server cron job that runs every 5 or 15 minutes.

WP-Cron is not a real clock-based scheduler. The WordPress PHP handbook says wp-cron.php checks on every visit whether a job is due, and those checks consume time and produce load.

On a busy site, that check runs on many visits. On a quiet site, jobs run late because no visit triggers them.

Do both steps below. Disabling WP-Cron without a replacement stops scheduled posts, update checks, and plugin tasks.

  1. Back up the site first, using your host backup or a backup plugin.
  2. Open wp-config.php and add this line above the “stop editing” comment: define( 'DISABLE_WP_CRON', true );
  3. Add a server cron job in your host panel that calls wp-cron.php every 5 or 15 minutes.
  4. Use the command form your host documents, such as a wget call to your site's wp-cron.php address.

The WordPress plugin handbook on WP-Cron gives the same two-part method: set up the system task scheduler, then disable WP-Cron in wp-config.php so page loads no longer trigger it.

After the change, check Tools → Site Health → Status and confirm that scheduled events are running. For the wider picture on workers and load, see how many PHP workers a WordPress site needs.

How do you slow down the Heartbeat API and admin-ajax.php?

Raise the Heartbeat interval to 60 seconds or turn Heartbeat off where you do not need it.

The Heartbeat API is the WordPress system that sends periodic requests to admin-ajax.php for autosave, post locking, and login status.

The Heartbeat Controller plugin page says it sends requests every 15 to 60 seconds, and frequent calls can cause high CPU use, mainly when several admin tabs stay open. Its minimum interval is 15 seconds, so 15 seconds is the fastest setting, not a target to aim for.

Use one of these options.

  • Install a Heartbeat control plugin, then set the dashboard interval to 60 seconds and the front-end interval to 60 seconds or off.
  • Close admin tabs you are not using, and log out of extra sessions.
  • If a plugin makes its own admin-ajax.php calls on every page, check that plugin's settings for a refresh or polling interval.

Do not turn Heartbeat off everywhere without a reason. Autosave and post locking stop working when Heartbeat is off in the editor.

A 60-second interval keeps those features working while cutting the request count to a quarter of the 15-second rate. Kinsta's performance troubleshooting guide lists high admin-ajax.php use as a first check, and it links that use to plugins and to many logged-in users triggering Heartbeat calls.

How do you fix high CPU from Wordfence scans?

Set each Wordfence scan stage to 15 seconds, turn on low resource scanning, and stop scanning files you do not need to scan.

Wordfence scans read files and database rows on your own server, so a full scan is heavy work. The Wordfence support team on WordPress.org advises a PHP max_execution_time of 30 or 60 seconds, because Wordfence uses about half of that value by default.

It also advises setting Maximum execution time for each scan stage to 15 seconds and keeping Use low resource scanning turned on, so the scan spreads over more time at a lower peak. Low resource scanning makes the scan take longer, but it lowers the load at any one moment.

Follow these steps in WordPress admin.

  1. Go to Wordfence → Scan → Scan Options and Scheduling.
  2. Under Performance Options, set Maximum execution time for each scan stage to 15.
  3. Turn on Use low resource scanning.
  4. Keep the total scan time limit near 3 hours, which is 21600 seconds, unless your host advises a different value.
  5. Under Advanced Scan Options, leave Scan images, binary, and other files as if they were executable turned off unless you have a reason to scan those files.
  6. Add cache paths to the excluded files list, such as wp-content/cache/*, when your cache plugin stores files there.

Also check Wordfence → Tools → Live Traffic. Logging every visit writes many rows to the database. Switch Live Traffic to Security Only when you do not need a full visit log.

Wordfence 9.1.0 was released on 9 November 2026, with a follow-up 9.1.1 release on 10 November 2026, according to Wordfence, so update Wordfence before you tune it. If scans still strain the plan, run them at a quiet hour. For a full Wordfence-specific walkthrough, see how to fix Wordfence high CPU usage.

How does caching and a persistent object cache lower CPU?

A page cache serves a saved HTML copy instead of building the page with PHP, and a persistent object cache cuts repeat database reads.

Without a page cache, every logged-out visit runs PHP and database queries to build the page. With a page cache, later visits get the saved copy. Turn on your host cache or a cache plugin, then test a logged-out page and confirm the response comes from cache.

A persistent object cache is a second layer. The WordPress optimization handbook says a persistent object cache saves trips to the database, because data such as site options would otherwise be read from the database on every page view.

Your host must offer a cache server, and you then install an object cache plugin that supports it.

WordPress also has memory limits that shape this work. The PHP handbook says the WordPress default WP_MEMORY_LIMIT is 40 MB, the multisite default is 64 MB, and WP_MAX_MEMORY_LIMIT for the admin area is 256 MB. PHP's own memory_limit setting defaults to 128M and caps how much memory a script may allocate, according to the PHP manual.

Raising memory does not fix high CPU on its own. For memory and plan size, see how much RAM WordPress needs.

How do you check that the fix worked?

Compare the same numbers before and after: host CPU, admin-ajax.php requests, query time, and page load time.

Wait at least 30 minutes after each single change, then check these four items.

  • Host CPU graph: the peak should fall, and the line should stay below the plan limit during normal traffic.
  • Access log: requests to wp-cron.php and admin-ajax.php should fall after the cron and Heartbeat changes.
  • Query Monitor: total query time and query count on the same slow page should fall after the heavy plugin fix.
  • Site Health: Tools → Site Health → Status should show that scheduled events are running.

Change one thing at a time. If you change the cron setup, Heartbeat, and a plugin in one go, you cannot tell which change helped.

Keep a short note with the time, the change, and the CPU reading before and after. If CPU stays high after the plugin, cron, Heartbeat, scan, and cache checks, the cause may be traffic volume or a plan limit.

That is the point to ask the host for the top processes by CPU. For a slow-host check, see how to tell if your host is slowing WordPress down.

When should you contact your host?

Contact your host when CPU stays high after you fixed the plugin, cron, Heartbeat, scan, and cache causes, or when you cannot change a server setting.

Ask the host for three facts: the top processes by CPU in the last 24 hours, the exact limit on your plan, and whether the limit is CPU seconds, cores, or PHP workers.

Send the host the times of the spikes and the changes you already made, so the support team does not repeat your checks.

Ask about a plan change only after the host names the limit you hit. More CPU helps when traffic is real and the code is already lean. It does not help when a single plugin or scan still burns most of the CPU, because that work will grow to fill the new limit too.

What mistakes should you avoid?

Do not disable WP-Cron without a replacement, do not raise PHP timeouts to fix a slow scan, and do not change several settings at once.

  • Disabling WP-Cron alone stops scheduled posts, update checks, and backups from running.
  • Raising max_execution_time to several hundred seconds does not fix a slow Wordfence scan; it lets one bad scan run longer.
  • Deleting a plugin without a backup can break a feature you need, and it hides the cause instead of fixing it.
  • Leaving Query Monitor active on a busy live site adds load of its own, so deactivate it after the check.
  • Turning off Heartbeat everywhere breaks autosave and post locking in the editor.
  • Clearing the whole cache during a traffic peak forces PHP to rebuild every page at once, so clear it at a quiet time.

Frequently asked questions

What causes high CPU usage in WordPress most often?

A heavy plugin, WP-Cron, Heartbeat requests, a security scan, or uncached pages cause most cases. A plugin can run slow database queries on every page, while WP-Cron and Heartbeat add background PHP work. Check Query Monitor first, then your host CPU graph and access log, so you fix the cause that uses the most CPU instead of guessing.

Is it safe to disable WP-Cron in WordPress?

It is safe only when you add a real server cron job at the same time. Disabling WP-Cron without a replacement stops scheduled posts, update checks, backups, and plugin tasks from running. Add the DISABLE_WP_CRON line to wp-config.php, then set a server cron job to call wp-cron.php every 5 or 15 minutes and check Site Health afterwards.

Does the Heartbeat API really use a lot of CPU?

It can, mainly when many admin tabs stay open or many users are logged in at once. Heartbeat sends requests every 15 to 60 seconds to admin-ajax.php for autosave and post locking. Raising the interval to 60 seconds cuts those requests sharply while keeping autosave working. Turning it off in the editor stops autosave and post locking.

Why does Wordfence use so much CPU?

Wordfence scans read files and database rows on your own server, so a full scan is heavy work. Live Traffic logging adds more database writes when it records every visit. Set each scan stage to 15 seconds, turn on low resource scanning, and switch Live Traffic to Security Only. Run scans at a quiet hour when you can.

Will a cache plugin fix high CPU usage?

A page cache helps a lot when most visits are logged-out readers, because it serves saved HTML instead of building each page with PHP. It does not fix a heavy plugin, a bad cron schedule, or a scan that runs during busy hours. Fix the cause first, then use caching to cut the repeat work that remains.

When should I upgrade my hosting plan for high CPU?

Upgrade only after you have fixed the plugin, cron, Heartbeat, scan, and cache causes and CPU stays high during real traffic. Ask your host for the top processes by CPU and the exact limit you hit. A larger plan helps real traffic on lean code, but it does not fix a single plugin or scan that burns most of the CPU.

Sources

  1. Hooking WP-Cron Into the System Task Scheduler WordPress Developer Resources
  2. PHP Optimization WordPress Developer Resources
  3. Query Monitor WordPress.org
  4. Optimization WordPress Developer Resources
  5. Troubleshooting Performance Kinsta Docs
  6. Heartbeat Controller WordPress.org
  7. Website too slow when Wordfence is active WordPress.org Support
  8. What's New in Wordfence 9.1.0 Wordfence

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test