What is the WordPress Heartbeat API and how to manage it?

In 2013, WordPress introduced the Heartbeat API, a feature that allows your browser to automatically communicate with the server. If you are using web hosting, you need to carefully check your server's CPU usage. This is because some hosting companies may suspend your account when you exceed the limit.
Here, we'll discuss why the WordPress Heartbeat API is often a suspected factor in causing problems.

What is the WordPress Heartbeat API?

The WordPress Heartbeat API is a protocol that provides communication between the browser and the server using AJAX calls, and has three main functions.

1. Automatic saving and revision: The Heartbeat API automatically saves every 60 seconds when you create or edit a post, so you don't have to worry about accidentally losing content.
2. content lock: In collaborative WordPress sites, it has a post locking feature that prevents you from editing posts that other users are working on. If you're using an eCommerce plugin, this API will also help show you sales happening on your site.
3. Real-time dashboard notifications: With the Heartbeat API, your WordPress backend receives instant notifications of all kinds, whether it's a system update or a plugin alert. In this way, you will be able to keep abreast of the status of your website and react quickly.

The default communication interval for Heartbeat API is 15 seconds, but developers can customize this interval to make the data exchange more in line with their needs.Heartbeat API is the magic tool to make WordPress website management smarter and more efficient.

Why limit the WordPress Heartbeat API?

While it's nice to have an autosave feature and real-time data notifications, it has implications for a very limited pool of server resources.

Heartbeat API using /wp-admin/admin-ajax.phpThe file sends an AJAX request (POST request). Each request to execute a PHP file is equal to the CPU time on the server.

This may result in a large number of requests being sent to the hosting server, leading to high CPU utilization.

As we mentioned before, this can be a problem for webmasters using hosting. High CPU usage can eventually lead to account suspension when you reach your quota limit. Therefore, we have the option of using the GTmetrix plugin to monitor and analyze site performance and fix spikes in managed ajax files.

What to consider before stopping the Heartbeat API?

If you're considering stopping using the Heartbeat API altogether, think twice.

If there is no WordPress Heartbeat API, before you forget to click "Save Draft"button, all the changes you made in the post will be lost. And you will no longer be able to access theRevisions in WordPressThe

If you install the WordPress plugin that uses the Heartbeat API, you will also not be able to display real-time notifications and messaging features on your website.

However, if you are an individual workstation and all these features are not important to you, then you can go ahead and stop the WordPress Heartbeat API.

Otherwise, you may want to consider taking control of the Heartbeat API.

How can I limit the WordPress Heartbeat API using a plugin?

You can use theHeartbeat ControlThe plugin controls how often the Heartbeat API sends callbacks to the server.

After installing and activating the plugin, go toSettings -> Heartbeat Control Settings. Here you can set it up for the API.

• heartbeat behavior- Allows you toEnable Heartbeat,Disable HeartbeatmaybeModify heartbeat
• placement- Determine from which region you want to control the API; it gives you three options:WordPress Dashboard,Frontendrespond in singingPost Editor
• frequency- The number of times you are allowed to call back for each identified location. The range of values is 15 to 300 seconds

Example: This is a practical approach if you have multiple authors working on the same WordPress site and we limit the frequency of the Heartbeat API function in the editor to 200 seconds.

The plugin also allows you to completely disable the WordPress Heartbeat API. you can do this via theFor "Heartbeat Settings," select "Disable Heartbeat."to perform this operation.

How to stop Heartbeat API completely without plugin?

You can also add this code snippet to the functions.php of the active theme by adding it to thefile to stop the Heartbeat API without a plugin.

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

This should be done if you are the only person using the site and do not need to install other plugins that use this API.

From the WordPress dashboard, go toAppearance -> Theme File Editor. Make sure you are editing the active theme of the site. From the right navigation menu, clickTheme functions (functions.php) . Paste the code snippet above into the start<?phpAfter marking, then clickUpdate FileThe

That's it, now you have successfully disabled the WordPress Heartbeat API on your site.

summarize

You've already learned about the functionality that the Heartbeat API provides for your website. While it is beneficial for websites, in a hosted environment, but handled poorly, it can lead to a number of other larger issues.

Therefore, to reduceWordPressCPU utilization on the server, you can control the API or disable it altogether. Additionally, you can use plugins or manually add code to thefunctions.phpfile to accomplish this.