~/talk

Performant web animations — Emily Hayman

Talkat JAMstack Conf 2017 · 2017-05-24..05-26· [web-animation, web-performance]
slides:none on file

Aim for 60fps (16.7ms per frame) by only animating properties that hit the compositor: transform and opacity. Use will-change to promote heavy or fixed elements to their own layer, apply requestAnimationFrame for imperative timing, and prefer CSS animations when possible for browser optimizations. Watch for layout thrash (read then write), use CSS containment for isolated widgets, and fall back to pragmatic hacks — e.g., replace thousands of SVG nodes with an image on touch devices when event listeners kill performance.

AI-written summary · about

  1. 0:00Introduction to performance
  2. 0:48Why performance matters
  3. 2:39Browser rendering internals
  4. 5:54Optimizing CSS properties
  5. 8:23Manual layer promotion
  6. 10:32The 'will-change' property
  7. 13:05Imperative vs declarative
  8. 16:01Avoiding layout thrashing
  9. 16:52CSS containment
  10. 18:12Hack-based optimizations
  11. 19:35Performance testing tools
~/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.