How To Disable/Limit The WordPress Heartbeat API Manually Or With Plugins

The WordPress Heartbeat API should usually be disabled (or limited) because it consumes server resources.

However, WordPress Heartbeat is run on the frontend, backend, and editor. I would keep the backend heartbeat on, then limit the frontend/editor heartbeat by increasing the frequency to something like 60-120 seconds.

At the cost of server resources, the Heartbeat API uses /wp-admin/admin-ajax.php to run AJAX calls from the browser. In turn, it is able to show you real-time plugin notifications, when other users are editing a post (this sends a request every 15 seconds), and other unneeded features.

The easiest way to disable WordPress Heartbeat is to install the Heartbeat Control plugin, view the settings, and modify the Heartbeat interval in the dashboard, frontend, or post editor, or disable it completely. Other methods include adding a few lines of code to your functions.php file or using a plugin that already has an disable Heartbeat option like WP Rocket or LiteSpeed.

What Does The WordPress Heartbeat API Do?

• Shows real-time plugin notifications
• Shows when other users are editing a post
• Shows when users are locked out for being idle
• Creates periodic auto saves, drafts, and revisions
• Shows real-time sales data when using eCommerce plugins

Important: always make sure you save your drafts when editing! If you disable the Heartbeat API and have auto drafts and post revisions turned off, you could risk losing all your hard work.

 

1. Install The Heartbeat Control Plugin

The easiest way to disable the WordPress Heartbeat API is with the Heartbeat Control plugin. Once installed, go to the General Settings and you can disable Heartbeat in the WordPress dashboard, frontend, and the post editor. Ideally, it is recommend you disable it everywhere.

If you don’t want to disable Heartbeat and limit it instead, you can modify Heartbeat and choose your own intervals. By default, the WordPress heart beats once every 15 seconds.

 

2. Manually Disable The WordPress Heartbeat API

To disable the WordPress Heartbeat API without a plugin, go to Appearance > Theme Editor, then edit the functions.php file of your theme. Next, paste the code right after the <?php tag:

add_action( 'init', 'stop_heartbeat', 1 );
function stop_heartbeat() {
wp_deregister_script('heartbeat');
}

 

3. Disable Heartbeat With WP Rocket

If you’re already using WP Rocket, they also have an option to disable or limit Heartbeat. One major advantage of WP Rocket is that it comes with more built-in speed optimizations than other cache plugins. This not only means less plugins running on your WordPress site, but better speed optimizations and GTmetrix scores. That’s why it’s usually #1 in Facebook polls.

 

5. Disable Heartbeat With LiteSpeed Cache

If you’re using the LiteSpeed Cache plugin, they also have an option to disable WordPress heartbeat in Toolbox → Heartbeat. You can edit the frontend, backend, and editor heartbeat.

 

6. Disable Heartbeat With Perfmatters

You can also use the Perfmatters Plugin (by Kinsta) to disable the WordPress Heartbeat. This plugin also lets you selectively disable plugins, scripts, and styles from loading on certain pages, limit post revisions, and disable many unnecessary things in the WordPress admin. I use it on my own website and like to say “it takes care of the last 10% of your WordPress speed.”

 

What’s Next?

I have some great resources on WordPress speed optimization:

• How I Got 100% GTmetrix Scores
• WordPress Speed Optimization YouTube Video
• Optimizing External Scripts

And many more which you can find below.

Hope this was helpful! Comment if you need any help at all.

Cheers,
Tom