~/talk

FaCSSt: CSS & Performance

Talkat JS Fest 2018 · on Friday, 2018-03-30· [css, web-performance]

Slides and experiments show concrete, actionable findings: a 1 MB stylesheet takes about 200 ms parse on a Moto G, base64-encoding images in CSS makes parsing massively worse (measured as 10× slower first paint on mobile and ~32× selector-parse slowdown), @import creates long request chains that flatten to many extra RTTs, switching to multiple link rel files drops start‑render from ~2.5s to ~0.5s, mixins gzip better so compiled CSS hits 12 KB under TCP magic, and moving critical CSS to another asset domain can add DNS/TCP/TLS overhead and slow things.

AI-written summary · about

  1. 0:00Introduction
  2. 2:25My work
  3. 3:04Why does it matter
  4. 4:23Final size
  5. 5:30Light vs CSS
  6. 6:13Basics T4
  7. 7:20Critical Path
  8. 10:09Import
  9. 13:03Selector Performance
  10. 21:00Alphabetic CSS
  11. 31:52Inline script block
  12. 35:26Wrap up
  13. 36:58Questions
  14. 40:05Time
  15. 41:15SVG vs Font
  16. 43:34Google PageSpeed
  17. 49:59Static Analysis
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.