
One second image LCP booster: meet the fetchpriority attribute
If optimizing was only as simple as adding a few attributes. But this time, it really is and it's even easier to use than image preloading.
Can't get enough? I'm regularly sharing snack bite tips and advice on LinkedIn as well.
If optimizing was only as simple as adding a few attributes. But this time, it really is and it's even easier to use than image preloading.
Wether you're reading a LinkedIn or Twitter discussion, there still is confusion around lazyloading images. Especially when it comes to above the fold images, such as hero images. Let's deal with this for once and for all.
Wondering why Lighthouse is recommending you to fix this, although you don't see any layout shifts yourself, and why is it warning you only now and not before?
To lazyload or not to lazyload images? From a user and performance perspective, you should lazyload images, but should you use a JS library?
Browsers are always trying to optimize as well. Some browsers already support lazyloading of images and iframes, using the loading attribute.