Dynamic Front-End Heartbeat Control


Introducing an enhanced solution for optimizing the performance of your WordPress website when the manual heartbeat settings or the WordPress Heartbeat API fall short.

The plugin offers a seamless and efficient approach to dynamically control the front-end heartbeat, automatically determining the optimal settings for your website. By analyzing user usage, WordPress site assets, and server environment, it empowers your WordPress performance to achieve its full potential. Once activated, it immediately begins improving performance without any need for user intervention. It intelligently adjusts the heartbeat interval in real-time, adapting to the changing demands of your website. This dynamic control guarantees an optimized and efficient heartbeat system, resulting in improved overall performance and responsiveness.

For the best outcome it’s recommended that you have a caching plugin installed as well as optimized pages(minified CSS, JavaScript, including optimized images).

If you already have the plugin files on your device you can follow the steps:

Step 1: Login to your WordPress Dashboard.

Step 2: Click on «Plugins» on the left-hand side menu, then select «Add New».

Step 3: Click on the «Upload Plugin» button at the top of the page.

Step 4: Click on the «Choose File» button and browse to the location on your computer where the plugin file is saved. Select the plugin dynamic-heartbeat.zip file and click on «Open».

Step 5: Once the plugin file is uploaded, click on the «Install Now» button.

Step 6: After installation, click on the «Activate» button to activate the plugin.

Step 7: Once activated, the plugin will begin working right away. Allow a few visits on your pages to let the plugin fully determine the best heartbeat interval. Make sure you clear your cache after activation.

Additional important information:

  • The plugin will try to connect to the default localhost Redis port or Memcache. If you have a different path for object caching methods you can update them in the WP Admin Dashboard > Settings > DFEHC. In the event you don’t have object cache enabled, the plugin will fall back and use regular cache automatically.
  • Some caching plugins offer manual heartbeat control. For the best outcome, make sure that you only have this plugin controlling your heartbeat intervals automatically. This plugin is designed to integrate with any other plugins you might have installed. It seamlessly works with other services, enhancing overall heartbeat performance and ensuring that you can leverage all the benefits that other plugins and CDNs bring to your site.


I'm not a tech savvy person and all other plugins that control heartbeat intervals are manual. I'm happy to have a solution that takes care of this automatically
We already have Litespeed cache but the heartbeat intervals were manually set. Pages have a more responsive snap to them with this plugin!
Посмотреть все 5 отзывов

Участники и разработчики

«Dynamic Front-End Heartbeat Control» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:


Перевести «Dynamic Front-End Heartbeat Control» на ваш язык.

Заинтересованы в разработке?

Посмотрите код, проверьте SVN репозиторий, или подпишитесь на журнал разработки по RSS.

Журнал изменений


  • Settings page update.


  • Code structure upgrade.
  • Added the ability to manually control back-end heartbeat as well as editor heartbeat intervals.
  • Now you can adjust the resource priority from WP Admin Dashboard > Settings > DFEHC


  • Efficiency improvements.


  • Enhanced Unix server load detection.
  • Added a new setting in the plugin’s settings DFEHC page that allows users to completely disable the WordPress Heartbeat API.


  • Efficiency improvements.


  • Improved object caching calling method.
  • Other small code and visual adjustments.


  • Added Heartbeat Health widget in the admin dashboard.
  • Performance & security improvements.


  • Small code improvements.


  • Persistent Storage Support: Added support for Redis and Memcached as persistent storage options for efficient data handling and improved performance.
  • Settings Page: Added a dedicated settings page to configure Redis and Memcached settings, providing flexibility in specifying server and port information. In the event the user does not have persistent storage support options, the plugin will fallback to regular caching. Update the settings only if they are needed from your WP Admin dashboard > Settings > DFEHC
  • Improved Load-Based Recommendations: Calculate the recommended heartbeat interval based on server load average and response time to optimize performance
  • Made various updates to improve compatibility with different server configurations and enhance overall performance.
  • Improvements in error reporting.


  • Reliability improvements.


  • Implemented an asynchronous heartbeat determination feature, ensuring that the plugin operates seamlessly within any WordPress setup without compromising performance. By offloading the heartbeat calculation to a separate asynchronous process, the plugin remains non-invasive and minimizes any potential impact on the overall performance of your website.
  • Small corrections and code minification.


  • Fixed compatibility issues with some older versions of server-side programs.


  • Minor corrections.
  • Performance improvements.


  • The plugin has undergone extensive improvements to ensure seamless integration and optimal performance across various WordPress configurations. With its new enhanced compatibility, it can seamlessly adapt to different themes, plugins, and hosting environments, providing a reliable solution for all types of WordPress websites.
  • Added more complex reasoning behind determing the best recommended heartbeat inteval.
  • Set the grounds for easier future updates.


  • Added a new way of calculating heartbeat accuracy.
  • Improved compatibility with shared hosting environments where users have no control over the server load.
  • Hearbeat is now taken into account on pages that can only be accesible to visitors.
  • Now caching the frequently used DOM elements to avoid unnecessary reselection and improve performance.
  • Various realiability improvements.


  • Updated heartbeat structure to incorporate heartbeat caching. Recommended heartbeat caching will automatically be disabled when it doesn’t make sense anymore. For example the website is crowded.