Announcing Autoptimize 2.5

Q about Lazy Loading. Will it work with masonry galleries that require you to have a size for the image and the gallery to render properly? That’s one area of contention with lazy loaders. I’ve found ONE (and only one) that does it right, which is LazyLoader and uses some other plugin to calculate the image sizes first.

Masonry can be difficult; I do have it working on a customer’s site, but had to add one line of JS to make it work perfectly.

Does your lazy load feature include the fancy fade in? The one thing I dislike about what I’m using now is how the image snap in.

I don’t mind adding additional javascript as long as it works to make the gallery show up correctly. When this is released, do you think that can be added to the core?

re. fancy fade-in: when using image optimization (the shortpixel implementation in AO), a “low quality image placeholder” is loaded immediately and is replaced with the real optimized image when lazyload triggers. if image optimization is not active, there is no LQIP, so no fancyness ??

re. additional JS: it requires the ID of the div that encompasses the masonry grid which can be different for each site, so can’t move this in the core, but I’ll probably add example code in the FAQ.

Thanks.

Re: custom code – Maybe useful to have a field in the settings for a class, that would effectively eliminate the per gallery issue.

hmm, I feel masonry is a tad to specific to feature in the UI ??

Even a little old check box and field? lol. I don’t think it’s that specific to be honest. Almost ALL themes offer a Masonry option, so do page editors etc. It’s very common these days.

I tested 2.5.0-beta5 and unfortunately this doesn’t work properly for me.

Google PageSpeed Mobile section still warns me about “Defer offscreen images” and “Serve images in next-gen formats”, even though I have all options in Images tab checked, cleared cache and tested multiple times. Chrome dev tools still won’t recognize any image as WebP in Network section, even though they are served from ShortPixel CDN.

I also don’t see any low quality placeholder being served from CDN, is it intended? I didn’t notice any placeholders showing up at all.

I use free Cloudflare, so no Polish is active. Multiple Google PageSpeed and GTmetrix tests don’t show any loading speed change from selecting these settings.

This made me look for alternatives – Optimole plugin improves speed by significant amount, files are WebP and Google PageSpeed positively audits mentioned problems. I hope that ultimately this will work for Autoptimize too and I’ll be able to see what is faster / better for the eye, when the page loads.

@taisho: thanks for the feedback ??

re. webp; there’s an issue at Shortpixel which results in webp not being served, should be fixed before AO25 goes live.

re. lazyload; should work (see my own site for example), would like to look into that, can you share your URL?

I’m troubleshooting Optimole at the moment (despite speed gain, WebP are somehow larger than vanilla images). Will let you know when I have Autoptimize set up for WebP image serving.

Indeed lazy loading works on your blog. What I learned from author of WebP Express is that his plugin didn’t serve WebP for my WooCommerce product image gallery thumbnails, because this image gallery is JS generated (while Optimole doesn’t care and works there!). Maybe it could be the issue.

• This reply was modified 5 years, 7 months ago by taisho.

Optimole problem solved, it came out that auto compression was 100 quality, so even WebP had larger size than WordPress 82 quality thumbnail, how silly.

Now it’s deactivated and everything in Image tab in Autoptimize is set, cache purged.
1. All images are hosted by ShortPixel, but Chrome says not WebP.
2. I excluded logo from lazyload, because it kept annoyingly blinking, by typing “custom-logo” in exclusions, this works great.
3. Google PageSpeed hates me for what I mentioned in my first post + “Serve static assets with an efficient cache policy” which is 30 days on ShortPixel.

The link is:
https://parymet.pl/sklep/dystans-montazowy-stal-nierdzewna-satyna/

-> not webp; that’s a known issue, waiting for shortpixel to fix ??
-> re cache policy; 30d is not too bad, but maybe this can be longer somehow, what do you think @shortpixel ?

I forgot to mention, on WordPress 5.1, PHP 7.3 I’m receiving the following notices and some extra notices whenever I update any of my plugins:

Deprecated: strpos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in /home/platne/serwer24774/public_html/wp-content/plugins/autoptimize-beta/classes/external/php/plugin-update-checker/Puc/v4p4/Plugin/UpdateChecker.php on line 641

Warning: Cannot modify header information – headers already sent by (output started at /home/platne/serwer24774/public_html/wp-content/plugins/autoptimize-beta/classes/external/php/plugin-update-checker/Puc/v4p4/Plugin/UpdateChecker.php:641) in /home/platne/serwer24774/public_html/wp-admin/includes/misc.php on line 1198

• This reply was modified 5 years, 7 months ago by taisho.

@optimizingmatters

Thanks for your help on this forum, it’s much appreciated.

Our developer is having some trouble getting WebP images to show on compatible browsers, despite having the AO > Images > “Optimize Images” ON , “Load WebP in Supported Browsers” ON, and “Lazy Load Images” ON.

We’ve also disabled Smush and Simple Images Sizes on his recommendation, but still aren’t getting .webp images when performing the following tests.

– Source code shows “cdn.shortpixel.ai” for images.
– Right-click on image > Open in New Window shows vanilla file extension, not webp.

You mentioned above: “re. webp; there’s an issue at Shortpixel which results in webp not being served, should be fixed before AO25 goes live.”

Is this still an issue? i.e. Should we be waiting for a fix instead of chasing our tails? ??

Thanks in advance,
KV

AO/ Shortpixel does not change the file extension, but the image should be a webp-image nontheless (the bug mentioned has been fixed a long time ago). If you can share your URL I can have a look.

(next time better open a new support ticket here instead of replying to an old one)

frank