A dependency chain is an ordered sequence of operations in which each later operation waits for preceding work to finish. Mapping the chain reveals which operations block a user goal and which can run later or in parallel. section 4.1
Trace the user action from initiation to completion, then classify each operation:
- Mark operations that directly prevent the user from completing the goal as part of the critical path. section 4.1
- Follow indirect dependencies, such as a database query feeding a service call that produces the response. section 4.1
- Identify sequential operations without true dependencies and parallelize them; defer nonessential work that blocks rendering. section 4.1
- Use timeline and tracing tools to expose the chain, including Browser DevTools, Android Profiler, Instruments, or Jaeger. section 4.1
Sequential page loading
A page fetches user data, then preferences, then content even though none depends on the others. Each request adds latency; parallel execution shortens the dependency chain. section 4.1
