LiteSpeed Cache for WordPress Settings: Tuning

Optimize and Tuning are two closely-related tabs. Generally-speaking, you will find the ON/OFF switches in Optimize, and the customizations that go along with these switches in Tuning.

For a detailed explanation of what these tabs do, please see Optimization Through Minification and Combination

Please test these options thoroughly before enabling them on your production site!

off

Normally, combined CSS is loaded after external CSS files. This is because combined local CSS is more likely to have customizations that need to be loaded after the base CSS. Enable this option if you have reason to load combined CSS before other CSS files.

empty string

If you enabled minification, combination or push for CSS in the Optimize tab, you may exclude some CSS here. Use this space to list any CSS files (one per line) you would like excluded from the optimization functions. You may enter full URLs or a partial string. There's no need to use wildcards in partial strings.

off

Normally, combined JavaScript is loaded after external JavaScript files. Enable this option if you have reason to load combined JavaScript before other JS files.

empty string

If you enabled minification, combination or push for javaScript in the Optimize tab, you may exclude some JS here. Use this space to list any JS files (one per line) you would like excluded from the optimization functions. You may enter full URLs or a partial string. There's no need to use wildcards in partial strings.

1.2MB

A larger file size results in fewer combined files needing to be generated. This is good for your page score, but beware: if a combined file is too large, it will cause heavy memory usage. We consider 1.2MB to be a good starting point. Adjust it up or down to meet your site's needs.

off

This setting strips the query string from static resources. Static resources with query strings may not be cached by browsers and proxy servers. Removing the strings allows them to be cached, which translates into a faster page load.

off

You may not wish to enable asynchronous loading of all of your CSS, but you do want it for just the Google Fonts. If enabled, this option will allow you to load Google Fonts asynchronously without also loading the other CSS that way. Additionally, this option adds a preconnect to Google so that the fonts may be downloaded more quickly.

As of v2.7.3, this option has been improved, and now results in even faster page load times. Learn more.

off

This options removes all Google fonts from your site. Be sure to test this. Unless you have suitable replacement fonts stored locally, the style of your site could change dramatically.

empty string

When Load CSS Asynchronously is enabled in the Optimize tab, critical CSS is generated automatically. You may wish to single out a few additional definitions that must be loaded first in order to properly style above-the-fold content. Enter those rules here in plain CSS, just as they appear in your stylesheet. They will be appended to the generated CSS.

empty list

If Load JS Deferred is enabled in the Optimize tab, there may be some JavaScript files you do not want to be deferred. List them here, one per line. You may list the full URI or partial strings to be matched (no wildcards).

off

If enabled, this setting removes the extra JavaScript file that is used to add support for emojis in older browsers. Visitors who use modern browsers that have their own native emoji support will not notice a difference.

empty string

If there are pages you would like to exclude from optimization, you may list them here. You can use a full path, or a partial string.

unchecked

There may be user roles that you wish to exclude from any sort of optimization. For example, if you are an admin, testing new functionality, you may want to exclude your administrator role from optimization until your testing is through.

  • Admin
  • Last modified: 2019/04/12 18:37
  • by Lisa Clarke