In this post, we’ll share the best Autoptimize plugin settings to improve the performance and page speed of your WordPress site.
Before we dive into the best Autoptimize settings, let’s quickly go over three reasons why Autoptimize is a great optimization plugin.
- The free version of Autoptimize has a complete feature set for optimizing your WordPress site.
- Autoptimize is strictly an optimization plugin and does not do any HTML page caching. This means it is compatible with all web hosts – even ones with custom page caching configurations like Kinsta.
- Autoptimize has over 1 million active installs in the WordPress repository and is consistently updated with new features and bug fixes.
Autoptimize JS, CSS, and HTML Settings
Aggregate JS Files
Also Aggregate Inline JS
The “also aggregate inline JS” option extracts inline JS in your HTML, and combines it with Autoptimize’s optimized JS file. Since this option can cause a rapid increase in Autoptimize’s cache size, we recommend keeping this option disabled unless you have a specific reason to enable it.
<head> element, we recommend excluding those scripts from Autoptimize.
Exclude Scripts from Autoptimize
Add Try-Catch Wrapping
Optimize CSS Code
We recommend enabling this option. When “optimize CSS code” is enabled, Autoptimize will minify your CSS files.
Aggregate CSS Files
Autoptimize’s “aggregate CSS files” option will combine all of your CSS files into a single file. As we mentioned earlier, this feature may not benefit sites that support HTTP/2. We recommend A/B testing this option on your site to determine if there is any positive impact on page speed.
Also Aggregate Inline CSS
This option will move inline CSS to Autoptimize’s CSS file. While moving inline CSS to a browser-cacheable CSS file can reduce page size, we recommend leaving this option disabled in most cases.
Generate Data: URIs for Images
When this option is enabled, Autoptimize will base64-encode small background images and embed them into CSS. We recommend testing out this option to gauge the impact on your page speed. While encoding images into base64 format reduces the number of HTTP requests, base64 representations files are typically 20-30% larger than their binary counterparts.
Inline and Defer CSS
Inlining critical CSS can result in a significant speed boost for some sites. The idea here is inline styles that are required for elements that are “above the fold”. In practice, inline CSS usually targets elements like structural elements, global font families and sizes, and navigation styling.
By inlining these key elements, the larger complete CSS file can be loaded at a later time without impacting the look of the page. While it’s possible to manually extract critical styles, we recommend using a tool like this one to generate the styles as a starting point.
After generating the critical CSS, copy and paste it into Autoptimize settings.
The next step is to test your site’s frontend experience. If you notice some strange flashes of unstyled content (FOUC), you’ll likely need to identify those unstyled elements and add the corresponding styles into Autoptimize for inlining.
Autoptimize offers a “power-up” that automatically generates critical CSS for your WordPress pages. From our experience, this feature can occasionally slow down your site because it uses external API calls to generate the critical CSS. Thus, the initial critical CSS generation is dependent on the responsiveness of an external server. In most cases, the aforementioned method which doesn’t require any external API calls is a cleaner solution.
Inline all CSS
For most sites, we do not recommend inlining all CSS as it can increase page size dramatically. Furthermore, inlining all CSS makes it impossible for the web browser to cache CSS.
Exclude CSS from Autoptimize
Autoptimize’s HTML optimization can help reduce the size of your pages by removing whitespace.
Optimize HTML Code
We recommend enabling the “optimize HTML” code feature because it reduces page size by removing unnecessary whitespace in your HTML. While this feature is compatible with most sites, removing whitespace can cause glitches on some sites. Thus, we recommend testing HTML code optimization thoroughly before using it in a production environment.
Keep HTML Comments
Enable this feature if you would like to keep HTML comments for your optimized pages.
If you’re using Kinsta CDN or a proxy service with CDN capabilities like Cloudflare, you do not need to configure anything in Autoptimize’s CDN options. For an even quicker and easier boost to your overall optimization, you can consider minifying your code. This can be done right in the MyKinsta dashboard using the code minification feature.
If, however, you’re using a different CDN service to accelerate your assets, you would enter the CDN URL in this field.
Autoptimize’s “cache info” displays important information like the location and permissions of the cache folder, as well as the total size of the cached styles and scripts. If you see “No” next to “Can we write?”, you’ll need to work with your host to fix the folder permissions.
Autoptimize has a few miscellaneous optimization settings. If you’re having issues getting optimized CSS and JS files to load on your site, you may need to reconfigure some of the settings below.
Save Aggregated Scripts/CSS as Static Files
We recommend enabling this option to save aggregated files as static files locally. You may need to disable this if your server is not configured to handle file compression and expiry.
Minify Excluded CSS and JS Files
We recommend enabling this option to ensure all CSS and JS files are minified. However, if you notice some minification-related issues with some of your excluded CSS and JS files, you can go ahead and disable this option.
Also Optimize for Logged In Editors/Administrators
We recommend enabling this to ensure assets are optimized for logged-in editors and administrators. This is important if you are testing Autoptimize settings as a logged-in user.
Image Optimization in Autoptimize
Autoptimize features a built-in integration with ShortPixel for optimizing images. In addition to an image quality setting, Autoptimize’s integration also allows you to generate and serve WEBP versions of your images.
For Kinsta users, we do not recommend using the image optimization feature in Autoptimize. Instead, we recommend using the full-featured plugins from ShortPixel or Imagify directly. With the full plugin, you’ll have more granular control over optimization settings including rewriting images to use the
<picture> tag, which is required for WEBP support on Kinsta.
Autoptimize also includes lazy-loading functionality for images. We recommend enabling this feature to improve page speed for image-heavy pages. When lazy-loading is enabled, Autoptimize lets you exclude certain image classes and filenames from being lazy-loaded.
The exclusion setting is useful for images like logos, social icons, and other important image elements that shouldn’t be lazy-loaded. If you’re looking for a solution that offers more control over lazy-loading, check out our guide on lazy-loading images and videos in WordPress.
Extra Optimizations in Autoptimize
Autoptimize has a few different options for optimizing Google Fonts. The best option for you will depend on how your site utilizes Google Fonts.
- Leave as is.
- Remove Google Fonts.
- Combine and link in head.
- Combine and preload in head.
- Combine and load fonts asynchronously with webfont.js.
We don’t recommend using the “leave as is” option because it offers no speed benefit.
If Google Fonts isn’t a mission-critical requirement on your site, removing them and using a system font stack instead can have a huge positive impact on your page speed.
If you would like to keep Google Fonts on your site, we recommend testing out the last three options to find out which one works best for your site.
Remove Query Strings from Static Resources
If you’d like to remove query strings (e.g. ?ver=) from static resources, you can enable this option. The removal of query strings will not impact load time, but it may help improve your site’s score in GTmetrix, Google Pagespeed, and other performance testing services.
Preconnect to 3rd Party Domains
The preconnect directive allows your browser to connect to specified domains to process DNS lookups and SSL handshake negotiations before a full HTTP request is sent.
For example, if your site has a logo image that’s served from
https://site.kinsta.cdn.com/logo.png, you can instruct Autoptimize to add a preconnect directive to handle the initial DNS and SSL connections in the
<head> element before the HTTP request is made in the
<body> element of your HTML.
You can use your browser’s developer tools or inspector to find important external domains to preconnect to. In the example page below, there are external requests to the following domains.
These three domains can be added to Autoptimize’s preconnect list.
For performance reasons, we recommend adding no more than six domains to Autoptimize’s preconnect list because specifying preconnect directives for too many domains can result in a performance hit.
Preload Specific Requests
Preload directives instruct your web browser to download an asset as soon as possible. This directive is useful for downloading assets that are needed very early in the page load process. In practice, preloading is often used to speed up load times for custom fonts by loading them before they are requested in the page’s CSS.
We recommend consulting with a developer regarding which assets, if any, to preload on your WordPress site. As with many other performance-related tweaks, preloading too many assets can cause your site to load slower.
async HTML flag. While loading JS files asynchronously can improve page speed, we recommend doing adequate testing to make sure that no site functionality is affected.
If you know how to tweak its settings, the Autoptimize plugin is a solid option for WordPress users looking to boost site performance.
With basic features like HTML and CSS optimization and more advanced ones, such as the ability to specify preconnect and preload directives, Autoptimize has everything you need to optimize your WordPress site’s frontend performance.
If you’re interested in learning more about WordPress optimization and how to optimize your site’s backend, be sure to check out our comprehensive WordPress performance guide.
Awesome guide, thanks Kinsta team!
ps tiny typo in summary ‘If you now how’
Keep up the great work, love my Kinsta life :)
Thanks, Dominic the typo has been fixed! We are glad to hear you liked the guide.
Great article. I currently host my site with Kinsta and just installed KinstaCDN. If I decide to also install Autoptimze, will there be any conflicts? I have had errors before when using a CDN with a caching/optimization plugin.
Hello Moe, Kinsta CDN is compatible with Autoptimize. After you install Autoptimize, just make sure you add your Kinsta CDN URL to Autoptimize’s CDN settings as highlighted in the article.
A question please. I use WP Rocket on my site. Can or should Autoptimize be used along with it?
Hello Gust, if you are already using WP-Rocket, there is no need to use Autoptimize as well. WP-Rocket alreaady covers Autoptimize’s feature set, so you are all set!
I am using Autoptimize plugin for my WordPress website. Before using plugin my website was load very slowly.
But right now my website is loads faster, I was having trouble setting up the CDN, so I searched on Google, I found the article of Kinsta. Now I have set everything up.
Thanks for providing the information with us.
Hello Harish, glad to hear your website is loading faster now!
I installed Autoptimize last week and have hosting through Kinsta and use the site builder Elementor. Enabling Autoptomize was very helpful in increasing page speed. However, I accidentally had checked the “also aggregate inline JS” option since last week. My Autoptimize cache is now full. I have unchecked that box now but haven’t done anything further since I read people say clearing the Autoptomize cache can break the site in some cases. Is it safe to deactivate the Autoptimize plugin? Will selecting Clear Cache on the Autoptomize cache be ok or are there specific steps with Kinsta I should add?
Hello Eryn, you should be fine to clear the Autoptimize cache, as the JS files that were used to generate the inline code should still be there. I’d also recommend clearing your page cache as well.
I use Cloudflare that is minifying my css, js, html. Should i use Autoptimize now?
If you’re already using Cloudflare to minify assets, there’s no need to enable it in Autoptimize. However, you can use Autoptimize to combine assets still.
Great, in detail article!! Thank you so much for the instructions!