~/talk

Six bottles of RUM: Real World Mobile Performance

Talkat CascadiaJS 2013 · 2013-11-14..11-15· [web-performance]
slides:none on file

Measurements from real users show a cold TCP fetch for zero bytes taking 0-byte cold TCP ≈200–250ms, while a 6.7KB image drops to roughly 6.7KB image ≈100ms warm; average pages report 42 resources but many sites have 80–160, so serial costs add up. Cookies under keep cookies <400B have negligible cost but 4KB headers add ~50–60ms cold (≈20–25% warm). Domain sharding multiplies cold-connection costs—domain sharding hurts on mobile—HTTP/2 multiplexing and sprite usage (Amazon sprite tests) avoid those penalties; use cookie‑free domains and tune CDN/server timeouts.

AI-written summary · about

  1. 0:00Introduction to RUM
  2. 4:58Why mobile performance matters
  3. 12:24HTTP performance basics
  4. 17:22Domain sharding pitfalls
  5. 21:11HTTP/2 and connection limits
  6. 23:41CSS performance myths
  7. 28:34Key mobile performance takeaways
~/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.