Quiet periods
A gap is measured after all earlier requests have completed, not merely between request starts.
Morrow / Context → Evidence → Pattern → Interpretation
Follow requests, console messages and their timing in one local workspace. Keep the sequence in view while you inspect the details.
Import either file or both. Nothing leaves this browser. Network captures may contain private customer information.
No HAR selected.
No console log selected.
Ready. Nothing is sent to a server.
Local evidence workspace
Network requests and their captured timings. Choose an event to inspect it alongside the list.
A console line with only HH:mm:ss needs an associated date. You can set it above; when a HAR is loaded, its first capture date will be suggested, not asserted. Date/time without a timezone is treated as provisional UTC and can be corrected using the offset.
Select a row to inspect it alongside the list.
| Time | Request / message | Duration | Shared timeline | Inspect |
|---|
The shared clock shows recorded sequence, not causation. Console dates or timezones may be provisional; undated lines stay unaligned. Use Clock alignment to correct an offset.
A gap is measured after all earlier requests have completed, not merely between request starts.
Rate is bytes transferred divided by HAR receive time. It is not an internet speed test; missing sizes produce an unknown result.
Highlight requests with ≥ 1 second reported blocked time; check browser queueing and connection pool activity before attributing the delay to a backend.
Interpretation boundary: An empty interval may be ordinary application idleness, offline work, logging filters or a stalled capture. HAR and console files alone cannot establish that a live service froze. Compare these timestamps with application logs and user actions.
Groups use normalized messages and may combine different contexts. Select occurrences before drawing conclusions.
Exact correlation ID matches are stronger evidence than time proximity. Neither alone proves causation.
Generate a self-contained HTML timeline with your pinned findings, error/blocked highlights, correlations and explanatory notes. No raw request/response body or full console dump is included. Review before sharing; sanitized summaries can still contain sensitive information.
Confirmed: request timestamps, captured HTTP methods/statuses, available console messages, correlation identifiers, headers, response bodies and reported timings. Hypotheses: potential freeze periods, rate limitations, retries or dependency waits. Unknown: application thread state, requests omitted from the capture, end-user actions and actual network capacity.
Exported recovery is a new, local HAR containing only independently parsed entries. Repairs are recorded in the interface; missing or damaged entries are never fabricated. Always keep the original capture separately.