Plugin how-tos · Guide
How Do You Fix Wordfence High CPU Usage?
Short answer
Fix Wordfence high CPU usage by turning on low resource scanning, switching Live Traffic to Security Only, and running scans at quiet hours. Wordfence scans files and filters every request, so those three changes cut the heaviest work first. If CPU stays high after that, check PHP, memory and hosting limits, because the plan itself may be too small.
Key takeaways
- Low resource scanning spreads a scan over more time and lowers the CPU peak during the scan.
- Live Traffic logging records requests, so Security Only mode cuts the work it adds on busy sites.
- Wordfence 9.1.0 was released on 9 November 2026 with PHP 8.6 support and lighter data syncing.
- WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater, or MySQL 8.4 or greater.
- On the free version a quick scan runs daily and a full scan runs every 72 hours.
- If CPU stays high after tuning, the hosting plan may simply be too small for the site.
What causes Wordfence high CPU usage?
Wordfence high CPU usage usually comes from scans, Live Traffic logging, and firewall checks on every request.
Wordfence is a PHP-based, application-level firewall, so it filters malicious requests on your own server, according to the Wordfence help index. That work uses your CPU on every request it checks.
A scan adds a second load. Wordfence says a scan examines all files on your site for malicious code, backdoors and shells, plus known malicious URLs, on the same Wordfence help index. Large sites have more files to read and hash, so scans run longer and use more CPU.
Live Traffic adds a third load, because it records request data as visitors arrive. Bot traffic makes this worse, since each bot request still passes through the firewall and may be logged.
How do you confirm Wordfence is the cause?
Check when CPU spikes happen, then match the times to scans and traffic before you change any setting.
Open your hosting control panel and look at the CPU graph for the last 24 hours. Note the exact times of each spike, then open Wordfence and check when the last scan ran.
If spikes line up with scan times, the scan is the main suspect. If spikes line up with traffic peaks instead, Live Traffic logging and firewall checks are more likely.
Use Wordfence Diagnostics to check the basics. Wordfence says Diagnostics shows your PHP version, database permissions and connectivity results, so start there before you ask your host for help.
For a clear read on plan limits, see how to read a hosting plan's CPU and RAM limits. It explains what each limit means in plain terms.
What do you need before you start?
You need a WordPress admin login, a current backup, and 30 minutes when traffic is low.
Make a full backup first, including files and the database. Settings changes are small, but a backup lets you undo a mistake fast.
Update Wordfence before you tune it. Wordfence 9.1.0 was released on 9 November 2026, and 9.1.1 followed on 10 November 2026, according to the Wordfence 9.1.0 release post. That release added PHP 8.6 support and lighter attack data syncing that reduces overhead.
Note your current settings before you change them. Write down the scan type, the scan schedule, and the Live Traffic mode, so you can compare results later.
How do you turn on low resource scanning?
Turn on low resource scanning so the scan runs more slowly and uses less CPU at any one moment.
This is the first change to make, because it targets the heaviest single job Wordfence runs. The option is labelled "Use low resource scanning (reduces server load by lengthening the scan duration)" on the Wordfence scan options page.
- Go to Wordfence, then Scan, then Scan Options and Scheduling.
- Find Performance Options on that page.
- Tick “Use low resource scanning”.
- Set “Maximum execution time for each scan stage” to a value your host allows, such as 20 seconds.
- Check “How much memory should Wordfence request when scanning” and leave it at the default unless your host tells you to change it.
- Click Save Changes.
Run one scan after this change and watch the CPU graph. The scan will take longer, but the peak should fall. If the scan still times out, lower the stage time further and ask your host about PHP limits.
How do you change the scan type and schedule?
Use a lighter scan type and run scans at quiet hours, because scan depth and scan timing both drive CPU use.
Wordfence offers Limited, Standard, High Sensitivity and Custom scan types, as listed on the Wordfence scan options page. Limited keeps server load low but checks less, while High Sensitivity checks more and uses more CPU.
| Scan type | Load | When to use it |
|---|---|---|
| Limited | Low | Busy site, or a quick check between full scans |
| Standard | Medium | Normal weekly scanning on most sites |
| High Sensitivity | High | After a suspected hack, or a one-off deep check |
| Custom | Varies | When you need to pick each check yourself |
Use Standard for routine scans and save High Sensitivity for a suspected problem. Running High Sensitivity every day on a small plan will keep CPU high for no gain.
Timing matters too. Wordfence says the scan runs regularly for free users, while Premium customers can adjust how often it runs, on the Wordfence help index.
On the free version, a quick scan runs daily and a full scan runs every 72 hours, according to a Wordfence staff reply on the WordPress.org support forum. That reply also says the full scan cannot be disabled without a Premium licence.
If you have Premium, use “Manually schedule scans” and pick a quiet hour, such as 3 a.m. local time. Check your analytics for the quietest hour first, then set the scan there.
How do you cut Live Traffic logging?
Switch Live Traffic to Security Only so Wordfence logs security events instead of every visit.
Live Traffic shows what is happening on your site in real time, according to the Wordfence help index. That view is useful, but logging every request costs CPU and database writes on a busy site.
- Go to Wordfence, then Tools, then Live Traffic.
- Open Live Traffic Options.
- Set the traffic logging mode to Security Only.
- Save the change.
Since Wordfence 7.2.3, the default traffic mode is already Security Only. If your site was set up earlier, or someone changed it to All Traffic, this step can cut a large amount of logging.
You can also stop Live Traffic with a constant in wp-config.php. Add define('WORDFENCE_DISABLE_LIVE_TRAFFIC', true); above the line that says “stop editing”.
A host knowledge base that quotes Wordfence docs notes that Wordfence says to consider disabling live traffic to reduce load on low-cost plans, on the Tiger Technologies Wordfence page. Use the constant only if you do not need the Live Traffic view at all.
Also lower the amount of Live Traffic data stored. Go to Wordfence, then All Options, then Tool Options, and reduce “Amount of Live Traffic data to store” so old rows are purged sooner.
How do you tighten rate limiting and blocking?
Tighten rate limiting so repeat bot requests are blocked early instead of reaching WordPress again and again.
Wordfence includes a rate limiting firewall that controls how site content can be accessed, according to the Wordfence help index. Rate limits stop one visitor or bot from making too many requests in a short time.
- Go to Wordfence, then Firewall, then Rate Limiting.
- Lower the limit for crawlers first, since aggressive crawlers are a common cause of CPU spikes.
- Set a limit for login attempts and for requests to admin pages.
- Save the changes and watch the CPU graph for 24 hours.
Check Live Traffic after a spike and block the worst IP addresses by hand. Go to Wordfence, then Tools, then Live Traffic, find the address that made the most requests, and block it.
Do not block whole countries or large IP ranges unless you have a clear reason. A wrong block can lock out real visitors, and it does not fix a scan or logging problem.
How do you check PHP, memory and hosting limits?
Check PHP, memory and plan limits next, because tuning Wordfence cannot fix a server that is too small.
WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater, or MySQL 8.4 or greater, as of November 2026, on the WordPress.org requirements page. Older PHP versions are slower and no longer get security fixes.
Check your own numbers in WordPress. Go to Tools, then Site Health, then Info, then Server. That panel lists the PHP version, the database version and the PHP memory limit.
PHP itself sets a default memory limit of 128M in its core settings, according to the PHP manual on core php.ini directives. That is a PHP default, not a WordPress rule, and your host may set a different value.
If PHP is below 8.3, ask your host to move you to a supported version. If the memory limit is below what Wordfence needs for a scan, ask the host to raise it or to move you to a larger plan.
Wordfence 8.0.0, released on 4 November 2024, raised the minimum WordPress version to 4.7 and the minimum PHP version to 7.0, according to the Wordfence changelog. Those are minimums, not targets, so do not treat them as good enough.
For help on the server side, read what PHP workers are. Too few workers can make a scan and normal traffic queue up and look like a Wordfence problem.
How do you know the fix worked?
Compare CPU before and after each change, and run one full scan at a quiet hour to confirm the peak has fallen.
Take a screenshot of the CPU graph before you start. Change one setting at a time, wait 24 hours, then compare the same hours on the next day.
A fix has worked when the scan peak is lower, pages load at normal speed during a scan, and no new timeout errors appear.
Wordfence 7.11.7, released on 29 July 2024, cut scan database queries by about 38% along with CPU usage, according to the Wordfence changelog. An update alone can help, but you still need to check your own numbers.
If CPU is still high after tuning, check for a second cause. A backup plugin, a broken cron job, or a traffic spike can look like a Wordfence problem. For wider speed checks, see how to speed up WordPress.
Also confirm scans still finish. Open Wordfence, then Scan, and check that the last scan shows as complete with a recent date. A scan that never finishes is not a fix, even if CPU looks low.
What mistakes should you avoid?
Do not turn off Wordfence, delete the plugin, or skip scans just to lower CPU.
Turning off the firewall removes protection and leaves the site open to attacks. Wordfence says over 5 million site owners use Wordfence Free, on the Wordfence home page. That number shows how many sites rely on it, but it does not mean the plugin is free of cost in CPU.
Do not set scan memory or stage times to 0 unless you know what 0 means for that field. A 0 can mean no limit, which lets a scan use more CPU, not less.
Do not exclude large folders from scans to make them finish faster. Excluded folders are not checked, so malware there would be missed.
Do not change five settings at once. If CPU falls, you will not know which change helped, and if something breaks, you will not know which change caused it.
If the site is on shared hosting and CPU stays high after every step here, read when to upgrade from shared hosting. A plan upgrade is a real fix when the site has outgrown its limits.
Frequently asked questions
Can Wordfence slow down a site even when no scan is running?
Yes. The firewall checks requests as they arrive, and Live Traffic logging adds database writes on every logged request. Bot traffic makes this worse because each bot request still passes through the firewall. Cut Live Traffic to Security Only, tighten rate limiting, and check the CPU graph at traffic peaks to see if the firewall or logging is the cause.
Is low resource scanning safe to leave on all the time?
Yes. It only changes how fast the scan runs, not what the scan checks. The scan takes longer to finish, but it uses less CPU at any one moment. Leave it on if your site is on shared hosting or a small plan. Turn it off only if you need a scan to finish fast and your server has spare CPU.
Should I run Wordfence scans every day?
For most sites, the free schedule is enough. A quick scan runs daily and a full scan runs every 72 hours on the free version. Running a High Sensitivity scan every day adds CPU load without much gain. Use Standard scans on a routine schedule and save High Sensitivity scans for a suspected hack or a one-off deep check.
What should I do if a Wordfence scan keeps timing out?
First turn on low resource scanning and lower the maximum execution time for each scan stage. Then check Tools, then Site Health, then Info, then Server for your PHP version and memory limit. If the scan still times out, ask your host about PHP limits and cron jobs, and check whether a backup or another plugin is running at the same time.
Will disabling Live Traffic make my site less secure?
No. Live Traffic is a view of requests, not the firewall itself. Switching to Security Only still logs security events, and the firewall still blocks attacks. The constant that disables live traffic also leaves the firewall and scanner working. You lose the real-time view of all visits, but you do not lose protection.
Sources
- Help Documentation Wordfence
- What's New in Wordfence 9.1.0 Wordfence
- Wordfence Scan Options Wordfence
- WordPress Requirements WordPress.org
- Description of core php.ini directives PHP.net
- Wordfence Plugin Configuration Tiger Technologies Support
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.
Thanks — we review requests within 3 business days.
