~/talk

12 Frontend Developer Mistakes or How to Optimize an Existing Product

TalkinRussianat OdessaJS 2015 · 2015-08-21..08-22· [frontend-architecture]
links:none on file
slides:none on file

A collection of thirty live frontend optimization case studies across 30 production sites, showing concrete before/after metrics (e.g. 355 requests and 18s to usable content vs 51 requests and 1s). Practical tools and fixes covered include Critical CSS, Picture/srcset, Chrome Audits, prefetch/DNS-prfetch, HTTP/2 tradeoffs, and removing unsafe cookie hacks, with demonstrated lifts in interaction and revenue.

AI-written summary · about

  1. 0:00Introduction
  2. 1:45What is optimization
  3. 3:33Too many HTTP requests
  4. 6:28HTTP/2 features and limits
  5. 7:13Unoptimized rendering
  6. 9:25Extra content bytes
  7. 12:15Wrong sharding use
  8. 13:43Unsafe code and cookies
  9. 16:12No user action prediction
  10. 18:05Ignoring rendering
  11. 19:22Unnecessary HTTP redirects
  12. 21:07Interface errors 9 & 10
  13. 24:36Uninformative error messages
  14. 26:23Poor navigation
  15. 27:52Successful page components
  16. 31:44Optimization results
  17. 32:28Q&A
~/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.