WordPress uses the Heartbeat API to send small requests to admin-ajax.php every 15 to 60 seconds while pages are open: for autosave, post locking and dashboard notifications. Each request runs PHP and counts toward your CloudLinux limits. With several admin tabs open, it adds up. LiteSpeed Cache can slow Heartbeat down.
Before you start
- LiteSpeed Cache installed (see configuring LiteSpeed Cache).
- Check whether
admin-ajax.phpshows up often in Resource Usage snapshots or X-Ray traces (see X-Ray).
Where the settings are
Go to LiteSpeed Cache → Toolbox → Heartbeat. You get separate controls for three contexts:
| Context | Suggested | Why |
|---|---|---|
| Frontend Heartbeat | Disable (TTL 0) unless a plugin needs it | Visitors rarely need Heartbeat |
| Backend Heartbeat | 60–120 seconds | Dashboard notices still work, just less often |
| Editor Heartbeat | Keep on, 30–60 seconds | Autosave and post locking protect your work |
Apply the settings
- Turn on Frontend Heartbeat Control and set the TTL to 0 to disable.
- Turn on Backend Heartbeat Control and set 60 or 120.
- Turn on Editor Heartbeat Control and set 60.
- Save.
Warning: Do not disable Heartbeat in the editor if several people edit content. Post locking, which stops two people overwriting each other, depends on it.
Check the effect
- Leave a dashboard tab open and watch the Network tab in DevTools:
admin-ajax.phprequests should appear less often. - Over a few days, Resource Usage should show fewer entry process spikes while you work in wp-admin.
Other admin-ajax sources
Heartbeat is only one source. Live chat widgets, statistics plugins and page builders can poll admin-ajax.php too. If load stays high, find the plugin responsible and reconfigure or replace it (see 508 errors).
Troubleshooting
A plugin stopped updating live
Some plugins use Heartbeat on the front end, such as live notifications or carts. Re-enable Frontend Heartbeat with a longer interval.
"Your session has expired" in the editor
The editor interval is too long or disabled. Use 60 seconds or less.
Frequently asked questions
Is Heartbeat control safe for WooCommerce?
Yes, with the editor left on. Test cart and checkout if you disable front-end Heartbeat; most shops do not need it.
Do I need a separate Heartbeat plugin?
No. LiteSpeed Cache includes the same controls; avoid running two plugins for this.
How often does Heartbeat run by default?
Usually every 15 seconds in the editor and every 60 seconds elsewhere, which is why open tabs add up.
Does closing browser tabs help?
Yes. Every open wp-admin tab sends its own Heartbeat requests. Close tabs you are not using.
Can a security plugin also send admin-ajax requests?
Yes. Some security and statistics plugins poll admin-ajax.php or the REST API. Check their settings for live features you do not need.
Will this improve PageSpeed scores?
Front-end scores barely change, but server load drops, which helps under traffic and keeps you within CloudLinux limits.