CSS containment and the cost of a repaint
A while back I spent two days chasing a jank issue that turned out to be one property: contain. Not because it was set, but because it was not.
The list re-rendered 40 rows every time a single row changed. Layout was recalculated for the whole subtree, and the browser had no way to know a row was independent.
The fix
li { contain: layout paint; }
A single declaration, and the frame time dropped from 14ms to under 4ms on a mid-range laptop. The lesson is not "use contain everywhere" — it is that the browser needs hints about what can change independently, and it will not guess.
Where it hurts: elements whose children overflow visibly, and anything relying on size containment for intrinsic sizing. Test with real content, not lorem ipsum.