Autoptimize
by Optimizing Matters 4.7 (1,428 reviews)

Autoptimize

Autoptimize speeds up your website by optimizing JS, CSS, images (incl. lazy-load), HTML and Google Fonts, asyncing JS, removing emoji cruft and more.

Autoptimize ranks #77 among WordPress.org plugins with 800,000+ active installations, is #12 of 1,518 in the Performance category, a 4.7/5 rating from 1,428 reviews, and was last updated Aug 20, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v3.1.15.1 Current Version v3.1.15.1
Updated 3 weeks ago Last Update on 20 Aug, 2026
Refreshed 11 hours ago Last Refreshed on
#12 of 1,518 in Performance Top 1% by installs Downloads -18.6% this week Actively maintained
View on WordPress.org
Rank
#77
No change
Active Installs
800K+
-6.7%
KW Avg Position
15.8
0.2 better
Downloads
43.1M
+2,393 today
Support Resolved
67%
No change
Rating
94%
Review 4.7 out of 5
4.7 (1,428 reviews)

Next Milestone 900K

Total Progress 57.1%
800K+ 900K+
3
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 42,858 more installs to reach 900K+

Rank Changes

57 67 77 87 97 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
57 67 77 87 97 31-08-2026 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
Current #77
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

1K 1.5K 2K 2.5K 3K 3.5K 4K 4.5K 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
1K 1.5K 2K 2.5K 3K 3.5K 4K 4.5K 31-08-2026 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.7
1,428 reviews
Overall 94%
5
1,289 (90%)
4
34 (2%)
3
21 (1%)
2
20 (1%)
1
64 (4%)

Support Threads Overview

Resolved
Unresolved
3
Total Threads
2
Resolved
1
Unresolved
67%
Resolution Rate

Security History

Source: WPVulnerability

17 known vulnerabilities on record · 4 in the last 24 months · checked 1 week ago

  1. Autoptimize [autoptimize] < 3.1.15

    CVE-2026-3220 · Fixed in v3.1.15

  2. Autoptimize [autoptimize] < 3.1.15

    CVE-2026-2430 · Fixed in v3.1.15

  3. Autoptimize [autoptimize] < 3.1.15

    CVE-2026-2352 · Fixed in v3.1.15

  4. Autoptimize [autoptimize] < 3.1.14

    CVE-2025-13401 · Fixed in v3.1.14

  5. Autoptimize [autoptimize] < 3.1.7

    CVE-2023-2113 · Fixed in v3.1.7

  6. Autoptimize [autoptimize] < 3.1.7

    Fixed in v3.1.7

  7. Autoptimize [autoptimize] < 3.1.7

    Fixed in v3.1.7

  8. Autoptimize [autoptimize] < 3.1.0

    CVE-2022-4057 · Fixed in v3.1.0

  9. Autoptimize [autoptimize] < 3.1.1

    CVE-2022-2635 · Fixed in v3.1.1

  10. Autoptimize [autoptimize] < 2.8.4

    CVE-2021-24332 · Fixed in v2.8.4

Showing the 10 most recent of 17 records.

TL;DR

AI summary of the plugin's readme

Autoptimize is for WordPress site owners who want to improve page speed without deep technical configuration. It solves slow-loading pages by optimizing and aggregating JS, CSS, images, HTML, and fonts to reduce load times.

  • Aggregates and minifies scripts and styles
  • Inlines critical CSS
  • Defers aggregated CSS
  • Moves scripts to footer
  • Minifies HTML
  • Lazy-loads images with WebP/AVIF support
  • Optimizes Google Fonts
  • Removes emoji cruft

Frequently Asked Questions

Common questions about Autoptimize

It minifies all scripts and styles and configures your webserver to compresses them with good expires headers. JavaScript be default will be made non-render-blocking and CSS can be too by adding critical CSS. You can configure it to combine (aggregate) CSS & JS-files, in which case styles are moved to the page head, and scripts to the footer. It also minifies the HTML code and can also optimize images and Google Fonts, making your page really lightweight.
HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests and for that reason on new installations Autoptimize will not aggregate CSS and JS files any more. That being said, concatenation of CSS/ JS can still make a lot of sense, as described in this css-tricks.com article and this blogpost from one of the Ebay engineers. The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it's just HTTP/2, maybe it's HTTP/2 + aggregation and minification, maybe it's HTTP/2 + minification (which AO can do as well, simply untick the "aggregate JS-files" and/ or "aggregate CSS-files" options). And Autoptimize can do a lot more then "just" optimizing your JS & CSS off course ;-)
Although Autoptimize comes without any warranties, it will in general work flawlessly if you configure it correctly. See "Troubleshooting" below for info on how to configure in case of problems. If you want you can test Autoptimize on a new free dummy site, courtesy of tastewp.com.
Starting from AO 2.1 WordPress core's jquery.min.js is not optimized for the simple reason a lot of popular plugins inject inline JS that is not aggregated either (due to possible cache size issues with unique code in inline JS) which relies on jquery being available, so excluding jquery.min.js ensures that most sites will work out of the box. If you want optimize jquery as well, you can remove it from the JS optimization exclusion-list (you might have to enable "also aggregate inline JS" as well or switch to "force JS in head").
This happens when aggregating JavaSCript and ticking the "force in head" option or when not aggregating and not deferring. Consider changing settings.
With the default Autoptimize configuration the CSS is linked in the head, which is a safe default but has Google PageSpeed Insights complaining. You can look into "inline all CSS" (easy) or "inline and defer CSS" (better) which are explained in this FAQ as well.
CSS in general should go in the head of the document. Recently a.o. Google started promoting deferring non-essential CSS, while inlining those styles needed to build the page above the fold. This is especially important to render pages as quickly as possible on mobile devices. As from Autoptimize 1.9.0 this is easy; select "inline and defer CSS", paste the block of "above the fold CSS" in the input field (text area) and you're good to go!
There's no easy solution for that as "above the fold" depends on where the fold is, which in turn depends on screensize. There are some tools available however, which try to identify just what is "above the fold". This list of tools is a great starting point. The Sitelocity critical CSS generator and Jonas Ohlsson's criticalpathcssgenerator are nice basic solutions and http://criticalcss.com/ is a premium solution by the same Jonas Ohlsson. Alternatively this bookmarklet (Chrome-only) can be helpful as well.
The short answer: probably not. Although inlining all CSS will make the CSS non-render blocking, it will result in your base HTML-page getting significantly bigger thus requiring more "roundtrip times". Moreover when considering multiple pages being requested in a browsing session the inline CSS is sent over each time, whereas when not inlined it would be served from cache. Finally the inlined CSS will push the meta-tags in the HTML down to a position where Facebook or Whatsapp might not look for it any more, breaking e.g. thumbnails when sharing on these platforms.
Autoptimize does not have its proper cache purging mechanism, as this could remove optimized CSS/JS which is still referred to in other caches, which would break your site. Moreover a fast growing cache is an indication of other problems you should avoid. Instead you can keep the cache size at an acceptable level by either: disactivating the "aggregate inline JS" and/ or "aggregate inline CSS" options excluding JS-variables (or sometimes CSS-selectors) that change on a per page (or per pageload) basis. You can read how you can do that in this blogpost. Despite above objections, there are 3rd party solutions to automatically purge the AO cache, e.g. using this code or this plugin, but for reasons above these are to be used only if you really know what you're doing.

Sign In / Register

You need to sign in or register to use this feature.