Heartbeat Control Alternative: What It Really Does, and What to Use Now

Heartbeat Control has not been updated since August 2023. What it really does, the editor catch inside its Dashboard rule, and how to move to AdminEase.

Search the docs

⌘ K
Try "heartbeat", "restore from S3", or "WP-

Popular

License activation

WP-CLI install

Restore a backup

Hooks reference

Heartbeat Control by WP Rocket runs on 70,000 WordPress sites, but it has not been updated since 31 August 2023 and is only tested up to WordPress 6.3. If you are looking for a Heartbeat Control alternative, this page covers what the plugin really does, where it falls short today, and how to move its three settings to AdminEase, for free, in about five minutes.

The short version

Nothing is on fire. Heartbeat Control still loads on current WordPress, and we found no published vulnerability for it. But nobody is looking after it, and one of its rules does not do what most people think it does.

  • Still works: slowing down or stopping the heartbeat on the dashboard, the front end and the post editor.
  • The catch: its Dashboard rule also covers the post editor. "Disable on the dashboard, keep it in the editor" switches it off in both.
  • The alternative: AdminEase, free, has the same three places, keeps the post editor separate, and its slower speed holds in the block editor.
  • Verified: 24 October 2026, against Heartbeat Control 2.0.1 and AdminEase 2.6.0.
On this page
  1. What the Heartbeat API does
  2. What Heartbeat Control does, and where it stands
  3. Where it falls short today
  4. A Heartbeat Control alternative, setting by setting
  5. How to switch in five minutes
  6. When to keep what you have
  7. Troubleshooting

1. What the Heartbeat API does

While you are logged in, WordPress keeps a quiet line open between your browser and your server. Every so often the browser sends a request to admin-ajax.php, and 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 that request goes every 15 seconds in the post editor and every 60 seconds on other admin screens.

Each request is a full WordPress load. One person with one tab open costs nothing worth measuring. Several editors with a few admin tabs open all day, on shared hosting, can be the biggest source of admin CPU use on the account. That is why people slow it down, or switch it off where nothing needs it. If your admin is slow and you are not sure the heartbeat is the reason, the slow admin guide helps you find the real cause first.

In the post editor, slow beats off Turning the heartbeat off in the post editor also turns off post locking, and in the classic editor it stops autosave. Slowing it down keeps both and still saves most of the requests.

2. What Heartbeat Control does, and where it stands

Heartbeat Control is made by WP Media, the company behind WP Rocket. It gives you one rule for each of three places: the WordPress Dashboard, the Frontend and the Post editor. Each rule is Allow, Disable or Modify, and Modify adds a slider from 15 to 300 seconds. Out of the box, all three are set to Allow.

Its wordpress.org listing on 24 October 2026:

Version 2.0.1 Active installs 70,000+ Rating 4.2 out of 5 (68 ratings) Last updated 31 August 2023 Tested up to WordPress 6.3

WordPress has moved on to 7.1 since then. An untested plugin is not automatically broken, and this one is small and simple, which works in its favour. But nobody is checking it against new WordPress releases, and nobody is fixing what follows.

If you use WP Rocket, you may not need either plugin WP Rocket has the same control built in, under Settings › WP Rocket › Heartbeat, with a choice for the backend, the post editor and the front end. If WP Rocket is already on your site, use that and remove the standalone plugin. Whatever you choose, run one heartbeat control, never two.

3. Where it falls short today

We read the plugin's code (version 2.0.1) before writing this section. Three things stand out.

  • The Dashboard rule covers the post editor too. The plugin decides whether a screen is "the dashboard" by checking whether it is any admin screen at all, and the post editor is an admin screen. So when the Dashboard rule is set to Disable, the heartbeat is switched off in the post editor as well, whatever the Post editor rule says. The most common advice, "disable it on the dashboard, keep it in the editor", gives you the first half and quietly drops the second.
  • The Post editor rule only covers editing an existing post. It matches one screen, post.php. The Add New screen, where you write a new post, is ruled by the Dashboard setting instead.
  • Its custom speed can be overridden. Modify sets the heartbeat's starting interval, and nothing else. Any script on the page can change that interval later. WordPress has a second value, the minimum interval, which scripts cannot go below once the page has loaded, and Heartbeat Control does not set it. AdminEase had exactly this problem until version 2.5.0, when slowing the heartbeat down started working in the block editor.
We read the code, so check your own site too The first two points come straight from the plugin's own code, in the check it uses to decide which screen it is on. If your Dashboard rule is set to Disable and you count on post locking, or on autosave in the classic editor, open a post and check that they still work. Section 7 shows how to watch the heartbeat requests yourself.

4. A Heartbeat Control alternative, setting by setting

AdminEase is ours, so here is the careful version. Its Heartbeat Control is in the free plugin, on the Performance tab, and it covers the same three places with the same three choices:

HEARTBEAT CONTROL ADMINEASE (Performance tab) WordPress Dashboard Dashboard and other admin screens Frontend Front end Post editor Post editor (editing and Add New) Allow Heartbeat Normal (WordPress default) Disable Heartbeat Turn off Modify Heartbeat Slow down Frequency, 15 to 300 sec Heartbeat Frequency: 15, 30, 60 or 120 sec One speed per place One speed for every place set to Slow down

Two differences go in Heartbeat Control's favour, and you should know them before you switch:

  • The slowest speed is 120 seconds. If you had a place on Modify at more than 120, the closest AdminEase setting is 120, which is still half as often as WordPress's 60-second default.
  • One speed for every slowed place. If you had different speeds for different places, pick the one that matters most. For most sites that is the post editor.

Two differences go the other way. The post editor setting covers both editing and Add New, and the dashboard setting never overrides it. And Slow down holds in the block editor.

These are the settings and what they start at when you first switch the feature on:

SETTING CHOICES STARTS AT Heartbeat Control on, off off Dashboard and other admin screens Normal, Slow down, Turn off Turn off Post editor Normal, Slow down, Turn off Slow down Front end Normal, Slow down, Turn off Turn off Heartbeat Frequency 15, 30, 60 or 120 seconds 60 seconds
Behind the scenes AdminEase works out the place from the screen itself: any public page is the front end, post.php and post-new.php are the post editor, and every other admin screen is the dashboard. Slow down sets both the interval and the minimum interval through the heartbeat_settings filter, which is why the block editor cannot speed it back up. Turn off removes the heartbeat script, and every script that depends on it (autosave and the session-expired login check among them). It does this late in page loading, once every other script has been registered.

5. How to switch in five minutes

Step 1: Write down your current settings Open Settings › Heartbeat Control and note the rule for each of the three places, and the frequency on any that are set to Modify.
Step 2: Install AdminEase Go to Plugins › Add New Plugin, search for AdminEase, then install and activate it. The installation guide covers the details, and it is also on wordpress.org.
Step 3: Switch on Heartbeat Control Open AdminEase › Performance and turn on the Heartbeat Control switch. Four more settings appear below it.
Step 4: Set the three places Use the table in section 4 to copy your old rules across. If you are starting fresh, keep what AdminEase starts with: the dashboard and the front end turned off, and the post editor slowed down.
Step 5: Choose the speed Set Heartbeat Frequency for the places on Slow down. 60 seconds is a safe start for the post editor. Autosave and post locking keep working, just less often.
Step 6: Save, then deactivate Heartbeat Control Click Save settings. Then go to Plugins › Installed Plugins, deactivate Heartbeat Control and delete it. Two plugins changing the same heartbeat give you whichever one runs last, which is hard to predict.
Step 7: Reload your open admin tabs A page that was already open keeps its old speed until you reload it. Reload any admin tabs you had open, and the new settings apply.

6. When to keep what you have

Switching is not always the right call:

  • You already run WP Rocket. Use its built-in Heartbeat settings and remove the standalone plugin. You do not need AdminEase for this.
  • You need a speed slower than 120 seconds, or a different speed in each place. Heartbeat Control still offers both, as long as you keep the Dashboard caveat from section 3 in mind.
  • You only want this one switch. AdminEase is a toolkit with many settings. Its Heartbeat Control is one switch on one tab and stays off until you turn it on, but if a single-purpose plugin is what you want, that is a fair reason to stay.

7. Troubleshooting

  • Autosave stopped in the classic editor. The post editor is set to Turn off. Set it to Slow down instead. The Autosave Interval setting explains how the two depend on each other.
  • No warning when two people open the same post. Same cause: post locking needs the heartbeat in the post editor.
  • The "session expired" login box no longer appears. That check runs on the heartbeat, so it goes wherever the heartbeat is turned off. WordPress still asks you to log in again the next time you save or change pages.
  • Requests still arrive every 15 seconds. Reload the page first: an open tab keeps its old speed. If it still happens, check whether another plugin controls the heartbeat too, such as WP Rocket or the old Heartbeat Control.
  • How to watch it yourself. Open your browser's developer tools on any admin screen, go to the Network tab and filter for admin-ajax. Each heartbeat request shows up as a POST with action=heartbeat in its data. The gap between them is your real speed.

Where to go from here

If Heartbeat Control is on your site, start by checking what its Dashboard rule is set to. If it says Disable, your post editor has no heartbeat either, and you may not know it. From there, either fix the rules in place, move the setting into WP Rocket if you already pay for it, or switch to AdminEase and get the post editor back as a separate choice. Whichever you pick, keep exactly one plugin in charge of the heartbeat.

Frequently asked questions

Is Heartbeat Control abandoned?

WP Media has not said so. The facts are that its last update was on 31 August 2023 and it is only tested up to WordPress 6.3. Whether that counts as abandoned is a judgement call, but nobody is checking it against new releases.

Is it unsafe to keep it?

We found no published vulnerability for Heartbeat Control. The risk is compatibility with new WordPress versions, not a known security hole. It is a small plugin with little code, which keeps that risk low.

Can AdminEase import my Heartbeat Control settings?

Not today. You set them by hand, which is three dropdowns and a speed, using the table in section 4.

What is the slowest speed in AdminEase?

120 seconds. Heartbeat Control's slider goes up to 300.

Does slowing the heartbeat down work in the block editor?

In AdminEase, yes, since version 2.5.0. It sets the minimum interval as well as the interval, and the block editor cannot go below the minimum.

Do I need AdminEase Pro for this?

No. Heartbeat Control is in the free AdminEase plugin on wordpress.org.

Was this article helpful?

On this page
Back to top
Copy link to article