Addy Osmani's piece on the <img> element is worth reading in full: it surveys what the tag can now do and ties those capabilities back to user experience and the Core Web Vitals. For developers whose work lands in the DOM, treating image handling as core knowledge is not optional — images shape performance, accessibility, UX and SEO at once.

A companion Instagram summary of the same material is embedded here:

View this post on Instagram

A post shared by Addy Osmani (@addyist)

Decoding hints and open questions

The decoding="async" attribute remains an unresolved item. Some material suggests attaching it to every image, though Addy neither recommends that blanket approach nor offers guidance either way. If always-on async decoding turns out to be the right default, the better outcome would be for browsers to adopt that behavior natively, removing the need for the attribute. A related question: Addy advises loading the hero image as early as possible but suggests no further tricks. Whether deliberately withholding the hero until user interaction — a technique previously covered for gaming Core Web Vitals numbers — becomes good or bad practice is still unclear.

A word on "HTML developer"

The term "HTML developer" rarely comes up; "React developer" is the common construction. The footnote definition is broad: anyone writing code that ends up as the DOM qualifies, and with that comes responsibility for the experience the HTML delivers.

CSS-Tricks star logo

Advertisement

Direct link to the source piece, from Smashing Magazine.