Here, we’ll talk about why WordPress Heartbeat API is the usual suspect that causes the issue.<\/p>
Download all-in-one WordPress cheat sheet<\/a><\/p> WordPress Heartbeat API provides a communication protocol, using AJAX<\/a> calls, between the browser and the server.<\/p> As the name implies, the API will send continuous pulses and trigger events (or callbacks) upon receiving data. This function helps sync all the data between the server and the WordPress dashboard.<\/p> The idea behind Heartbeat API is quite compelling. For example, when you create\/edit a post from the editor, it provides a function to autosave the post periodically.<\/p> In a collaborative WordPress site, it has a post-locking function to prevent you from editing a post that’s being worked on by another user. If you use an eCommerce plugin, this API will also help to display sales on your site.<\/p> While having an autosave function and real-time data notification features can be beneficial, they can also be harmful in a specific situation.<\/p> Heartbeat API sends AJAX requests (POST requests) using the \/wp-admin\/admin-ajax.php<\/strong> file. Each request that executes a PHP file equals CPU time on the server.<\/p> This can cause a large number of requests to be sent to the hosting server, which results in high CPU utilization.<\/p> As we noted earlier, this can be a problem for a webmaster with a shared hosting plan. As you reach your quota limit, high CPU usage can eventually lead to account suspension. So be sure to check how to fix spikes in your admin ajax file<\/a>. <\/p> If you’re thinking of completely stopping Heartbeat API, you need to think twice. It’s not because you can’t do that, it’s just not practical.<\/p> Without WordPress Heartbeat API, all the changes you made in the post will be lost should you ever forget to click the Save Draft<\/strong> button. And you will no longer have access to the Revisions feature in WordPress<\/a>.<\/p> If you install WordPress plugins<\/a> that use Heartbeat API, you also can’t display the real-time notifications and information features on your site.<\/p> But if you’re working alone and all of these functions do not matter to you, you can then proceed to stop WordPress Heartbeat API.<\/p> Otherwise, you might consider controlling the API instead.<\/p> You can stop Heartbeat API by adding this code snippet to your active theme’s functions.php<\/strong> file.<\/p> Remember, you should do this if you’re the only person working with the website, and you don’t need to install additional plugins that use this API.<\/p> From your WordPress Dashboard, go to Appearance -> Theme Editor<\/strong>. Make sure you’re editing the active theme of your site. Click Theme Functions (functions.php)<\/strong> from the right-hand navigation menu. Paste the code snippet above right after the opening <?php<\/strong> tag and click Update<\/strong>.<\/p> That’s it, and now you’ve successfully disabled WordPress Heartbeat API on your site.<\/p>What is WordPress Heartbeat API?<\/h2>
Why limit WordPress Heartbeat API?<\/h2>
Things to consider before stopping Heartbeat API<\/h2>
How to completely stop Heartbeat API?<\/h2>
add_action( 'init', 'stop_heartbeat', 1 );\nfunction stop_heartbeat() {\nwp_deregister_script('heartbeat');\n}<\/pre>![\"Edit](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/2\/2019\/05\/edit-the-functions-php-file.png\/public\")
<\/figure><\/div>![\"\"](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/2\/2024\/06\/New-WP_in-text-banner.png\/w=1024,h=1024,fit=scale-down\")
<\/a><\/figure>Conclusion<\/h2>