WordPress Hearbeat is an API that was introduced in early WordPress version. It sends continuous beats or pulse to perform time-to-time tasks. Browsers will then communicate with the server in real-time and provide information quickly to the WordPress Dashboard.
It will allow WordPress to tell you when other authors are editing a post or page, or plugins can use the HearBeat API to show you notifications real-time.
Why You Should Control WordPress HeartBeat API
If the HeartBeat API is not controlled, it can increase your CPU usage, slow down your website, and your usage of the allocated resources will reach its threshold. This usually affects WordPress website with multiple administrators or editors; basically, anyone with a backend access to WordPress. When there are multiple backend users navigating or simply idling at the WordPress admin pages, the number of pulse or ticks generated from the API increases as well. You may get issues with the limits with the number of processes for such cases.
How to Control the HeartBeat API
We recommend installing the HeartBeat Control plugin and apply the recommended settings below to allow you to control the pulses generated by the API. Follow the steps below:
Step 1. Login to your WordPress website.
Step 2. Hover mouse on Plugins and choose Add New.
Step 3. Search for HeartBeat Control on the Search Bar then click Install Now.
Step 4. Once it’s installed click on Activate button.
Step 5. Once the plugin is activated, hover your mouse to Settings and click Heartbeat Control Settings.
Step 6. Remove all default rules generated from the plugin. Then add these rules.
Step 7. Click Save Changes.
This will now limit the HeartBeat API in your WordPress site.
Please don’t hesitate to contact our 24/7 Singapore or Australia Support Team if your have further queries.