I just released AO26, which comes with a bunch of new features, improvements and bugfixes.
- New: Autoptimize can be configured at network level or at individual site-level when on multisite.
- Extra: new option to specify what resources need to be preloaded.
- Extra: add display=swap to Autoptimized (CSS-based) Google Fonts.
- Images: support for lazyloading of background-images when set in the inline style attribute of a div.
- Images: updated to lazysizes 5.2.
- CSS/ JS: no longer add type attributes to Autoptimized resources.
- Improvement: cache clearing now also integrates with Kinsta, WP-Optimize & Nginx helper.
- Added “Critical CSS” tab to highlight the criticalcss.com integration, which will be fully included in Autoptimize 2.7.
- Batch of misc. smaller improvements & fixes, more info in the GitHub commit log.
The release has been tested extensively (automated unit testing, manual testing on several of my own sites and testing by users of the beta-version on Github), but as with all software it is very unlikely to be bug-free. Feel free to post any issue with the update here or to create a separate topic in this forum.
Happy holidays to all!
So for those using AO who are seeing occasional 404’s on AO’d resources and (somewhat) into code; here’s a GitHub commit that might interest you;
(More later, gotta run now)
Fun fact; As per wordpress.org “popular plugins” ranking , Autoptimize is slowly but surely closing in on what used to be the go-to solution for Web Performance Optimization W3 Total Cache based on the “active installs” metric. Who would have thought? What a crazy ride …
Over the last couple of months Juanfran Granados from Mirai, an hotelier agency that used WordPress extensively, worked hard to add multisite administration capabilities to Autoptimize:
- If AO has been network-activated, there will be an entry-point in the network settings screens where one can configure Autoptimize for the entire network.
- On the subsites the AO settings screen will show a message that settings are done at a network level
- On the network-AO-settings there is an option to allow AO to be configured per site
- if AO has not been network-activated, things work as they do now; all settings are done on a per-site level
I have just merged his code into separate branch on Github and given that significant changes that went into this (almost all files changed), I need you and you and you and … to download and test that multisite-test branch before I merge the changes into the beta branch. Looking forward to your feedback!