. –\u00a0 The best option here is to tick this checkbox. With a new release, the developers could implement new functionality that may require a cache purge to be enabled.<\/span><\/p>\n\n\n\nCache Exclusions<\/b><\/p>\n\n\n\n
This section in the plugin configuration page includes three text fields that can help you exclude pages or posts from the cache. You can use the first text field to define in a comma-separated page or post IDs that you do not want to be cached. Inside the second text field, you can enter Regular Expressions matching a specific page path that you want to exclude. Finally, you can use the third text field to specify Regexes that match cookies, which should bypass the cache.<\/span><\/p>\n\n\n\nCache Inclusions<\/b><\/p>\n\n\n\n
The cache inclusion section has a single text field, which will allow you to add pages that you <\/span>NEED <\/b>to be cached, regardless of any exclusions you implemented above.<\/span><\/p>\n\n\n\nCache Minifications <\/b><\/p>\n\n\n\n
If you plan to combine the Cache-Enabler plugin with Autoptimize, then any cache minification should be disabled, as this is Autoptimize\u2019s bread and butter. If you want to use Cache-Enabler on its own, then you should use this drop-down and enable minification for HTML and Inline JavaScript.<\/span><\/p>\n\n\n\n2. Autoptimize Settings<\/h3>\n\n\n\n To access the Autoptimize configuration page, go to <\/span>Settings <\/b>> <\/span>Autoptimize<\/b>.<\/span><\/p>\n\n\n\n
As opposed to the Cache-Enabler, Autoptimize offers a wide variety of configuration options on its settings page. Some of them can have a positive impact on your site in terms of speed or page score (if this is something you care about), whereas others may slow down your site. It depends on the site, so it is tough to predict its demeanor. The settings we will provide here will be optimal for most websites; however, if you see a drop in performance, you should simply deactivate the setting causing this, and you will be fine.<\/span><\/p>\n\n\n\nAutoptimize has its settings distributed under five separate tabs. We will start with the first one – the \u201c<\/span>JS, CSS, and HTML<\/b>\u201d tab.<\/span><\/p>\n\n\n\n
JavaScript Options<\/h4>\n\n\n\n Optimize JavaScript Code?<\/strong>Aggregate JS Files?<\/strong>Also Aggregate Inline JS?<\/strong>Force JavaScript in <head>?<\/strong>Exclude Scripts from Autoptimize<\/strong>Add Try-Catch Wrapping?<\/strong>CSS Options<\/b><\/p>\n\n\n\n
Optimize CSS Code?<\/strong>Aggregate CSS Files?<\/strong>Also Aggregate Inline CSS?<\/strong>Generate Data: URIs for Images?<\/strong>Inline and Defer CSS?<\/strong>Inline All CSS?<\/strong>Exclude CSS from Autoptimize<\/strong>HTML Options<\/b><\/p>\n\n\n\n
<\/p>\n\n\n
\n
\nOptimize HTML Code? Enabling this option will activate minification for your HTML files, effectively removing unnecessary characters from these files (such as whitespaces), reducing their size. In practice, this option works great on most websites; however, it can cause issues sometimes.<\/span><\/b> Thus, it is better to activate it and see how your website will behave.<\/span><\/b><\/li>\n\n\n\nKeep HTML comments? If you select this option, Autoptimize will keep the comments for the HTML pages optimized.<\/span><\/b><\/li>\n<\/ul>\n\n\n\nCDN Options<\/b><\/p>\n\n\n\n
CDN Base URL <\/b>– If you are using a CDN, you can enter your CDN-based<\/span> URL inside to serve static pages from there. If you are using Cloudflare or any other proxy-based CDN service, this option will not be necessary.<\/span><\/p>\n\n\n\nCache Info<\/b><\/p>\n\n\n\n
This section of the page will show you the cache folder, which is writable, and its size is shown. It is useful to keep track of your cache disk usage and to verify whether the cache is working correctly.<\/span><\/p>\n\n\n\nMisc Options<\/b><\/p>\n\n\n\n
\nSave aggregated script\/css as static files? – You should leave this option selected unless your server does not handle expiry and compression correctly.<\/span><\/b><\/li>\n\n\n\nMinify excluded CSS and JS files? – If you enable this option, your CSS and JS files will benefit from minification, regardless of whether they are excluded from the cache or aggregated.<\/span><\/b><\/li>\n\n\n\nEnable 404 fallbacks?<\/strong> – This is a great recent addition to the Autoptimize arsenal. It ensures that your visitor will see a \u201c<\/span>fallback<\/strong>\u201d version of a page if, for some reason, the cached plugin content is no longer present. To ensure the proper delivery of the \u201c<\/span>fallback<\/strong>\u201d page, please add the following snippet of code in your <\/span>.htaccess<\/a>\u00a0file:<\/li>\n<\/ul>\n\n\n\nErrorDocument 404 wp-content\/autoptimize_404_handler.php<\/code><\/p>\n\n\n\n\nAlso optimize for logged in editors\/ administrators? –<\/span> You will typically see this option enabled by default on a fresh Autoptimize installation. However, we do not reckon it is necessary. To begin with, logged in users and admins will usually not pay that much attention to performance, and the speed benefits will not be that substantial. In addition to that, you are keeping things a lot cleaner, not having to deal with the extra cache.<\/span><\/b><\/li>\n\n\n\nAlso optimize shop cart\/ checkout? – The cart\/checkout page is very delicate, and we would recommend everyone disable any kind of cache form on it.<\/span><\/b><\/li>\n<\/ul>\n\n\n\nNext is the \u201c<\/span>Images<\/b>\u201d tab, where Autoptimize offers two options that will help reduce the size of images or enable the \u201clazy-load\u201d images. <\/span><\/p>\n\n\n\n