FSD Frontend System Design

Part III β€” The Speed

5 Performance

GoalMeasure what users feel, then fix it in the order that actually moves the number.

  1. 5.1 Performance Overview Three metrics describe what a user feels: is it there, does it respond, does it stay still. Core Web Vitals on a page-load timeline Β· 14 min
  2. 5.2 Performance Importance Latency is a business metric β€” it moves conversion, retention, and reach, not just Lighthouse scores. Latency vs conversion curve + who your slow users are Β· 12 min
  3. 5.3 Performance Monitoring Lab tests tell you what changed; field data tells you what users actually got. RUM vs synthetic + percentile distribution Β· 15 min
  4. 5.4 Performance Tools Read the waterfall before you read the code β€” the shape of the chart names the bottleneck. Annotated waterfall + which tool answers which question Β· 16 min
  5. 5.5 Network Optimization Fewer round trips, closer bytes, fewer bytes β€” in that order, because that's the order of impact. Before/after waterfall with preload and parallelisation Β· 18 min
  6. 5.6 Rendering Patterns Where and when HTML gets built β€” CSR, SSR, SSG, ISR, streaming β€” decides your LCP before you write a line. Six patterns on the same timeline Β· 18 min
  7. 5.7 Build Optimization Ship only the code this route needs, compress it, and let the browser cache it forever. Bundle treemap before/after + caching split Β· 17 min

Capstone

Take a page with a 6-second LCP under 2.5s. List every change you made and the milliseconds each one saved.