Diagnosing Slow Endpoints & HTTP Failures Offline
When a QA engineer or customer sends a browser-exported .har trace containing 200+ asset requests, finding the one failing 422 Unprocessable Entity or sluggish API timeout inside raw JSON can feel like hunting in the dark—yet uploading production HAR traces to external web viewers exposes active cookies and OAuth credentials.
This browser-only analyzer parses log.entries[] in local memory, summarizes total requests, unique hosts, and 4xx / 5xx error counts, and lets you switch instantly between capture order and Slowest First with proportional latency bars. Built-in token redaction stays enabled by default so every copied curl command or exported .har stays safe to paste into bug tickets.
QA Triage Workflow & Terminal Equivalent
- Drop a Chrome, Edge, Firefox, or Charles Proxy
.harcapture above, or click Try sample .har (with mock secrets). - Filter by 4xx / 5xx to find rejected calls, or click Slowest First to check backend bottlenecks.
- Review the Redaction Audit tab and click Download Sanitized .har to attach a scrubbed trace to your ticket.
# List non-2xx requests sorted by latency locally with jq
jq -r '.log.entries | sort_by(-.time)[] | select(.response.status >= 400) | "\(.response.status)\t\(.time | round)ms\t\(.request.method)\t\(.request.url)"' capture.harWhat It Does & Does Not Read
- No network replay: Loading a HAR file here strictly parses its JSON structure and never fires any HTTP requests to captured endpoints.
- Large media captures: DevTools exports with multi-megabyte inline images take extra tab memory when formatted as raw JSON; use the table tabs cleanly without triggering full JSON rendering until needed.
Frequently Asked Questions
Does this HAR file analyzer inspect timing and errors locally?
Yes. Your .har capture stays inside browser RAM. Latency bars, HTTP status filtering (2xx/3xx/4xx/5xx), and unique host metrics compute strictly on the client side.
Does this viewer hide secrets if I decide to download the HAR or copy cURL afterward?
Yes—automatic redaction of Authorization headers, Cookies, query secrets, JWTs, and emails is enabled by default whenever you copy cURL or download a cleaned .har attachment.
How do I spot the slowest or failing API requests quickly?
Click the "4xx / 5xx" status filter pill to isolate errors, or switch sorting from Capture Order to "Slowest First" to surface high-latency endpoints immediately.