Siteground’s SG Optimizer Default WordPress Heartbeat Optimization Settings Aren’t the Recommended Ones

red amazon danbo on brown wooden surface

When you enable SiteGround’s SG Optimizer plugin WordPress Heartbeat Optimization you don’t get the recommended settings. This can cause issues. Read to learn more.

SiteGround is one of the most popular and recommended WordPress hosting. It has an official SG Optimizer plugin, which can help you improve your site’s performance. Under an Envriomrment Optimization section in the plugin, there is a WordPress Heartbeat Optimization setting, which is supposed to decrease CPU usages while using the WordPress admin.

When you toggle WordPress Heartbeat Optimization on, you see 3 sub-settings: WordPress Admin Pages, Post and Page Edit, and Site Frontend. By default, all Heartbeat types are disabled by SG Optimizer. Nevertheless, if you will click on each subsetting edit pencil you will discover that while for WordPress Admin Pages and Site Frontend the recommended setting is indeed ‘disabled’, the actual recommended setting for Post and Page Edit is ‘enabled at 180 seconds’.

graphical user interface, text, application, chat or text message
Although disabled by default, the recommended setting for the Post and Page Edit Heartbeat is ‘enabled at 180 seconds’

As far as I understand, keeping WordPress Heartbeat API disabled on Post and Page Edit can increase the chances of users overriding each other edits. This is exactly what happened in my case.

Was the post helpful?

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: