~/talk

Measuring Web Performance - Metrics & Tools

Talkat JSUnconf 2017 · on Saturday, 2017-03-25· [web-performance, devops-and-delivery]

Concrete metrics and tools determine whether this is useful: concrete claims about Time to First Byte, First Meaningful Paint and Speed Index with video-based visual metrics, lab tools like webpagetest.org and Lighthouse, RUM via Boomerang JS or the rum speed index heuristic, emulation tools (Chrome low‑end device mode, Network Link Conditioner), a worked example of side‑by‑side video comparisons, and operational advice — set a performance budget (example: 1 MB JS or speed index <2000) and enforce it in CI.

AI-written summary · about

  1. 0:00Measuring web performance matters
  2. 1:03Resource-based metrics limits
  3. 3:13Timing-based metrics beyond load
  4. 5:40Custom visual performance markers
  5. 7:47Speed index and visual completion
  6. 10:18Browser tools for quick checks
  7. 12:06WISLO and PageSpeed Insights
  8. 14:41WebPageTest deep analysis
  9. 16:27Sitespeed.io modern alternative
  10. 17:54Google Lighthouse for Progressive Web Apps
  11. 19:37Real user monitoring in browser
  12. 21:05Navigation and resource timing APIs
  13. 22:29RUM Speed Index without video
  14. 24:12Boomerang JS tracking
  15. 25:16BrowserTime open-source RUM
  16. 26:19Performance budgets with teams
  17. 27:45Facebook’s 2G Tuesdays
  18. 28:29Performance side-by-side videos
~/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.