Opens in a new tab
Turquoise abstract wavy W logo on a black background
Turquoise abstract wavy W logo on a black background
White WP PowerSuite logo on a black background
White WP PowerSuite logo on a black background
[wpps_ai_summarize]
On This Page
Last updated: 19/08/2026

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

WordPress Heartbeat runs regular background requests between the browser and your server to power features such as autosave, post locking, and live dashboard updates. On busy websites or hosting environments with limited resources, frequent Heartbeat requests can add unnecessary server activity.

Disable Heartbeat gives you control over how often WordPress Heartbeat runs and where it is allowed. Instead of simply switching it off, you can throttle requests, disable Heartbeat only in selected areas, or keep it available inside the editor where important WordPress features depend on it.

Solid black square
Solid black square
Who is this for?
  • WordPress sites looking to reduce unnecessary background requests
  • Busy websites where frequent admin-ajax requests add server activity
  • Agencies optimizing WordPress performance for client websites
  • Developers who want precise control over the WordPress Heartbeat API
  • Sites that want to reduce Heartbeat activity without losing editor functionality

Features

Throttle WordPress Heartbeat
Reduce how frequently Heartbeat requests are sent instead of disabling them completely. The recommended default is 60 seconds.
Flexible Heartbeat Intervals
Choose from common intervals such as 15, 30, 60, or 120 seconds, or set a custom interval between 15 and 300 seconds.
Disable Heartbeat by Location
Turn Heartbeat off only on the frontend, only on the main WordPress Dashboard, throughout wp-admin, or everywhere.
Keep Heartbeat in the Editor
When disabling Heartbeat in the admin area or across the entire site, you can keep it active on post and page editing screens for features such as post locking and editor check-ins.

Reduce Unnecessary WordPress Background Requests

  • WordPress Heartbeat communicates with the server at regular intervals while users have WordPress pages open.
  • Those requests serve a purpose, but the default frequency isn't necessary for every website.
  • Instead of taking an all-or-nothing approach, WP PowerSuite lets you decide how Heartbeat should behave.
  • For many websites, simply increasing the interval is enough to reduce background activity while preserving the WordPress features that rely on Heartbeat.

Throttle Instead of Disable

  • Throttle is the recommended starting point.
  • It keeps the Heartbeat API working but increases the time between requests. WP PowerSuite uses a 60-second interval by default, and you can adjust it based on your requirements.
  • This gives you a balance between reducing repeated admin-ajax requests and maintaining features that depend on Heartbeat.
  • If you need more aggressive control, you can disable it in specific areas instead.

Control Heartbeat Where It Matters

  • Not every part of WordPress needs to be treated the same way.
  • You can disable Heartbeat on public-facing pages while keeping it available throughout the dashboard.
  • Or remove it from the main Dashboard screen while leaving other admin areas untouched.
  • For more aggressive optimization, Heartbeat can be disabled throughout wp-admin or across the entire website.
  • When using these stronger modes, you can still allow Heartbeat inside the post and page editor.
  • This is particularly useful because WordPress uses Heartbeat for editing features such as post locking and collaboration-related check-ins.

Use Cases

  • Reduce admin-ajax Activity
    Increase the Heartbeat interval to reduce frequent background requests while keeping its core functionality available.
  • Optimize Busy WordPress Sites
    Reduce unnecessary Heartbeat activity on websites with multiple administrators, editors, or active backend sessions.

Frequently Asked Questions

Related Modules

Disable WordPress Emojis

Uses the visitor’s device for emoji instead of WordPress’s add-on scripts, so pages start a bit faster.
Speed
Disabled

Disable Post Auto-Save

Fewer automatic saves while you edit, so your site stores fewer hidden draft revisions and stays tidier.
Speed
Disabled

Disable Auto-Update Emails

Turns off WordPress update notification emails after core, plugin, or theme changes.
Speed
Disabled

Remove Shortlink

Removes the default shortlink meta tag from your pages for tidier markup.
Speed
Disabled

Disable oEmbed Auto-Embeds

Stop WordPress from auto-embedding links and loading extra embed code. Ideal when you want faster pages and you handle media and links...
Speed
Disabled

Disable Dashicons on Frontend

Loads fewer icon styles on your public pages for guests. Not recommended if you use Elementor, Bricks, or similar builders on the...
Speed
Disabled

Remove Query Strings

Removes version query parameters from local CSS and JS on the front end for leaner HTML. Does not strip other query args...
Speed
Disabled

Remove Version From Scripts

Removes the WordPress core version from public stylesheet and script links while keeping theme and plugin version markers for cache busting.
Speed
Disabled