Heartbeat Control

Beschreibung

Heartbeat Control by WP Rocket allows you to manage the frequency of the WordPress heartbeat API in a few clicks.

The WordPress Heartbeat API is a great feature that provides real-time communication between the server and the browser when you are logged into your WordPress admin panel. It uses the file /wp-admin/admin-ajax.php to run AJAX calls from the browser. By default, AJAX requests are sent every 15 seconds on post edit pages, and every 60 seconds on the dashboard.

This is indeed helpful; but if you usually leave your WordPress admin open for long periods (for example when you write or edit posts), the AJAX requests from the API can pile up and generate high CPU usage, leading to server performance issues and even hosting account suspensions.

With Heartbeat Control by WP Rocket, you can easily choose to limit or completely stop the activity of the WordPress Heartbeat API. You can also add rules for specific locations only (Dashboard, Frontend or Post Editor).

To learn more about WordPress performance optimization and make your website faster, join our WP Rocket Facebook Community!

Related Plugins

  • Imagify: Best Image Optimizer to speed up your website with lighter images.
  • WP Rocket: Best caching plugin to speed-up your WordPress website.
  • Lazy Load by WP Rocket: Best Lazy Load script to reduce the number of HTTP requests and improves the websites loading time.

Screenshots

  • Add rules for specific locations
  • Modify the default frequency

Installation

  1. Upload the plugin folder to the /wp-content/plugins/ directory.
  2. Activate Heartbeat Control on the Plugins page.
  3. Adjust any settings within Settings > Heartbeat Control.

FAQ

How do I change my settings?

Once the plugin is installed and active, you’ll find it under Settings > Heartbeat Control Settings.

Can I modify the frequency of the Heartbeat?

Yes! If you choose the option Heartbeat Behavior > Modify Heartbeat, you’ll have the possibility to change the default frequency (15 secs) and increase it.

Is it ok to disable WordPress Heartbeat completely?

If you’re the only user of your site, and you’re sure you will need none of the featured related to the API, yes it’s ok to do that. It’s important to note that disabling the WordPress Heartbeat API completely could affect the functionality of plugins and themes that rely on it: use it responsibly!

Rezensionen

23. April 2019
The CPU usage of my shared host was really high, and I received the alert from host company. They recommend me to install this plugin. It works fine!
2. April 2019
Siteground's customer service recommended that I install this plug-in, in order to prevent the WP background from constantly accessing the host's CPU, resulting in excessive CPU usage, I believe that Siteground customer service recommendations, the interface is very easy and simple, is a great plug-in.
2. Oktober 2018
EDIT: quick response from author notes this is not intentional. was able to permanently dismiss by clearing my host Siteground's cache (from SG Supercacher). Solid plugin that was ruined by notifications for donations that will reappear every time the admin dashboard loads. No matter how many times you click X to close it. Unfortunate way to ruin a very good plugin.
24. August 2018
Update #2 Aug 2018: Plugin author updated the plugin within a week to remove the nag (see below) and is very responsive to reviews. Can't ask much more than that from a free plugin. Updating to 5 stars to reflect current functionality of the plugin. Appreciate your work and candor, Jeff. Aug 2018 Update: Donation nag appears to be gone without any update to the plugin. I guess it is programmed with the nag for so many days after update (rather than until dismiss). Either way, I no longer trust this plugin for a production environment. Original Review: Removing this from all my client sites after the latest update spams every page of the dashboard with an unremovable donate beg. You shouldn't have to edit the plugin to remove the nag. Seems the "bug" keeps reoccurring every few updates. Functionally, this is a 5 star plugin, but is intolerable with all the nags.
18. Februar 2018
Do not install this addon if you want a notification begging for a donation FOREVER on your admin screen. To remove the notification ========== 1.) Click on "Editor" on left side bar under plugins. 2.) Select the plugin from the drop down on the right, "Heartbeat Control" once selected, it should read "Editing heartbeat-control/heartbeat-control.php" on top of page. 3.) Do a search down the code for "Donation" and remove that section of the code including the } brackets before and after.
Lies alle 42 Rezensionen

Mitwirkende & Entwickler

„Heartbeat Control“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„Heartbeat Control“ wurde in 1 Sprache übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „Heartbeat Control“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

1.2.5

  • Fixed issue caused by previous version deployment.
  • Added hbc_disable_notice hook to force dismissal of update notices.
  • Additional documentation added.
  • Minor standards adjustments.

1.2.4

  • Updated CMB2 to 2.4.2.
  • Bumpted „tested up to“ version.
  • Fixed a bug that occurred if no locations were selected.
  • Minor standards adjustments.

1.2.3

  • Added composer.json and composer.lock that were missing.
  • Updated CMB2 to 2.3
  • Translation files generated.
  • Language path and text domain added to plugin header.
  • Bumped compatible WP version.

1.2.2

  • Minor bugfixes.

1.2.1

  • Fixed issue that would cause some users to not see the modification slider.

1.2

  • Added conditional logic.
  • Multiple actions can now be performed.
  • Scripts are bundled and minified.
  • Changes to settings structure.
  • Miscellaneous bugfixes.

1.1.3

  • Readme updates.

1.1.2

  • Bugfixes.
  • Resolves potential fatal error mistakenly pushed to 1.1.

1.1.1

  • Bugfixes.

1.1

  • Rewritten from the ground up for future extensibility.
  • Performance enhancements.
  • Improved UI.
  • Better handling for late calls to the Heartbeat API.
  • New condition settings for filtering on the frontend.

1.0.2

  • Bumped tested version
  • Added donation button

1.0

  • Erstveröffentlichung