Heartbeat Controller

46 Quality Score

Active Installs

14/30

About 1,000 active installs is a small footprint, indicating niche adoption rather than mainstream use, though it does exceed what some comparable micro-utilities reach.

Update Freshness

14/25

Last updated July 28, 2025 and tested against WordPress 6.8.5, the plugin is clearly being maintained, which is a strong positive given the modest user base.

User Rating

0/15

Zero ratings across zero reviews means there is no community signal to confirm or challenge the developer's claims about effectiveness.

Support Health

8/15

With 0 of 0 support threads, there is no public track record to evaluate, so the score reflects uncertainty rather than evidence of poor help.

WP Compatibility

11/15

Tested with WordPress 6.8.5 and requiring only PHP 7.2 and WordPress 5.2, compatibility looks broad and current for typical installations.

Scores higher than 2% of indexed plugins

About

Control WordPress Heartbeat API to reduce load. Allow, disable, or set custom frequency for Dashboard, Post Editor, and Frontend.

Active Installs 1k+

Rating 0/5

Last Updated 2025-07-28 8:10pm GMT

Requires WordPress 5.2+

Tested Up To 6.8.8

Requires PHP 7.2+

✓ No known vulnerabilities

What It Does

Heartbeat Controller lets site administrators tame WordPress's Heartbeat API by disabling, allowing, or rescheduling the background pulses that WordPress sends from admin pages, the post editor, and the frontend. In practice this means fewer AJAX calls to admin-ajax.php, which reduces server load, lowers CPU consumption on shared hosting, and can speed up the dashboard for sites with many editors logged in at once. It is a focused utility, not a general caching or performance suite.

Who It's For

This plugin is best for administrators on shared hosting, resource-constrained VPS plans, or multisite networks where the Heartbeat API is causing noticeable strain on admin-ajax.php. It is also a sensible pick for high-traffic news sites, e-commerce stores, or membership portals where many logged-in users are generating simultaneous autosave and post-lock requests. Sites with just one or two editors on a robust server will see minimal benefit.

Who Should Skip It

If you run a single-author blog on decent hosting, or you already use a performance plugin like LiteSpeed Cache or Jetpack that handles Heartbeat throttling as part of a broader optimization stack, you do not need this. Anyone uncomfortable tweaking WordPress internals or who relies on real-time autosave and post locking in the editor should also avoid it.

The Bottom Line

Heartbeat Controller scores a modest 49.4/100, dragged down mostly by the absence of any ratings and a tiny install base, yet it is actively maintained and clearly focused on a real problem. For site admins who have specifically diagnosed Heartbeat-related load on admin-ajax.php, it is a useful surgical tool. For everyone else, a broader performance plugin is likely the better first move.

Related Plugins

LiteSpeed Cache 95/100

Pick this if you want Heartbeat control bundled with page caching, image optimization, and a full performance stack on LiteSpeed servers.

Jetpack – WP Security, Backup, Speed, & Growth 94/100

Choose this if you also need security, backups, and CDN features alongside general site speed improvements.

Redis Object Cache 92/100

Go with this when your bottleneck is database queries rather than Heartbeat traffic, as it targets a different layer of the stack.

Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals 90/100

Select this if your priority is shaving milliseconds off frontend load times via Cloudflare edge caching.

WP Fastest Cache – WordPress Cache Plugin 89/100

Pick this for a beginner-friendly caching plugin that handles broad page and browser caching without the configuration overhead.