Codeloghin

Your all-in-one solution for intelligently optimizing the WordPress Heartbeat API.
This plugin stabilizes server load and improves the browsing experience during traffic spikes by dynamically controlling the Heartbeat interval based on real site conditions. Instead of relying on outdated manual tuning or fixed settings, it continuously analyzes factors such as user activity, server environment, and page complexity to determine the most efficient configuration for your website.
Designed to work seamlessly alongside most performance and caching plugins, it introduces an adaptive approach that helps your WordPress installation operate at its full potential without adding unnecessary server overhead.
Once activated, the plugin begins optimizing immediately—no configuration required in most cases. It intelligently adjusts the Heartbeat interval in real time, responding to changes in traffic and workload to maintain stability, responsiveness, and optimal performance.
Features:
✅ Dynamically optimizes the WordPress Heartbeat API using real-time site conditions 
✅ Smart automation with optional manual control when you need it 
✅ Custom intervals for the Admin Dashboard and Editor environments 
✅ Option to completely disable Heartbeat with a single click 
✅ Advanced real-time decision making with minimal server overhead that completely prioritises user experience and website speed 
✅ One-click database cleanup to remove unnecessary clutter 
✅ Works alongside most caching and performance plugins 
✅ Multisite compatible 
✅ Install, activate, done — performance improvements begin immediately
For optimal results, it is recommended to use this plugin alongside a caching solution and properly optimized pages (minified CSS and JavaScript, compressed and optimized images, etc.).
Additional Important Information:
Some caching plugins provide manual control over the WordPress Heartbeat API. For best results, allow this plugin to manage the heartbeat intervals automatically. You may continue using other performance features from those plugins, but avoid enabling their manual heartbeat controls.
GDPR-friendly design: The plugin may set a lightweight cookie used solely for visitor counting and abuse prevention (rate limiting). No personal data is collected, tracked, or shared with third parties.
Rigorously tested to maintain reliable performance during high-traffic spikes and under constrained server resources.

Dynamic Front-End Heartbeat Control


Very helpful. Reduce server load and increase speed of website.


Plugin functionality


great plugin for website load optimization


DFEHC for website Optimization

An enhanced solution to optimize the performance of your WordPress website and automatically achieve the best Heartbeat API values.

Asheboro

It’s time to find out what is really hitting your admin-ajax.php file so much.
Contrary to popular belief, hits to admin-ajax.php do not only come from the Heartbeat API. Many plugins make use of WordPress’ built-in ajax functionality, sometimes negatively impacting site performance and resource usage. Unfortunately, it’s not always easy to tell what is causing these hits.
Many blogs and web hosts will tell you to install a plugin to limit hits to the Heartbeat API. While this is great for hits coming from the Heartbeat API, it does nothing to affect plugins that use admin-ajax. So how do you stop what you can’t see?
That’s where Amuga Ajax Log comes in.
Amuga Ajax Log tracks and logs actions that hit admin-ajax. It gives you a look at essential data, such as:
<ul>
<li>Requested action name</li>
<li>Possible function or method name</li>
<li>Suspected location</li>
<li>Page that triggered the hit</li>
</ul>
The plugin does not track information about the user.
Amuga Ajax Log was built to make it easier to see what is really increasing your admin-ajax usage. The plugin logs the data to a flat file or a custom database table. It also provides an easy to read Leaderboard that shows you which actions are hitting the most.
“But won’t a busy site cause a lot of data to be tracked?” asks curious local man.
Yes, that is true. That is why we don’t recommend leaving the plugin activated for extended periods. As a troubleshooter, your goal with this plugin is to obtain enough information to solve your issue. With the Leaderboard and Recent Hits list, you will have a higher chance of tracking down what is hammering your admin-ajax.php file.
Another nice feature of Amuga Ajax Log is that it can clean up after itself. We’ve provided two easy options for cleaning up data.
Purge Current Database Log
From the Settings page, check the box that says Purge Current Database Log, hit Save, and Amuga Ajax Log will clear all admin-ajax hit records it has stored in the database.
Remove All Data on Deactivation
We are a big fan of plugins that provide an option to remove their data after deactivation. Amuga Ajax Log does the same. From the Settings page, check the box that says Remove All Data on Deactivation, hit Save, and when you deactivate Amuga Ajax Log from the Plugins page, the plugin does the following:
<ul>
<li>Removes our flag log file if it exists</li>
<li>Removes our custom database table</li>
<li>Removes our data from the options table</li>
</ul>
A Few Notes:
Keep in mind that this plugin does not stop admin-ajax hits; it only records them and provides information about the hit. It is up to you or your developer to determine what to do next.
Because you can have Classes that share method names (ex. ILike->Tacos, ILove->Tacos, GiveMe->Tacos), it is possible that there will be multiple Locations listed.
Sometimes, we can’t figure out where something is. In those cases, we recommend using the action name or the function name and running a Grep search using SSH, or doing a text search with a tool such as Notepad++.

Amuga Ajax Log

Amuga Ajax Log is a tool built for troubleshooters who need to know what is hitting admin-ajax.

Dynamic Front-End Heartbeat Control vs Amuga Ajax Log