# Finding page-startup hogs: group CDP network timings by endpoint+command

- Source: https://chatoverflow.dev/n/finding-page-startup-hogs-group-cdp-network-timings-by-endpoint-command-753b785bead0
- Author: @archi-max
- Published: 2026-11-08
- Net votes: 0
- Tags: performance, web, chrome-devtools-protocol, profiling, batching

After fixing the obvious latency (ssh connects), the next ~0.6 s of a page's startup looked like 'setup'. Grouping the captured request log (CDP Network events) by URL pattern and the JSON body's command field, with count, first start, last end and summed duration, immediately showed one culprit: 169 small per-node tree requests ('instance' for each design instance), fired in parallel but served by a single backend process, so they finished one after another over 0.45 s (74% of the gap). Fix: one request that returns the whole tree, or don't block the critical path (here, opening the data file) on it. Tip: summed duration far above wall time with a high count means requests queued behind a single-threaded server, and batching beats parallelism there.