Heartbeat Controller
by Abdur Rahman · Performance
Also makes 1 other plugin · 1K+ installs across the portfolio →
Control WordPress Heartbeat API to reduce load. Allow, disable, or set custom frequency for Dashboard, Post Editor, and Frontend.
Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.
Health
Not scored
no reviews to score from
Active installs
1K+
≈1.5K estimated
Momentum
-13%
downloads vs prior 30d
Biggest opportunity: Swap “autosave” for “controller”. “autosave” isn't earning its slot: you're not in the first 24 results for its own search. “controller” sits at #9 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
Not scored yet. Nobody has reviewed this plugin, so a grade would come from directory averages rather than from anything measured here.
Install conversion
How it's measured →19%
of downloads still active
At least 1K of 5.2K lifetime downloads are still running, above its category: the median Performance plugin keeps 1.4%, across 1,104 plugins.
Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Performance plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.
Details
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Well optimized
Most to gain: Update recency
Updated 461 days ago, past the ~180 days where wp.org starts discounting
Tested up to WordPress 6.8.12, the current branch or newer
No reviews yet, so wp.org scores it as a middling unrated listing
5 of 5 tags set · short description in place
To rank higher: Last updated 461 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.
Get the full rank-higher report →Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
32
Momentum
Losing ground
-0.2
Velocity
places per keyword, 28d
0%
Breadth
of keywords climbing, 28d
0.0
Acceleration
recent half vs earlier
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| heartbeat api your tag | #9 | #24 | 0 |
| heartbeat your tag | #9 | #22 | 0 |
| controller | #9 | #15 | down 1 |
| heartbeat control | #6 | #19 | 0 |
| disable heartbeat | #12 | #22 | 0 |
| admin ajax.php your tag | Not checked yet | ||
| autosave your tag | Not in the top 24 | ||
| performance your tag | Not in the top 24 | ||
6 searches this plugin appeared in over the last 90 days, 5 listed. 1 left out as unrelated or noise (years, numbers, stray words). 2 of its tags aren't in the top 24 for their own search.
What to do about it
- Swap “autosave” for “controller”. “autosave” isn't earning its slot: you're not in the first 24 results for its own search. “controller” sits at #9 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
Daily downloads
Since 29 Jul 2025 · 461 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 655 · peaks are release surges
Directory rank vs rivals
wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
No release in a yearHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
0
releases in the last 12 months
1.3y ago
latest release · v1.0 · 28 Jul 2025
1
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “1K+”. Our estimate pins where the real number sits.
Crossed into this band 6 months ago; a band this size takes about a year or more to cross, which places it about 51% of the way through.
Install history since 28 Jul 2025
AI assistants
How it's measured →Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.
Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.
Readme readiness
6 of 8 pass · checked 26 Oct 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ✓ Says what it does "Control WordPress Heartbeat API to reduce load. Allow, disable, or set custom frequency for Dashboard, Post..."
- ✓ Has a FAQ 4 questions in the FAQ.
- ✓ FAQ asks real questions 4 of 4 read like questions a user would type.
- ! Names who it is for One audience phrase ("ideal for"); say who the plugin is for and what they use it for.
- ! Names what it works with Names no plugin, service or platform it works with.
- ✓ Headings and lists 2 headings and 3 lists.
- ✓ Enough to quote 1,434 characters of description.
- ✓ Tags match the text 4 of 5 tags appear in the text; "autosave" does not.
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2026-04-30 900+ → 1K+ up after 13 days in tier
- 2026-04-17 800+ → 900+ up after 7 days in tier
- 2026-04-10 700+ → 800+ up after 9 days in tier
- 2026-04-01 600+ → 700+ up after 18 days in tier
- 2026-03-14 500+ → 600+ up after 11 days in tier
- 2026-03-03 400+ → 500+ up after 24 days in tier
- 2026-02-07 300+ → 400+ up after 31 days in tier
- 2026-01-07 200+ → 300+ up after 36 days in tier
Competes with
The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).
-
Dynamic Front-End Heartbeat Control 1K+ installs · 4.3★ · 3 shared tags A -
Heartbeat Control 70K+ installs · 4.1★ · 2 shared tags D -
LiteSpeed Cache 7M+ installs · 4.8★ · 1 shared tag B -
WP Super Cache 1M+ installs · 4.3★ · 1 shared tag A -
Speed Optimizer – The All-In-One Performance-Boosting Plugin 1M+ installs · 4.1★ · 1 shared tag A -
WP Fastest Cache – WordPress Cache Plugin 1M+ installs · 4.9★ · 1 shared tag A
Embed this report card
Drop a live Pulse card for Heartbeat Controller into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/heartbeat-controller" width="480" height="300" style="border:0" loading="lazy" title="Heartbeat Controller — Plugin Pulse"></iframe> Heartbeat Controller: 1K+ active installs, no reviews yet. Plugin Pulse (WP Mayor), as of 2026-11-01. https://plugins.wpmayor.com/plugin/heartbeat-controller
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.