Want to build faster websites? Here's how: - Learn how browsers parse, layout & paint - Treat JS as a tool, not the foundation(!) - Favor static HTML or server side rendering at all times - Use Core Web Vitals alongside other metrics to learn shortfalls, improve and iterate Then keep doing that.
Can we fine tune that “static HTML“ to semantic HTML instead? That means dibs are not primary elements but ratites when the object doesn’t already exist as primary semantic html. Div and span are not semantic. Button and list are.
It didn't fit for the purpose of my post and would have muddied the message. If I were to write a more general post (not strictly about performance), I'd say semantic, assistive technology accessible HTML. Comparatively, semantics don't offer much to viewers, but accessibility really does.
Fair point, but you said "faster" and suggested less JS. Semantics offers a lot to users, particularly faster & cleaner websites. But it looks like we're on the same page here.
I argue this at work but people look at me like I have 2 heads