10303 shaares
289 private links
289 private links
There are many methods that break performance and accessibility such as dynamic css classes and div and span soup.
Topics adressed from the outline:
- It’s not just bad HTML – it’s meaningless markup
- Semantic rot wrecks performance
- Big DOMs are slow to render
- Complex trees cause layout thrashing
- Redundant CSS increases recalculation cost
- Autogenerated classes break caching and targeting
- Animations and the compositing catastrophe (with properties triggering the layout engine)
- Autogenerated classes break caching and targeting
- Semantic tags can provide layout hints
- (AI) Agents are the new users and they care about structure
- Structure is resilience, isn't optional
Likewise,
content-visibility: auto
is one of the most underrated tools in the modern CSS arsenal. It lets the browser skip rendering elements
that aren’t visible on-screen – effectively “virtualising” them. That’s huge for long pages, feeds, or infinite scroll components.
and I didn't know about the contain CSS property.
contain: layout;
tells the browser it doesn’t need to recalculate layout outside the element.
will-change: transform;
hints that a compositing layer is needed.
isolation: isolate;
andcontain: paint;
can help prevent visual spillover and force GPU layers.