Part of the guide: Performance cleanup and limits
Heartbeat Control lets you slow down or turn off the WordPress Heartbeat API separately on the dashboard, in the post editor and on the front end. Use it to cut the background requests to admin-ajax.php that keep a busy admin, or a shared hosting account, working hard.
What Heartbeat Control does
While you are logged in, WordPress sends a request from your browser to admin-ajax.php on a timer. This is the Heartbeat API. WordPress uses it to autosave your work in the classic editor, to lock a post while you edit it so a colleague gets a warning instead of overwriting you, and to show the login box again when your session runs out. By default it runs every 15 seconds in the post editor and every 60 seconds on other admin screens.
Every request is a full WordPress load. A few editors with admin tabs open all day can make it the biggest source of admin CPU use on shared hosting. Heartbeat Control gives each of the three places its own choice: Normal (leave it to WordPress), Slow down or Turn off. All the places set to Slow down share one speed: every 15, 30, 60 or 120 seconds.
In the post editor, turning the heartbeat off also turns off post locking, and in the classic editor it stops autosave. Wherever it is off, the "session expired" login box no longer appears. Slowing it down keeps all three and still saves most of the requests, which is why the post editor starts on Slow down.
How to enable it
- Open AdminEase and go to Performance. Click AdminEase in the WordPress admin menu, switch to the Performance tab, and find the Background Activity section.
- Turn on Heartbeat Control. Switch it on. Four more settings appear below it.
- Choose a setting for each place. For Dashboard and other admin screens, Post editor and Front end, pick Normal (WordPress default), Slow down or Turn off.
- Choose the Heartbeat Frequency. This is the speed for every place set to Slow down: every 15, 30, 60 or 120 seconds.
- Save settings. Click Save settings, then reload any admin tabs you already had open. A page that was open before you saved keeps its old speed until it is reloaded.
Settings reference
The defaults below are what each setting starts at the first time you switch Heartbeat Control on.
| Setting | What it does | Default |
|---|---|---|
| Heartbeat Control | The main switch. While it is off, AdminEase leaves the heartbeat entirely to WordPress. | Off |
| Dashboard and other admin screens | Every admin screen except the post editor, including the Customizer. Normal, Slow down or Turn off. | Turn off |
| Post editor | Editing a post or page, and the Add New screen. Turning it off also turns off post locking, and autosave in the classic editor. | Slow down |
| Front end | The public side of your site. WordPress itself does not use the heartbeat there, so this only matters if a plugin or theme does. | Turn off |
| Heartbeat Frequency | How often the heartbeat runs in every place set to Slow down. Every 15, 30, 60 or 120 seconds. | Every 60 seconds |
What happens behind the scenes
Heartbeat Control changes no files on your server. It works through WordPress hooks on each page load, so switching it off undoes everything from the next page load.
- Which place you are in: any page outside the admin is the front end.
post.phpandpost-new.phpare the post editor. Every other admin screen is the dashboard. - Slow down sets both the
intervaland theminimalIntervalthrough theheartbeat_settingsfilter (priority 20). WordPress treats the minimum interval as a floor that no script can go below once the page has loaded, which is why the slower speed also holds in the block editor. - Turn off removes the
heartbeatscript and every script that depends on it, such asautosaveandwp-auth-check, at priority 9999 onadmin_enqueue_scripts,customize_controls_enqueue_scriptsandwp_print_scripts, once every other script has been registered. - Where it is stored: in the AdminEase settings, Performance group, as
heartbeat_control_enabled,heartbeat_dashboard,heartbeat_editor,heartbeat_frontandheartbeat_interval.
Earlier versions had one location choice instead of a setting per place. Until you save AdminEase's settings again, it keeps behaving the way the old choice did, and the three dropdowns show what it means for each place. The first save stores the new settings.
Common setups
- A blog or company site with a few editors: keep the defaults. Dashboard and front end off, post editor slowed to 60 seconds. Autosave and post locking keep working.
- Shared hosting with one person editing: the same, with the post editor slowed to 120 seconds.
- Several people editing the same posts at the same time: set the post editor to Normal, so post locking reacts quickly, and slow the dashboard down instead of turning it off.
- A plugin that uses the heartbeat on the front end (front-end editing or live notifications, for example): set Front end to Slow down or Normal.
Troubleshooting
Autosave stopped working in the classic editor
The post editor is set to Turn off, and classic editor autosave runs on the heartbeat. Set the post editor to Slow down. Autosave Interval, in the same section, then controls how often it saves.
There is no warning when two people open the same post
Post locking needs the heartbeat in the post editor. Set the post editor to Slow down or Normal.
The "session expired" login box no longer appears
That check runs on the heartbeat, so it stops wherever the heartbeat is turned off. You are still asked to log in again the next time you save or change pages.
Requests still arrive every 15 seconds
Reload the page first: a tab that was open before you saved keeps its old speed. If it still happens, check whether another plugin also controls the heartbeat, such as WP Rocket's Heartbeat settings or the separate Heartbeat Control plugin. Keep only one in charge, because the two will overwrite each other.
Something on the front end stopped working
If a plugin relies on the heartbeat on the front end, setting Front end to Turn off breaks it. To check quickly, go to AdminEase > Tools > Safe mode and click Turn AdminEase off for me. For one hour, front-end pages in your browser load as if Heartbeat Control and AdminEase's other cleanup switches were off, without changing anything for your visitors. If the problem goes away, set Front end to Slow down or Normal.
How can I see it working?
Open your browser's developer tools on any admin screen, go to the Network tab and filter for admin-ajax. Each heartbeat shows up as a POST request with action=heartbeat in its data. The gap between two of them is your real speed. Where the heartbeat is turned off, none appear.

