Home
/
WordPress Tutorials
/
SiteGround Optimizer Plugin Tutorial
/
Environment Controls in SiteGround Optimizer

Environment Controls in SiteGround Optimizer

HTTPS Enforce

Important!Before you enable the HTTPS, you need an SSL certificate issued for your site domain. By default SiteGround issues free Let’s Encrypt certificates for all websites.

If you are a SiteGround client you can check if there is one issued for your WordPress domain in Site Tools > Security > SSL Manager.

Non-SiteGround Users should make sure that they have an active SSL certificate.

Once you have the SSL issued, you can enable the HTTPS through the SiteGround Optimizer. This will configure your site to work correctly via HTTPS and force a secure connection to it by adding a rule in your .htaccess file. Because all our servers support the innovative and faster HTTP2 protocol, SiteGround clients running their site via HTTPS can also benefit from it as well.

Fix Insecure Content

In most cases, this does not need to be switched on. Use it only if you notice insecure/mixed content warnings on your site after switching the HTTPS. This option will dynamically rewrite insecurely loaded resources to go through https. Even though we’ve developed the re-write to be super fast, it will add some unnecessary overhead to the loading process of your site if it is already configured and working correctly via HTTPS.

GZIP Compression

GZIP compression is enabled for all websites on SiteGround’s servers by default, so this option appears only for non-SiteGround users.

Enables compression of the content that’s delivered to your visitors’ browsers, improving the network loading times of your site.

Browser Caching

Leverage browser caching is enabled for all websites on SiteGround’s servers by default, so this option appears only for non-SiteGround users.

Adds rules to store the static content of your site longer in the visitors’ browser cache which improves the site performance.

WordPress Heartbeat Optimization

By enabling this option, you can control the WordPress Heartbeat API. By default, the WordPress Heartbeat API checks every 15 seconds on your post edit pages and every 60 seconds on your dashboard and frontend whether there are scheduled tasks to be executed. This can generate high CPU usage if you leave browser tabs in which you’re logged in WordPress opened for a longer period of time. With this option, you can make the checks run less frequently or completely disable them. You have the option to change WP Heartbeat for three different locations and also modify the frequency of the Heartbeat.

Scheduled Database Maintenance

When enabled, this option schedules a database maintenance task that runs once every week. The optimization is performing the following operations: Database Optimization for MyISAM tables, deletes all automatically created post and page drafts, revisions, all posts and pages in your Trash, all comments marked as Spam or Trash and all expired transients.

Note that if your databases are using the InnoDB storage engine, the database optimization will be done automatically by the storage engine itself.

Tutorial Menu

Share This Article