Troubleshooting guide

WordPress High CPU Usage: Server-Level Causes and Fixes

Diagnose WordPress high CPU usage from PHP-FPM, plugins, cron, bots, database queries, WooCommerce and caching problems.

Remote support availableCommercial systemsService: WordPress Speed Optimisation
WordPresshigh CPUPHP-FPMMySQLCloudflare

What this problem usually means

WordPress high CPU can come from PHP execution, database load, bots, plugins, theme code, cron jobs, WooCommerce actions, or cache misses. The fix is usually a combination of server-level checks and application-level cleanup.

Production caution: Installing more caching plugins without checking server logs can make diagnosis harder. Start by finding whether CPU is PHP, database, bots or background jobs.

Common symptoms

  • CPU spikes during normal browsing
  • Admin area is slow
  • Checkout or cart pages hang
  • Hosting account hits resource limits
  • PHP-FPM or MySQL uses most CPU

Common causes

  • No full-page cache or object cache where appropriate
  • Heavy plugins or page builders
  • wp-cron running too often
  • Bot traffic hitting expensive endpoints
  • Slow database queries and bloated tables
  • WooCommerce sessions, carts or checkout actions under load

Safe first checks

These checks are intended to help identify the direction of the issue. Always adjust paths, service names and commands for your environment.

Check top processes

top -o %CPU

Check PHP-FPM and web logs

tail -100 /var/log/nginx/access.log /var/log/nginx/error.log

Look at WordPress cron

wp cron event list --due-now --path=/path/to/site

Check database activity

mysqladmin processlist

Typical fixes

  • Identify heavy URLs and bot traffic in access logs
  • Tune PHP-FPM workers to avoid overload
  • Use Redis/object caching where useful
  • Disable or reschedule expensive cron tasks
  • Optimise database tables and slow queries
  • Use Cloudflare or NGINX caching carefully for safe pages

When to get help

Get help if the system is production-facing, customer data is involved, backups are uncertain, or the issue affects revenue, security or uptime. We can review the logs, confirm the cause and quote a fixed-scope fix where appropriate.

Need this fixed?

Get remote support for this issue.

Fixed technical support starts from $499. Emergency incident support is $199/hr with a minimum window.

Contact Us

Related guides