The WordPress 3.6 version launched the WordPress Heartbeat API. WordPress Heartbeat API enables the communication of your browser and the server while you are logged into the WordPress admin panel. This feature enables WordPress to manage various aspects like letting the other author know that a particular post is being edited by some other user, the plugins can also use the script executions and thereby you can get notifications in real time etc.<\/p>\n
Even though the WordPress Heartbeat API looks like a great feature, it might cause some issues in some situations. The Heartbeat makes checks at different time periods on different pages of your website \u2013 like for the post edits, it makes a check in every 15 minutes and on the Dashboard, the check is made every minute etc. Every \u2018tick\u2019 made by the Heartbeat creates a POST request that adds to the number of your executions and it also adds to the CPU time used.<\/p>\n
The WordPress Heartbeat feature makes use of the wp-admin\/admin-ajaz.php <\/strong>file in order to make the AJAX calls. If you notice that a large number of POST requests are generated by that file, it means that you have to limit the work of Heartbeat or you need to stop it completely.<\/p>\n It is possible to limit the execution frequency of WordPress Heartbeat. This can be done by making use of a plugin known as \u2018Heartbeat Control\u2019.<\/p>\n When the settings are saved, you will override the Heartbeat execution frequency that is set by default. The frequency will be set to the value that you set through the Frequency slider.<\/p>\n You can disable WordPress Heartbeat by selecting the option \u2018Disable Heartbeat\u2019 from the \u2018Heartbeat Behavior\u2019 drop down menu and enable all the \u2018Locations\u2019. This will disable the use of Heartbeat feature on all the pages of your website.<\/p>\n If you no longer wish to work with the WordPress Heartbeat feature, you can stop it completely. For doing this, you have to edit the \u2018functions.php\u2019 file of your theme and paste the lines mentioned below right after opening the \u2018<?php\u2019 tag:<\/p>\n add_action( ‘init’, ‘stop_heartbeat’, 1 );<\/p>\n function stop_heartbeat() {<\/p>\n wp_deregister_script(‘heartbeat’);<\/p>\n }<\/p>\n This will completely stop Heartbeat from working on your website and it will no longer add to the number of executions and the CPU time utilized for your account.<\/p>\n","protected":false},"excerpt":{"rendered":" The WordPress 3.6 version launched the WordPress Heartbeat API. WordPress Heartbeat API enables the communication of your browser and the server while you are logged into the WordPress admin panel. This feature enables WordPress to manage various aspects like letting the other author know that a particular post is being edited by some other user, […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[78,86,499,500,178],"class_list":["post-5841","post","type-post","status-publish","format-standard","placeholder-for-hentry","category-wordpress-faq","tag-wordpress-2","tag-wordpress-blog","tag-wordpress-heartbeat","tag-wordpress-heartbeat-api","tag-wordpress-website"],"yoast_head":"\nHow To Limit Heartbeat?<\/strong><\/h2>\n
\n
How To Disable Heartbeat?<\/strong><\/h2>\n
How To Stop Heartbeat Completely?<\/strong><\/h2>\n