WordPress Heartbeat API High CPU or admin-ajax Errors
The Heartbeat feature can raise server load in the editor. Slow it down instead of breaking it.
Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
What it is
Heartbeat sends background requests while you edit, to autosave and keep sessions alive. Many open editor tabs multiply those calls.
Reduce the load
- Close unused editor and dashboard tabs.
- Use a plugin or snippet to slow the interval (for example, to 60 seconds) and limit it outside the post editor. Do not turn off autosave entirely, so you do not lose work.
- Check which plugin is making admin-ajax calls in the browser's network tab. See reading the browser console.
- Check hosting CPU graphs for spikes.
Related
See WooCommerce Slow Because of admin-ajax.php and Cart Fragments and WordPress Dashboard (wp-admin) Is Very Slow: Causes and Fixes.
Related guides
- WordPress High CPU Usage From wp-cron.php: How to Reduce It
- WordPress Site Is Slow: Practical Steps to Speed It Up
- WordPress Site Slow After an Update: Find the Cause
- WordPress Site Health Says a Persistent Object Cache Is Recommended: What It Means
Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.