WordPress uses a background feature called the Heartbeat API to manage tasks like autosaving drafts, locking posts when other users are editing them, and displaying real-time e-commerce data. While useful, it works by constantly sending requests to your server—sometimes every 15 seconds—for as long as your WordPress dashboard is open in your browser. If you leave a tab open while stepping away from your desk, or if you have multiple authors working simultaneously, these continuous background requests can quickly max out your hosting CPU limits and slow down your site.

Since your Sternhost account is powered by LiteSpeed, you can easily regulate or completely disable this feature using your existing LiteSpeed Cache plugin to protect your server resources.

Step 1: Accessing the Toolbox Settings

The LiteSpeed Cache plugin includes a dedicated section for managing advanced WordPress core features.

• Log in to your WordPress admin dashboard.

• In the left-hand sidebar, hover over LiteSpeed Cache and click on Toolbox.

• Click on the Heartbeat tab located at the top of the settings screen.

Step 2: Regulating the Heartbeat Intervals

Instead of turning it off completely and losing your autosave feature, the best practice is to drastically slow down how often the Heartbeat API "pings" your server.

• Locate the Frontend Heartbeat Control toggle and turn it ON. Unless you run a complex real-time web app, change the action to 'Disable'.

• Locate the Backend Heartbeat Control toggle and turn it ON. Set the interval (TTL) to 60 seconds to slow down unnecessary background dashboard tasks.

• Locate the Editor Heartbeat Control toggle and turn it ON. Set the interval to 60 or 120 seconds. This ensures your posts still automatically save while you write, but not so frequently that it strains the server.

• Click the Save Changes button in the top right corner.

Why Controlling Heartbeat is Essential

• Prevents Resource Errors: It stops thousands of unnecessary background requests, preventing the dreaded "508 Resource Limit Is Reached" error on your hosting account.

• Faster Admin Experience: By silencing the constant background chatter, it frees up server processing power so your actual tasks—like publishing posts and uploading images—happen much faster.

• Improves Local Device Performance: Constant background server pinging can actually drain the battery and use the RAM of the laptop or device you are using to edit your website; slowing it down improves your local browser performance as well.