Was hoping to see the results, but the images were all blurry dummy placeholders (some sort of lazy loading for images?). The images had a text on "click here for preview", but when I clicked it, nothing happened (I have ad-blockers, maybe that's why some JS code was disabled).
But what the heck, this is not how wepages should work - click here to "unblur" the image? Why add such an extra step? To save bandwidth cost?
There seems to be a proper lazy-loaded image (with low-res + high-res) with a thumbnail (low-res) on top; and the thumbnail is removed with JS code.
This is probably meant as a fallback to look nicer on browsers which don't support lazy-loading, at the expense of breaking browsers which don't support JS or fail to execute it.
AFIK, that’s because the CDN provides the ability to make the original images as WEBP. I will let maintainers know this case, may I know which browser you’re using?
this is a feature of asynchronously loading the "heavy" images to unimpede the loading of the text and markup. The "click to unblur" is because it failed to automatically load the image, and as a fallback uses a CTA (i.e., an event triggered by the user explicitly) to reattempt to load the images. CTAs have a higher privilege for fetching content.
But what the heck, this is not how wepages should work - click here to "unblur" the image? Why add such an extra step? To save bandwidth cost?