Summarize with AI:

Disable Heartbeat

Reduce automatic background requests from WordPress to ease server load. Pick what to turn off or slow down in the module settings.

Overview

Controls the WordPress Heartbeat API that polls admin-ajax in the background for autosave, post locking, and some dashboard refresh. You can throttle the interval or disable Heartbeat on the front end, dashboard, admin, or everywhere—with an option to keep it in the post editor.

Who is this for?

Sites on shared hosting hit by frequent admin-ajax Heartbeat calls
Front ends that enqueue Heartbeat unnecessarily for logged-in users
Admins who want fewer background requests without fully breaking post locking

Features

Throttle mode (recommended)

Keeps Heartbeat but raises the interval (default 60s; presets 15–120s or custom 15–300s).

Disable on frontend only

Stops visitor/public check-ins while leaving dashboard Heartbeat alone.

Disable on dashboard / admin / everywhere

Progressively stronger modes for cutting Heartbeat where you choose.

Allow in editor

When using admin or everywhere disable modes, optionally keep Heartbeat on post/page screens for locking and check-ins.

Use Cases

Shared hosting with concurrent editors
Reduce admin-ajax spikes when many people edit at once by throttling Heartbeat instead of leaving the default 15-second interval.

Membership and logged-in front ends
Stop Heartbeat on public pages when logged-in users would otherwise poll the server from the front end.

Staging and production policy
Standardize on throttle globally, then allow Heartbeat in the editor only when collaborative locking matters.

Frequently Asked Questions

What does the Disable Heartbeat module do in WP PowerSuite?
It controls WordPress Heartbeat background requests: throttle how often they run, or disable them on the front end, dashboard, admin, or everywhere—with an optional keep-alive in the post editor.
How do I enable Disable Heartbeat in WP PowerSuite?
Enable the module in the Modules hub, open settings, choose a mode (start with throttle at 60s), and save.
Who should use Disable Heartbeat?
Sites on shared hosting, teams with many concurrent editors, or front ends that poll Heartbeat unnecessarily for logged-in users.
What is the safest Heartbeat setting?
Throttle at 60 seconds or more. It reduces load while keeping Heartbeat available for editor features.
Is Disable Heartbeat a free or Pro module in WP PowerSuite?
It is included (free) with WP PowerSuite.