For a safe starting point, turn on Autoptimize’s Optimize JavaScript code, Optimize CSS code and Optimize HTML code options. Keep HTML comments, JavaScript-in-head, inline-all-CSS and data-URL image generation off. Treat file aggregation as an experiment—especially on larger sites—and pair Autoptimize with a full-page cache because Autoptimize does not cache complete pages.
The recommended starting profile
Autoptimize primarily minifies and reorganizes front-end assets. Minification removes unnecessary characters from JavaScript, CSS and HTML; aggregation combines files. Minification is generally the lower-risk change. Aggregation can reduce requests on a small site, but it also creates larger generated files, bigger cache entries and more opportunities for a script or stylesheet to conflict with another component.
As an Amazon Associate I earn from qualifying purchases.
| Autoptimize option | Starting value | Why |
|---|---|---|
| Optimize JavaScript code | On | Provides the basic JavaScript minification win. |
| Aggregate JS files | Test first; otherwise off | Useful mainly when the combined assets are small; aggregation can cause compatibility problems. |
| Aggregate inline JS | Off | Inline code can make the cache grow quickly and may disable functions such as popups. |
| Force JavaScript in head | Off | Loads scripts earlier and can make them render-blocking. |
| Add try-catch wrapping | Off | Enable only as a temporary diagnostic when aggregation causes a JavaScript error. |
| Optimize CSS code | On | Minifies CSS files with comparatively little setup risk. |
| Aggregate CSS files | Test first; otherwise off | The same small-site and compatibility trade-off as JavaScript aggregation. |
| Aggregate inline CSS | Off unless tested | Inline aggregation can increase cache size; the plugin’s own guidance allows disabling it when cache growth becomes a problem. |
| Inline all CSS | Off | It enlarges every HTML response and prevents those stylesheets from being cached separately. |
| Inline and defer CSS | Off initially | It changes loading behavior and should be enabled only after verifying the current release and testing the site. |
| Generate data URLs for images | Off | Embedding images in CSS can inflate stylesheets and is not a reliable general speed improvement. |
| Optimize HTML code | On | Removes unnecessary HTML characters. |
| Keep HTML comments | Off | Comments add bytes without helping visitors. |
This is a baseline, not a promise of a particular score increase. No published speed-gain statistic was established for Autoptimize, so measure your own pages after each change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Before changing settings
Back up and identify the active cache layers
Make a recent backup and note every system that can cache or rewrite assets: your hosting cache, a CDN, a page-cache plugin, a theme’s optimization features and any separate JavaScript or CSS optimizer. Running two tools that both aggregate or defer the same files can produce stale or broken output.
#1 Best Overall
Autoptimize does not cache full HTML pages. It creates optimized asset files and relies on another layer for complete-page caching. Add or keep a page-cache plugin, then configure it so its purge action also clears Autoptimize’s generated cache. A review specifically recommends pairing Autoptimize with WP Super Cache; the general requirement is a compatible full-page cache, not that particular product.
If you also need managed WordPress hosting, Antihost Managed WordPress places each site in an isolated environment and includes one-click staging, free migration, automated and manual backups and free SSL. A 14-day free trial has nothing due on day one.
Choose representative URLs
Record a home page, a typical post, an archive, a page containing a form, and any page with a popup, slider, shop cart or logged-in user interface. Test both mobile and desktop views. A setting that looks good on a brochure page can break a checkout, search form or interactive menu.
Capture a baseline
Run the same URL through GTmetrix or PageSpeed Insights before editing. Save the report, screenshots of the layout and a list of interactive behaviors that work. Scores fluctuate with network and server conditions, so compare repeated runs made in the same tool and location rather than treating one score as a laboratory result.
JavaScript settings
Optimize JavaScript code: on
Enable Optimize JavaScript code first. It minifies JavaScript files without changing the loading order by itself. Clear Autoptimize, page and CDN caches after saving, then test menus, forms, search, cookie controls, sliders and any logged-in controls.
Aggregate JS files: a test-first choice
Aggregation combines separate JavaScript files into generated bundles. Fewer requests can help a small site, but a bundle can also become large, change execution order and make one incompatible script affect every page that uses it.
One guide uses roughly 10 KB of combined JavaScript/CSS as a decision heuristic when inspecting a GTmetrix waterfall. That is guide advice, not an Autoptimize limit or a published web-performance standard. If your relevant files are around that size, test aggregation; if they are substantially larger or supplied by many plugins, leave it off initially and compare results.
When you test it, change only this option, purge every cache and inspect the browser console as well as the visual page. Keep aggregation only if the page is faster or equally fast and all interactions still work.
Rank #3
Aggregate inline JS: off
Inline JavaScript is code embedded in the HTML rather than loaded from a file. Aggregating it can make Autoptimize’s cache grow rapidly because small page-specific differences create additional generated variants. A guide also reports a popup failing after this option was enabled. Leave it off unless you have a measured, site-specific reason and have tested every page type.
Force JavaScript in head: off
Forcing scripts into the document head causes them to load earlier. That can make rendering wait for JavaScript and increase render-blocking work. Do not use it as a general fix for a missing script. If one file needs a different treatment, exclude that file from optimization or aggregation instead and test the affected feature.
Add try-catch wrapping: off by default
Try-catch wrapping can help reveal or contain a JavaScript failure after aggregation, but it changes the generated code and can conceal the underlying incompatibility. Use it only while diagnosing a confirmed aggregation problem. Excluding the conflicting file is usually the cleaner long-term remedy.
CSS settings
Optimize CSS code: on
Turn on Optimize CSS code to minify stylesheet files. After purging caches, check typography, spacing, responsive breakpoints, hover states, menus, modals and any page builder components.
Aggregate CSS files: test on small sites
CSS aggregation has the same basic trade-off as JavaScript aggregation: fewer requests versus a larger generated file and a larger blast radius when a stylesheet is incompatible. Start with it off on a plugin-heavy or frequently changing site. On a small site with a modest waterfall, enable it temporarily, test every representative URL and retain it only when the measured result and visual output justify the added complexity.
Aggregate inline CSS: the conservative default is off
Guides disagree about this switch. One setup lists it as enabled, while the official plugin listing advises disabling inline aggregation if cache size becomes a problem and its FAQ suggests disabling inline JavaScript and/or inline CSS aggregation to keep cache growth acceptable. Because inline rules vary by page, leave this option off until you have tested cache size and page behavior on your own site.
Inline all CSS: off
This option puts all stylesheet content into the HTML document. The response becomes larger, and visitors cannot reuse a separately cached CSS file across pages. It can be useful only for a narrowly tested delivery strategy; it is not a safe general-purpose speed setting.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Inline and defer CSS: evaluate cautiously
This option changes stylesheet delivery in a way that is close to a critical-CSS approach, but current-release behavior was not confirmed in the available documentation. Leave it off for the initial profile. If you test it later, inspect first paint, layout shifts, fonts, print styles and every responsive breakpoint, and verify that a cache purge regenerates the expected files.
Best Value
- Offer contains ONLY 2 titles regardless of the order quantity placed for this listing. Set of volumes may vary. Ordering in multiples will not change the volume received. Image is meant to display the type of book you will be receiving only.
- BRAIN TEASING. Perfect Puzzle Book for all ages to learn. Enjoy puzzles, maze, word search, or crosswords! This puzzle book is ideal for people on the go and will provide hours of entertainment.
- FUN & CHALLENGING. Exercise your brains long-term memory, working memory, executive functioning, attention to detail, multitasking, and processing speed. Perfect gifting item for those who love word search puzzles!
- RELAX, RECHARGE, & REFOCUS. The word find puzzle book offers an enjoyable challenge for all, from beginners to experts. Ideal for learning, practicing, and having fun time for various users.
- OFFICIALLY LICENSED. High-resolution printing. Perfect for family activities, classroom learning, or travel. Provide an engaging, educational experience with every page, making it both fun and meaningful.
Generate data URLs for images: off
Data URLs encode images inside CSS. That can remove a request for a tiny asset, but it also increases the stylesheet size and can make caching and debugging harder. Keep it disabled unless a narrowly measured case proves a benefit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.HTML settings
Optimize HTML code: on
Enable Optimize HTML code to remove whitespace and other unnecessary characters from the markup. Verify that forms, structured data, conditional comments, inline scripts and any HTML-sensitive widget still behave correctly.
Keep HTML comments: off
Leave Keep HTML comments disabled. Comments are not rendered for visitors and retaining them adds bytes. If a developer needs comments while debugging, turn the option on temporarily, then restore the production value and clear caches.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to apply the profile safely
- Open Autoptimize settings. Work in the JavaScript, CSS and HTML tabs, and note the existing values before changing them.
- Enable the three minification options. Turn on Optimize JavaScript code, Optimize CSS code and Optimize HTML code. Keep comments off.
- Leave high-risk delivery changes disabled. Do not force JavaScript into the head, inline all CSS or generate image data URLs during the initial pass. Keep inline aggregation disabled.
- Save and purge. Save Autoptimize, purge its generated files, purge the page cache and purge the CDN cache if one is present. Otherwise you may be testing old HTML that points to old assets.
- Exercise the site. Visit the representative URLs while logged out and, where relevant, logged in. Submit forms, open menus and popups, search, resize the viewport and check authenticated controls.
- Measure consistently. Re-run the same URLs in GTmetrix or PageSpeed Insights using comparable test conditions. Record load metrics, not just the headline score.
- Test aggregation separately. If the baseline suggests a request-count benefit, enable either JS or CSS aggregation—not both at once—purge caches and repeat the functional and performance checks.
- Keep or revert. Retain a change only when it does not introduce errors and produces a repeatable benefit. If something breaks, revert the most recent aggregation or delivery change first.
Troubleshooting common failures
A popup, menu or form stops working
- Purge every cache and test in a private browser window; stale generated files can imitate a code error.
- Open the browser developer console and identify the first JavaScript error, not just the later cascading errors.
- Disable the last JavaScript aggregation or inline-JavaScript change. If the feature returns, exclude the responsible file rather than forcing all JavaScript into the head.
- Retest the same feature on mobile and desktop and on both cached and uncached requests.
The page is unstyled or layout shifts badly
- Revert the latest CSS aggregation, inline-all-CSS or inline-and-defer change.
- Check that the generated stylesheet URL returns successfully and is not blocked by a CDN, security rule or stale cache.
- Inspect responsive breakpoints, fonts, pseudo-elements and print styles before re-enabling any delivery optimization.
Cache size grows unexpectedly
- Disable Aggregate inline JS and Aggregate inline CSS first; page-specific inline content can create many generated variants.
- Clear old Autoptimize files after changing the setting and confirm that the page cache is not retaining obsolete asset references.
- Review whether another optimizer is generating a second set of bundles.
Aggregation conflicts with another plugin
The Autoptimize FAQ documents the AUTOPTIMIZE_INIT_EARLIER wp-config.php define for changing initialization order. Use that only when you understand which plugin must initialize first, make a backup before editing wp-config.php, and test on a staging copy when possible. Changing initialization order does not remove the need to exclude incompatible files.
When to avoid aggregation
- Large, plugin-heavy sites: many independent scripts and styles increase the chance that one bundle breaks a feature.
- Frequently changing pages: inline content can multiply generated cache variants and erase the practical benefit.
- Sites already using a capable bundler or theme optimizer: a second aggregation layer can duplicate work and complicate cache invalidation.
- Sites where reliability matters more than a small request reduction: minification alone is easier to maintain and roll back.
Aggregation is not automatically bad; it is simply the setting that deserves evidence from your waterfall and functional tests rather than a permanent default.
A maintenance routine for Autoptimize
- After installing, removing or updating a plugin, theme or page builder, purge Autoptimize, page and CDN caches.
- Recheck one interactive page and one content page after each update.
- Keep a short change log of enabled options and the date of each performance test.
- When a regression appears, revert the newest aggregation or CSS/JavaScript delivery change before changing several settings at once.
- Repeat tests on the same representative URLs so improvements and regressions remain comparable.
What the settings can and cannot do
These options optimize the delivery of existing HTML, CSS and JavaScript. They do not replace image compression, efficient hosting, database maintenance, a CDN or a full-page cache. Autoptimize also does not establish a universal speed percentage: the outcome depends on the theme, plugins, cache headers, network and page composition. Treat the settings as a controlled optimization layer and use your own repeatable measurements to decide whether a change belongs in production.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
