This leads to a situation for users that’s almost worse than before. Instead of staring at a blank screen, now they get HTML lickety-split—excellent! But if they try to interact with what’s on screen, they’ll find that nothing is working yet. Even worse, once the JavaScript is delivered, and is being parsed, they probably can’t even scroll—their device is too busy interpreting all that JavaScript. Your users suffer.

Comment réduire l’impact des visuels sur les performances de decitre.fr tout en gardant une bonne qualité d’affichage ? WebP, images à haut ratio et LQUIP !

A way of validating data independently of the programming language, a sort of mustache / handlebars, but only in the world of data validation.

If I would need to implement image lazy-loading on a high-traffic e-commerce site today, I’d very likely go for a JS-based solution. Partly because the native solution only works in Chrome, but also because Chrome’s implementation is too eager and therefore not so effective.