Although the score is different, the problem on mobile is the same on desktop (as can be seen by clicking on the opportunities; you’ll see the same images listed); AO currently cannot lazyload background-images. As a result it cannot automatically switch them to webp either. I hope to have this fixed in AO26, but in the mean time the only 2 options are either leaving as is or switching from background-images to normal <img tags where possible.
hope this clarifies,
frank
Ah, that makes sense. Thanks for the reply!
you’re welcome. I’ll ping you here when background-images are supported in 2.6 beta so you can take is out for a spin 🙂
OK, this was the push I needed to finally get this in, just committed to the beta version on github, would be great if you could download AO26 beta to confirm if this indeed now also lazyloads (and webp’s) your background images! 🙂
frank
Wow, great support!
It appears as though the lazy loading and Webp categories have improved, but the overall score has decreased. :-/
I know this is outside of your free support, but would you be able to point me in the direction of how to address the Opportunity to eliminate render blocking resources? Am I missing a setting somewhere, or can I move around some code somewhere on the site? (I’m also using Async Javascript.)
I’m sure you’ll notice I’m using SG Optimizer for my cache plugin, but I’ve also tried WP Fastest Cache and gotten the exact same results. Since the client is using SiteGround hosting, I just stayed with that.
Thanks for everything!
Using SG-opt (or WPFC or …) is not a problem, it’s just that when combining with AO you should disable all CSS/ JS aggregation/ minification in the other plugin(s).
and when that is done, the next step is to go “inline & defer CSS” in AO to stop the CSS from being render-blocking, see the AO FAQ for more info.
Deactivating those features in SG already bumped the mobile score up to 33 (from 23). Time to dig into those other things and see if I can somehow deactivate Revolution Slider in mobile. I suspect that’s a really big and slow plugin.
I won’t comment on the use of revslider, but … 😉
Ha! You just said it all. I’ve inherited it from the client.
