~/talk

Continuous web performance monitoring using Node.js

TalkinSpanishat NodeConf Argentina 2018 · 2018-10-18..10-20· [web-performance, nodejs]
links:none on file
slides:none on file

A company with 300 million users implemented continuous, user-centric web performance monitoring using Node.js by running Lighthouse (headless Chrome) to collect metrics like Time to Interactive and First Meaningful Paint under simulated 3G network and CPU throttling. They run automated per-page Lighthouse jobs that trigger alerts and block CI on SLO regressions, and found that measuring real interactivity (not just full load) reveals different optimization priorities because pages can appear fully loaded while still performing background work.

AI-written summary · about

  1. 0:00Start
  2. 3:26Monitoring the Navigation Timing API
  3. 8:16Monitoring user-centric metrics
  4. 11:36Lighthouse!
  5. 12:47Lighthouse architecture
  6. 13:34Using Lighthouse programmatically
  7. 14:36Network throttling
~/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.