# WordPress Heartbeat optimization checklist
## Volade — practical guide · June 2026

Print this page or check off as you go.

---

## Phase 0 — Diagnosis (before any change)

- [ ] Open DevTools → Network, filter `admin-ajax.php`
- [ ] Note dominant action: `heartbeat` / `woocommerce_*` / other __________
- [ ] Count wp-admin tabs in normal use: __________
- [ ] Measure dashboard + product list load time (before): __________ s
- [ ] Full site + database backup
- [ ] Staging available (recommended): yes / no

---

## Phase 1 — Choose approach

- [ ] Confirmed issue = Heartbeat (`action=heartbeat`)
- [ ] Approach chosen: HCM preset / WP Rocket / snippet / other __________
- [ ] Only one active Heartbeat tool (no duplicates)
- [ ] Site profile: Blog / WooCommerce / Agency / Builder / Max perf

---

## Phase 2 — Install & preset

- [ ] Heartbeat Control Manager installed and active
- [ ] Settings → Heartbeat Control opened
- [ ] Preset applied: _______________________
- [ ] Effective config preview checked on current screen
- [ ] WP Rocket / Heartbeat Control conflict: none / resolved

---

## Phase 3 — Required tests (5/5)

- [ ] Editor autosave: type text → wait 45 s → draft saved
- [ ] Co-editing lock tested (2 browsers)
- [ ] Product / order list: acceptable load time
- [ ] Public front: cart / checkout OK (if store)
- [ ] Plugin stats: requests avoided noted: __________

---

## Phase 4 — Production

- [ ] Go-live off-peak: date/time __________
- [ ] Old `disable_heartbeat` snippets removed
- [ ] JSON config export saved (agency)
- [ ] Team briefed: admin may feel "different"
- [ ] 48 h watch: support tickets + host email

---

## If something goes wrong

| Symptom | Lead |
|---------|------|
| Autosave stopped | Editor interval ≤ 60 s · Builder preset |
| admin-ajax still high | Re-diagnose action · WC Action Scheduler |
| Builder slow / buggy | Elementor preset · editor 30 s |
| Plugin conflict | One Heartbeat manager only |

---

volade.com/en/blog · Heartbeat Control Manager by Volade