Advanced
Dotjuice → Page speed → Advanced
What this tab controls
WordPress's Heartbeat API, XML-RPC, and WooCommerce script loading on non-shop pages.
Settings
| Setting | Default | What it does |
|---|---|---|
| WordPress Heartbeat API | Optimise | Choose Default (WordPress's normal behaviour, checking in roughly every 15 seconds), Optimise (extends the interval — see below), or Disable (removes it entirely). Heartbeat powers autosave, post-locking ("someone else is editing this post") notices, and some plugins' live dashboard updates. |
| Heartbeat Interval (seconds) | 60 | Only used when Heartbeat is set to Optimise. How often it checks in — minimum 15 seconds, whatever you enter is used as the new interval. A longer interval means less background load but a longer delay before autosave/post-lock notices update. |
| Disable XML-RPC | Off | Stops your site responding to XML-RPC requests — the older remote-publishing protocol some legacy apps and (historically) some brute-force attack tools target. Only worth enabling if you don't use an app, service, or plugin that specifically requires XML-RPC (check before enabling; some SEO and cross-posting tools still rely on it). |
| Disable WooCommerce Scripts on Non-Shop Pages | Off | Stops WooCommerce's cart and general styling/scripts from loading on pages outside your shop and cart/checkout flow — see the warning below before enabling. |
⚠ Before enabling "Disable WooCommerce Scripts on Non-Shop Pages"
This is a genuinely useful setting for pages that have nothing to do with your shop, but check your My Account pages (order history, downloads, addresses) after enabling it — those pages rely on WooCommerce's own styling too, and if they look visibly broken after you turn this on, it's this setting. Test it and confirm your account pages still look right before leaving it enabled on a live site.
Heartbeat: Optimise vs Disable
Optimise (the default) is the safer of the two active choices — it keeps all of WordPress's Heartbeat-dependent features working (autosave, post locking, live plugin dashboards) but checks in less frequently, cutting down on background requests without losing functionality.
Disable removes Heartbeat entirely. This means autosave-in-the-background and "someone else is currently editing this" warnings stop working, and any plugin whose live-updating dashboard widgets depend on Heartbeat will stop updating live. Only choose this if you're confident nothing on your site relies on it.
About XML-RPC
Disabling XML-RPC here uses WordPress's own built-in mechanism to refuse XML-RPC requests — it doesn't hide or remove the xmlrpc.php file itself, it simply makes it respond that XML-RPC is turned off. If you need airtight blocking at the server level (rather than the WordPress application level), that typically needs a rule added at your web server or firewall instead.