LevelNetwork Heartbeat Manager

常見問題集

Will disabling the Heartbeat API break my site?

No, it will not break your site’s core layout. However, completely disabling it on the frontend might affect real-time updates from third-party plugins that rely on it (e.g., live notification badges or certain real-time WooCommerce cart dynamic updates). If you notice issues, you can change the setting from “Disabled” to a higher time interval (e.g., 60 or 120 seconds).

What is the recommended setting for an E-commerce store?

For maximum performance under high traffic, we highly recommend setting the Backend interval to 60 or 120 seconds, and setting the Frontend to “Disabled”. This drastically reduces the number of background AJAX requests (admin-ajax.php) hitting your server.

Why do I get an “Uncaught ReferenceError” or “undefined” error when testing the frontend in the browser console?

This is completely normal and actually a good sign! WordPress does not load the Heartbeat script on the public frontend by default. If you see this error, it means neither your theme nor any active plugins are currently triggering the Heartbeat API on your public pages. Your frontend is already naturally optimized and completely free of these background AJAX hits. The frontend custom interval setting will only apply if an asset explicitly requests the Heartbeat script.

Will a higher Post/Page Editor interval cause lag or sync issues in my Page Builder?

No, it won’t cause lag. However, if you increase the interval to the maximum (e.g., 300 seconds), your automatic backups (autosaves) will only happen every 5 minutes. If you are actively designing with heavy page builders, we highly recommend keeping the Post/Page Editor frequency at 30 or 60 seconds. This gives you the perfect balance: it drastically cuts down server resource usage while ensuring you don’t lose your layout changes if your browser crashes.