❦In memory of Saber Rastikerdar — creator of · Vazirmatn, the open typeface he gave the Persian web and asked nothing for.
Frontend Engineering

Appearance

Performance Engineer — Learning Path ​

An engineer who owns the speed of the application across loading, runtime, and delivery.

Level: Advanced · Required: 91 articles (~19.0 h) · Optional: 16 articles (~3.8 h)

Difficulty of required articles: Foundational 24 · Intermediate 54 · Advanced 13.

Follow the sections in order. Articles link into docs/; each shows its difficulty and estimated reading time. Full prerequisites for any article are in its domain's graph.json (see GRAPH.md).

Milestones ​

  1. Measure and interpret Core Web Vitals in lab and field
  2. Optimize the critical rendering path and loading strategy
  3. Diagnose runtime cost, long tasks, and memory growth
  4. Tune caching across HTTP, build, and service-worker layers
  5. Prevent regressions with budgets and CI gates

Expected skills ​

By completing the required articles you should be able to:

  • End-to-end performance profiling and diagnosis
  • Loading, runtime, and memory optimization
  • Cross-layer caching strategy
  • A performance culture with budgets and monitoring

Required articles ​

The Web Platform ​

Runtime & Execution ​

Networking & Protocols ​

Performance Engineering ​

Build Systems & Tooling ​

Rendering Architectures ​

Data & Server State ​

Animation & Motion ​

Progressive & Cross-Platform Web ​

Observability & Reliability ​

Optional articles ​

Browser APIs ​

Graphics & Immersive ​

Delivery & Infrastructure ​

← All learning paths · Knowledge Map · Dependency Graph

Peer-reviewed engineering decisions · MIT licensed

Frontend Engineering