Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTo limit WordPress Heartbeat, first confirm that Heartbeat requests are contributing to the activity you want to reduce. Then either increase the client-side polling interval in code or use a Heartbeat-control plugin to adjust behavior by location. Avoid disabling it site-wide without checking the Dashboard, Post Editor, and any other workflows that may rely on near-real-time updates.
What the Heartbeat API does
WordPress Heartbeat is a built-in polling mechanism: a browser-side tick sends data to WordPress through an AJAX handler, which returns a response. WordPress describes it as an API for near-real-time frontend updates in its Heartbeat API Plugin Handbook. The logged-in request handler is wp_ajax_heartbeat(); WordPress documents related hooks including heartbeat_received, heartbeat_send, and heartbeat_tick in its function reference. Those hooks are for handling Heartbeat data and responses, not the interval-setting method.
Polling frequency is not necessarily identical on every screen. The Plugin Handbook describes a client interval range of 15–120 seconds, while a later WordPress core changeset records a specific inline-edit behavior change. In changeset 59016, dated September 11, 2024, the inline-edit request frequency increased from once every 15 seconds to once every 10 seconds to reduce the delay before a post becomes unlocked when a user navigates away. That is a context-specific cadence, not a universal default for every WordPress page or installation. See the WordPress core changeset.
Before limiting Heartbeat, identify the requests
Check whether Heartbeat is actually responsible for the activity you want to address. In your browser’s developer tools, inspect network requests to admin-ajax.php and look for the Heartbeat action. Compare the request pattern before and after any change, and test the relevant dashboard or editing workflow. This helps distinguish a reduction in Heartbeat polling from a broader server or CPU issue; fewer polls alone do not establish that a site’s performance problem is solved.
Recommended Free Tools
#1 Best Overall
Choose a method: code or a plugin
| Approach | Best fit | Trade-off |
|---|---|---|
| Increase the interval in code | You can maintain and test site code, and want a controlled change. | You must ensure the Heartbeat client is available and the code runs at the right time on the intended screen. |
| Use a location-aware plugin | You want separate controls for areas such as the Dashboard, Frontend, and Post Editor. | Plugin compatibility and maintenance need to be checked against your WordPress version and site. |
Option 1: Increase the interval in code
The Heartbeat client method identified in WordPress core changeset 59016 is wp.heartbeat.interval(). That changeset says the method accepts values from one second to one hour. This is an API range, not a recommended setting or a performance guarantee. Choose a longer interval only if the resulting delay is acceptable for the workflows on your site.
The method must run where the Heartbeat client is available. The exact script handle and execution timing depend on the WordPress version and screen, so verify those details for your installation before adding code. Do not paste an unverified snippet into a live site: implement the change in a maintainable place, test it on a staging site if available, and confirm that the intended interval takes effect only where you want it.
Option 2: Use a Heartbeat-control plugin
The WordPress.org Heartbeat plugin tag page lists plugins categorized for Heartbeat control. One example, WP Media’s Heartbeat Control, describes separate controls for the Dashboard, Frontend, and Post Editor. Its repository readme reports tested compatibility only up to WordPress 6.3; that dated statement does not establish compatibility with a current WordPress release. Check the plugin’s live directory information and test it on your target installation before relying on it.
A location-aware control is useful when the right behavior differs between screens—for example, when you want to limit polling in one area but preserve editor behavior. Review the available settings carefully and change only the locations you intend to affect.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Should you disable Heartbeat?
Disable it only when you have considered what uses it on the affected screen and have tested the result. Heartbeat exists to support near-real-time behavior, and the WP Media plugin exposes a distinct Post Editor control rather than treating the editor as interchangeable with other locations. If your publishing workflow depends on editor behavior, retain that context or test it specifically before applying a broader disable.
Quick Recap
Verify the change and keep a rollback path
- Record the baseline: inspect
admin-ajax.phprequests and identify those carrying the Heartbeat action. - Make one reversible change: increase the interval in code or adjust one location in a plugin rather than changing several settings at once.
- Repeat the request check: compare the Heartbeat request pattern with the baseline. Treat any performance benefit as something to confirm with your site’s own measurements, not an assumed outcome.
- Test the affected workflows: check the Dashboard and the Post Editor if either was changed, along with any other screen whose behavior you rely on.
- Undo the change if needed: restore the prior code or plugin setting if a relevant workflow no longer behaves as expected.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
