HTML: How to Make Loveliness
summary
Uses concrete results: swapping client-side React rendering for server-side HTML cuts Javascript from 770 KB to 238 KB and drops load time from ~17 s to 4 s; adding structured data yields measurable gains (Eventbrite +100% search traffic, Jobrapido +115% organic, +270% new registrations, Rakuten 2.7× traffic); choosing real elements matters — use a label with an input and a button element not divs for built-in keyboard and focus support; picture element provides WebP fallback automatically; run automated accessibility tests (WebAIM finds 98% of top million homepages with errors). use semantic elements avoid unnecessary JavaScript
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:10TL; DR
- 1:53Tim Berners-Lee
- 2:57The raw materials
- 3:21HTML is declarative & fault-tolerant
- 5:31JavaScript is not declarative
- 6:56Don't rely on JavaScript
- 8:20HTML is more than div & span
- 11:22"Structured data"
- 14:19Accessibility is part of usability
- 15:55What can you do?
- 19:15How to make the Internet affordable
- 21:15The Internet matters
related talks
39mHow To Make Loveliness: an HTML treasure hunt
44mThe HTML Treasure Hunt: from JavaScripter to Front End Superhero in 29 Minutes
41mYou Really Don't Need All That JavaScript I Promise
50mAdvanced HTML for Good Developers
44mThe HTML Treasure Hunt: from JavaScripter to Front End Superhero in 29 Minutes
32mStay Away From My Path!
57mAdvanced HTML for Performance & Accessibility
30mAdvanced HTML for Performance & Accessibility
