Fixora Heartbeat Manager
Settings overview with per-location controls
Fixora Heartbeat Manager is lightweight heartbeat control for WordPress: allow, limit, or disable Heartbeat where it hurts performance, so admin-ajax polling does not burn CPU on shared hosting.
WordPress Heartbeat (Heartbeat API) powers autosave, post locking, and other logged-in real-time features. Out of the box it can fire about every 15 seconds on edit screens and every 60 seconds on the dashboard. Many open wp-admin tabs more admin-ajax.php?action=heartbeat traffic higher CPU.
Use Fixora Heartbeat Manager when you need to:
- Control Heartbeat separately on dashboard, post editor, and frontend (logged-in)
- Limit Heartbeat interval (15–300 seconds) to cut admin-ajax load and reduce CPU usage
- Disable Heartbeat on the frontend or dashboard when you do not need it
- Keep the post editor on Allow by default so autosave and post locks keep working
Safe defaults: dashboard limited to 60s, editor Allow, frontend disabled.
Built for the same problem people search as heartbeat control / disable heartbeat / reduce admin-ajax CPU — with modern WordPress/PHP support and no heavy framework.