It’s beginning to look a lot like Christmas ladies & gentlemen and I’m planning on putting Autoptimize 2.6 nicely wrapped up under your Christmas tree.
The new version comes with the following changes;
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.1.2 (5.2 is in beta now, might be integrated in AO26 if released in time).
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.
Large batch of misc. smaller improvements & fixes, more info in the [GitHub commit log](https://github.com/futtta/autoptimize/commits/beta).
So in order to make this the smoothest release possible I would like
the beta to be downloaded and tested by as many people as possible, including you!
Any issue/ question/ bug can be reported here as a reply or if a bug and if you’re more technically inclined over at
Github as an issue. Looking forward to your feedback!
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 …
Wolf Braun is a happy Autopitmize user and created this testimonial to tell the world just how great he thinks AO is;
Thanks Wolf, we agree! :-)
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!
Zwijg me (niet) van de laatste kutgroep uit Engelang! Crazy Squids feeding off houseplants (and cowbell);
Squid - "Houseplants" @ Hotel Vegas, SXSW 2019, Best of SXSW Live, HQ
Being wary of all things tracking by Google & Facebook, both of who’s products I love but data capturing practices I hate, for the last 4 years or so I always logged in into these in “Private browsing” sessions in Firefox (because
why trust the worlds biggest advertising platform with your privacy, right?)
Now I just “discovered” that the Mozilla team have rendered that somewhat clumsy procedure -which required me to log in each time I restarted my computer or browser- redundant with their
“Firefox Multi-Account Containers” add-on, allowing you to contain entire sessions to one (or more) tabs;
So now I have one browser window with a couple of tabs in the Google container, one tab in a Facebook container and all others in the “default” container where Google & Facebook can’t track me (fingerprinting aside, but
there’s an option for that).
Autoptimize was featured on the Smart Web Creators podcast, check it out below;