~/talk

How fast can web apps be?

Talkat Angular Connect 2016 · 2016-09-27..09-28· [web-performance]
slides:none on file

Empirical tests on midrange phones show heavy client-side apps can take multiple seconds to render page to page: network handshakes on typical 3G add about 2 seconds of latency and parsing large JS can cost 120 ms or more, while an average device used in demos is an $80 phone with 1 GB RAM that often fails on huge frameworks. Server-rendered HTML with inline styles/data, gzip, async/defer scripts, and streaming or delayed parsing yields far faster first paint and better perceived performance.

AI-written summary · about

  1. 0:00Introduction and examples
  2. 3:25Testing on real devices
  3. 7:52Understanding 3G latency
  4. 10:33Empathy for low-end phones
  5. 13:51Reddit performance example
  6. 16:47Optimizing HTML basics
  7. 18:37Performance tradeoffs
  8. 20:45Why speed matters
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.