I’ve set up a demo page with Mirage activated on the domain. As per the documentation, appending ?forcepreloadonly to the URL will only deliver degraded images.
However, I’m not able to see the degraded image. I tested from Chrome mobile user-agent and slow emulated network.
¡Hola Gijo!
I’ve tested with an actual mobile device on a slow network and per
we can see that Mirage seems to be working.
Hope this helps.
¡Gracias!
Alex
Any idea why Google PageSpeed Insights is still giving the warning “Properly size images”. Report: https://pagespeed.web.dev/report?url=https%3A%2F%2Fgijovarghese.com%2Fhello-world%2F
¡Hola Gijo!
Seems like the images are just larger than they’d need to be.
Per Website Speed Test - Image Analysis Tool by Cloudinary
evgeny-1536x864.jpg is 1536x864 but could be 580x326
solen-scaled.jpg is 1707x2560 but could be 580x870
screenshot-1536x864.png is 1536x864 but could be 580x326
Hope this helps.
¡Gracias!
Alex
But, Mirage should deliver smaller images on mobile, right?
Mirage detects mobile and slow network conditions and loads image thumbnails initially to improve FCP, then it loads full images with JS logic. So the purpose of Mirage to improve FCP, but it loads full images anyway at the end.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.