knaxuslearn · build · ship

Roadmaps / Frontend / Phase 3

Phase 3 of 4 · Study weeks 9-12

Rendering, performance and budgets

This phase makes the third checkpoint possible: pages that render fast and stay inside a budget.

Topics every week

  1. Week 98 h
    • Rendering modes: client, server, static and streaming
    • Server components and their limits
    • Hydration and its cost
    • Caching rules

    Hand inA rendering table for each route with the reason

  2. Week 108 h
    • Bundles and code splitting
    • Tree shaking
    • Build tools and their plugins
    • A bundle budget in CI

    Hand inThe budget gate and a seeded oversize import that fails it

  3. Week 118 h
    • Long tasks and INP
    • Scheduling work
    • Virtualised lists
    • Memory leaks in single-page apps

    Hand inThe long-task fix found from a trace

  4. Week 128 h
    • Measuring 10 runs with spread
    • Lab against field
    • Performance budgets as policy
    • Reading a regression

    Hand inCheckpoint 3, with predicted and measured numbers side by side

Practice projects

  • Practice 1, the rendering table (Week 9): pick a rendering mode for each route. Done when: a table lists the mode, the caching rule and a measured reason for each.
  • Practice 2, the bundle gate (Week 10): set a limit on the first route. Done when: a seeded import of a large library fails the build and removing it passes.
  • Practice 3, the slow keystroke (Week 11): add a long task to every keystroke in search. Done when: a trace shows it, the fix is applied and INP is measured before and after.
  • Optional, an Angular cart: rebuild the cart in Angular with signals. Done when: a table compares bundle size, lines of code and INP with your React version.

GitHub repos to study

Existence and last commit were checked on 22 Nov 2026 by shallow clone. Every repository below had a commit in the last 12 months.

RepoWhat to readWeek
vercel/next.jsRendering modes and the caching documentation9
vitejs/viteThe dev server, bundling and plug-in hooks10
angular/angularSignals, change detection and the compiler11

Milestone checkpoint

Build Checkpoint 3. Write your predictions for LCP, INP and CLS and the bundle size first. Choose the rendering mode per route, add the bundle gate and the seeded oversize import, then run 10 times on the throttled profile. Seed the long task, find it in a trace and fix it. Hand in the 10-run table with spread, the CI output, ADR-5 (rendering modes) and ADR-6 (the budgets and who owns them).

Check yourself

Answer each question in your head first, then open it to check.

  1. What does server rendering improve, and what does hydration cost?
    It can make the first content arrive sooner. Hydration then re-runs component code in the browser to attach events, which costs CPU on slow phones.
  2. How does code splitting reduce what the user downloads?
    Each route loads only its own code, and heavy parts load when needed.
  3. What causes poor INP?
    Long tasks on the main thread, large re-renders after an interaction and work that blocks the next paint.
  4. How do you find a memory leak in a single-page app?
    Take heap snapshots before and after repeating an action, and look for objects that keep growing, often listeners or caches that are never released.
  5. Why enforce a budget in CI?
    A budget that nobody checks drifts. A failing build makes the cost of each new dependency visible when it is added.