Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:lscwp:configuration:optimize [2018/07/06 13:54]
Lisa Clarke [Generate Critical CSS] Proofreading additional content
+++ litespeed_wiki:cache:lscwp:configuration:optimize [2018/10/04 18:33]
Lisa Clarke [Generate Critical CSS in the Background] Added placeholders for Separate CCSS
@@ Line 7: / Line 7: @@
 **Please test these options thoroughly before enabling them on your production site!**
-{{:litespeed_wiki:cache:lscwp:lscwp-settings-optimize.png?direct&799|}}
+{{:litespeed_wiki:cache:lscwp:lscwp-settings-optimize.png?direct&800|}}
 ===== CSS Minify =====
 //OFF//
 Extra white space characters, new line characters, and comments will be stripped from all included CSS files, if this option is enabled.
-===== Inline CSS Minify =====
-//OFF//
-Extra white space characters, new line characters, and comments will be stripped from all inline CSS code on the HTML page, if this option is enabled.
 ===== CSS Combine =====
@@ Line 32: / Line 27: @@
 Extra white space characters, new line characters, and comments will be stripped from all JS, if this option is enabled.
-===== Inline JS Minify =====
-//OFF//
-Extra white space characters, new line characters, and comments will be stripped from all inline JS code on the HTML page, if this option is enabled.
 ===== JS Combine =====
@@ Line 57: / Line 47: @@
 Extra white space characters, new line characters, and comments will be stripped from all HTML, if this option is enabled.
+==== Inline CSS Minify ====
+//OFF//
+Extra white space characters, new line characters, and comments will be stripped from all inline CSS code on the HTML page, if this option is enabled.
+==== Inline JS Minify ====
+//OFF//
+Extra white space characters, new line characters, and comments will be stripped from all inline JS code on the HTML page, if this option is enabled.
 ===== Load CSS Asynchronously =====
@@ Line 65: / Line 65: @@
 When you turn this option ON, CSS and HTML will be loaded at the same time. The page can load more quickly this way, but it may initially load without formatting. To avoid that problem, you will want to generate the Critical CSS and load that first. That is what the next setting is for.
-===== Generate Critical CSS =====
+==== Generate Critical CSS ====
 //ON//
@@ Line 84: / Line 84: @@
 There is one small issue: when your site has not yet had the Critical CSS generated (or after a Purge All), the first visitor to request a page will need to wait for the above process to complete before the Critical CSS styles are available. That can take a few seconds that the visitor may not be willing to spend. This leads us to the next setting.
-===== Generate Critical CSS in the Background =====
+==== Generate Critical CSS in the Background ====
 //ON//
@@ Line 97: / Line 97: @@
 If **Generate Critical CSS in the Background** is set to ''OFF'', then the critical CSS is generated in the foreground, immediately when the page is requested. This means that the visitor must wait for the critical CSS calculation before continuing to view the page. This has the potential to slow down page load.
+==== Separate CCSS Cache Post Types ====
+Coming soon.
+==== Separate CCSS Cache URIs ====
+Coming soon.
+==== Inline CSS Async Lib ====
+//ON//
+This will inline the asynchronous CSS library to avoid render blocking.
 ===== Load JS Deferred =====