WP-Cron is WordPress’s built-in task scheduler. Plugins and WordPress core use it for jobs such as scheduled posts, update checks, cleanup work, email queues, backups, feed imports, and other background tasks.
It works well for many sites. The performance problem appears when scheduled work is heavy, events are duplicated, a low-traffic site cannot trigger jobs on time, or a busy site asks normal web requests to keep checking for due work.
WP-Cron is not a normal system cron
A traditional system scheduler can run a command at a fixed time whether or not anyone visits the website. WP-Cron is tied to WordPress traffic. When requests arrive, WordPress checks whether scheduled events are due and can start cron processing.
This means a site with no visits may run a scheduled event late. A site with heavy traffic can check often, although WordPress uses locking and spawning behavior to avoid simply running the same work on every page view.
For a small content site with light scheduled tasks, this design can be perfectly fine. Do not replace it just because a speed checklist says “use real cron.”
Know what is scheduled before changing the trigger
Start by listing cron events. WP-CLI can show the hook name, next run, and recurrence with wp cron event list. WordPress admin plugins can also display the event list if you do not use the command line.
Look for hooks that appear far more often than expected, events scheduled every minute without a clear reason, overdue events, and hooks left behind by plugins you no longer use.
Do not delete an unknown hook because its name looks strange. Search the code or plugin documentation and identify the owner first.
Heavy jobs can make normal requests feel slow
A cron event may send mail, process images, generate a backup, import a feed, build search data, call a remote API, clean a database, or work through a large queue. If that job competes for the same PHP workers, CPU, database, or disk as visitors, the site can slow down while it runs.
This is a server-capacity issue as well as a scheduling issue. Read WordPress server performance if CPU, PHP workers, or database load spike during background work.
Duplicate events are a common plugin bug
A plugin should normally check whether its recurring event is already scheduled before adding another copy. Poor code can schedule the same hook repeatedly during page loads or plugin activation. Over time, many copies may run the same task.
If you see duplicate events, fix the plugin or custom code that creates them. Deleting duplicates without fixing the scheduling logic only gives temporary relief.
After a plugin is removed, its cleanup routine should unschedule its events when appropriate. If old hooks remain, confirm the plugin is really gone and remove the stale events carefully.
When a real server cron is useful
A server scheduler is useful when jobs must run at dependable times, the site has very low or uneven traffic, the site has many scheduled tasks, or cron spawning adds avoidable work to visitor requests.
The common setup is to disable the normal visitor-triggered WP-Cron call and ask the server to run WordPress cron on a schedule. The server can call the cron endpoint or use WP-CLI, depending on the host and your setup.
Do not disable WP-Cron before the replacement is working. Otherwise scheduled posts, queues, cleanup tasks, and plugin jobs may stop.
Choose a sensible interval
Running server cron every minute is not automatically better. If the site’s shortest meaningful job interval is fifteen minutes, a one-minute trigger may add needless checks. If an email queue is expected to move quickly, a longer interval may be too slow.
Match the system cron frequency to the site’s real jobs. On shared hosting, also check the provider’s minimum cron interval and resource rules.
WP-Cron intervals are not exact appointment times
WordPress recurring schedules are intervals. A recurring event has a next run time and then repeats based on its schedule. If a run is late because no request occurred or the server was busy, later timing can differ from the wall-clock pattern you imagined.
For tasks that need a strict external schedule, the system scheduler should own the exact timing and trigger a command designed for that task.
Watch long-running queues
Many ecommerce, membership, and mail plugins use their own queue system built on top of WordPress scheduling. A queue can grow if jobs fail, remote services are slow, or the server does not have enough capacity.
Look at failed and pending jobs in the plugin’s own tools. Fix the cause before increasing concurrency. More workers can make the site worse if the database or remote API is already overloaded.
Remote requests inside cron can be the real problem
A scheduled task that calls a slow outside API can occupy a PHP worker for a long time. Timeouts and repeated retries can make the queue grow.
Use logs and a development tool to find slow HTTP requests. Cache safe results, use reasonable timeouts, and move very heavy integrations to a dedicated queue or service when the site requires it.
If similar remote work happens during front-end requests, it can also cause high WordPress TTFB.
Database cleanup jobs can create bursts
Cleanup sounds harmless, but deleting thousands of rows, rotating logs, or rebuilding indexes can use database and disk resources. Schedule heavy maintenance for quieter periods when possible.
Keep retention settings reasonable so cleanup is steady instead of a huge emergency. The database cleanup guide explains why smaller is not always faster and why plugin-owned cleanup tools are safer.
Use WP-CLI to test events
WP-CLI can list events and run due events from the command line. This is useful when a hook appears stuck. Run one known hook in a controlled environment and watch logs, runtime, database load, and errors.
Do not run every due event at once on a production site during peak traffic just to “see what happens.” A large backlog can start many expensive jobs.
Do not hide cron problems with page cache
Page caching can make public pages fast while background work is still unhealthy. Admin requests, REST API calls, checkout, logged-in sessions, and cache misses may still compete with cron jobs for the same server resources.
Use WordPress caching for the layers it can help, but monitor cron and queues separately.
A safe move to system cron
- List current WP-Cron events and identify important jobs.
- Check whether jobs are late, duplicated, or unusually frequent.
- Create the server cron trigger using your host’s supported method.
- Test that due WordPress events run from the server trigger.
- Only then disable the normal visitor-triggered WP-Cron behavior.
- Watch scheduled posts, backups, email queues, and plugin jobs for several cycles.
- Keep logs long enough to catch failures.
If cron work still causes slowdowns after the trigger is moved, the job itself or the server capacity is the next place to investigate. Use the slow-plugin guide when one plugin owns the expensive task.
When to leave WP-Cron alone
Leave it alone when scheduled jobs run reliably, there are no large backlogs, server load is normal, and the site does not need strict timing. Every extra server setting is another thing that can fail later.
Performance work should remove measured problems. It should not replace simple WordPress behavior with a more complex system only because the complex system sounds faster.
Keep a record of expected recurring hooks
After you clean duplicate or stale events, save a short list of the important recurring hooks and their normal intervals. When the site later develops a queue or CPU spike, you can compare the current schedule with a known-good baseline instead of guessing which event is new.
This is especially useful on sites where plugins are added and removed often. Cron problems are much easier to solve when you know what “normal” looked like before the slowdown.
Review that baseline after major plugin installs, migrations, and queue changes. A new recurring task is not automatically bad, but it should have a known owner, a clear purpose, and a frequency that matches the work it performs.
That record also helps after hosting moves, because the trigger method may change while the WordPress hooks stay the same.
Sources and further reading
- Understanding WP-Cron scheduling
- Scheduling WP-Cron events
- WP-CLI cron event list
- WP-CLI cron commands
- WordPress wp-config cron settings
- WordPress schedule event function