Your WordPress site has a setting buried four layers deep that’s quietly costing you money every hour of every day. It pings your server every 15 seconds by default, hammers admin-ajax.php, and on shared hosting in Bergen County it’s the single biggest reason your $12/month plan feels like a $4/month plan. It’s called the Heartbeat API, and almost nobody touches it.
What the Heartbeat API actually does
WordPress uses the Heartbeat API to keep your admin dashboard “alive” — autosaving posts, showing the lock icon when two editors open the same page, refreshing notifications, and powering plugin dashboards. By default, every open WordPress tab fires a POST request to /wp-admin/admin-ajax.php every 15 seconds. Leave the admin open in a tab while you work in another? 240 requests an hour, per tab, per logged-in user.
Why 15 seconds is too aggressive for 95% of sites
The 15-second default was set in 2013 when most sites had one admin and dedicated hosting was rare. In 2026, on a shared SiteGround or Bluehost box, that constant admin-ajax.php traffic shows up as CPU spikes, slow dashboard loads, and — worst — slow front-end pages because PHP workers are busy answering heartbeats instead of serving visitors. We’ve audited Bergen County sites where 70% of all PHP execution time was Heartbeat traffic. Not visitors. Not bots. The admin tab the owner forgot to close last Tuesday.
The 60-second fix and what it saves
Bumping the interval from 15s to 60s cuts heartbeat traffic by 75% with zero functional loss. Autosave still works. Post-lock still works. You just check in every minute instead of every fifteen seconds.
Here’s what we typically measure on Bergen County client sites after the change:
- CPU usage on shared hosting: 18-35% reduction during admin sessions
- PHP memory: 80-150 MB freed back to visitor-facing requests
- Dashboard TTFB: drops from ~900ms to ~340ms on typical SiteGround GoGeek
- Monthly hosting headroom: equivalent to a $15-25/month plan upgrade you didn’t have to buy
- Lighthouse mobile score: 2-6 point jump on the front-end (PHP workers freed up)
How to change it (two ways)
The plugin route: install Heartbeat Control by WP Rocket (free), set “Modify Heartbeat” to 60 seconds on the dashboard, post editor, and front-end. Three dropdowns, done in 90 seconds.
The no-plugin route: add a tiny snippet to a child theme’s functions.php or a custom mu-plugin that hooks heartbeat_settings and sets $settings['interval'] = 60. We prefer the mu-plugin approach because it survives theme switches and doesn’t add another plugin to your maintenance load.
When NOT to touch it
If you run WooCommerce with multiple staff handling live orders, keep it at 15s in the admin so order notifications surface fast. If you run a multi-author publication where two editors might open the same draft, keep it tight. For 9 out of 10 service businesses, contractors, law firms, and local shops in Paramus, Hackensack, Ridgewood, and Fort Lee — 60 seconds is the sweet spot.
How AJD handles this
Every site we onboard gets a Heartbeat audit in the first hour. We measure baseline admin-ajax.php request rate, set the right interval per context (admin/editor/front-end separately), and document it in the site’s runbook so the next developer doesn’t undo it by accident. On a recent Paramus B2B client, this one change dropped their average page load from 3.1s to 1.8s — no other code changed. They were one tweak away from the speed they thought required a $200/month upgrade.
Whether you work with us or not, go check your Heartbeat setting today. It’s free, it takes two minutes, and it’s the highest-ROI WordPress tweak we know.
Want us to audit your WordPress site for hidden settings like this? We run a free 30-minute discovery call where we walk through your real performance metrics and tell you the three highest-impact fixes — no pitch, no pressure. Book Free Discovery Call →
