Heartbeat Manager
Optimize your WordPress server performance by taking full control of the Heartbeat API. Reduce CPU and RAM load without breaking your site's functionality.
What is the Heartbeat API?
The Heartbeat API is a native WordPress feature that simulates a continuous "pulse" between the browser and the server to handle autosaving and real-time notifications.
However, every "beat" consumes precious resources. Heartbeat Manager allows you to regulate or disable this beat granularly, saving up to 70% of unnecessary AJAX calls.
Backend control
Set the pulse frequency in the administration panel from 30 to 300 seconds to reduce the load while you work.
Frontend control
Completely disable the pulse on the public site or set it to 60/120 seconds to speed up navigation for visitors.
Safe & compatible
Developed with OOP standards. It doesn't remove scripts but instructs them to stop, avoiding conflicts with other plugins.
Ideal for...
High traffic e-commerce
Reduce superfluous admin-ajax.php calls generated by every visitor, ensuring instant page loading even during sales peaks.
Shared hosting
Avoid account suspensions or slowdowns due to exceeding CPU and RAM limits imposed by your budget hosting provider.
Editorial teams
Optimize simultaneous work of multiple authors, reducing the frequency of automatic saves on the database without losing post lock security.
Technical details
OOP architecture
Developed with PHP classes to avoid namespace conflicts and ensure superior maintainability.
Total sanitization
Every saved data is filtered and sanitized. Every output is protected against XSS attacks through native WordPress escaping.
Multilingual ready
Completely prepared for internationalization (i18n) with standard WordPress text-domain.
Frequently asked questions
Everything you need to know about the plugin's operation and compatibility.
Will disabling the Heartbeat API break my site?
No, it will not break your site's core layout. However, completely disabling it on the frontend might affect real-time updates from third-party plugins that rely on it (e.g., live notification badges or certain real-time WooCommerce cart dynamic updates). If you notice issues, you can change the setting from "Disabled" to a higher time interval (e.g., 60 or 120 seconds).
What is the recommended setting for an E-commerce store?
For maximum performance under high traffic, we highly recommend setting the Backend interval to 60 or 120 seconds, and setting the Frontend to "Disabled". This drastically reduces the number of background AJAX requests (`admin-ajax.php`) hitting your server.
Why do I get an "Uncaught ReferenceError" or "undefined" error when testing the frontend?
This is a great sign! WordPress does not load the Heartbeat script on the frontend by default. If you see this error, it confirms that neither your theme nor your active plugins are running background AJAX loops on your public pages, leaving your frontend fully optimized.
Will a higher Post/Page Editor interval affect my Page Builder or Autosaves?
Setting the Editor interval to a maximum value (e.g., 300 seconds) means your automatic layout backups will only trigger every 5 minutes. If you are actively building pages with Elementor, Divi, or Gutenberg, we highly recommend keeping this specific setting at 30 or 60 seconds to balance server resource savings with content safety in case of browser crashes.
Optimize your site today
Download Heartbeat Manager for free and give your server a breath of fresh air.
Disclaimer: This plugin is provided 'as is' and is completely free to use. Levelnetwork.it is not responsible for any damage or malfunction resulting from its use.