Start with the slow requests
Open a HAR file exported from browser developer tools to review recorded requests without contacting their servers. Filter the request list, inspect timings and response text, then pass a supported request to the cURL converter. All analysis stays in a local Worker.
Use cases
- Locate failed requests and slow API calls in a captured session
- Review request parameters, headers, and response text
- Prepare a redacted troubleshooting log and convert a request to application code
Reading timing phases
Sort by duration, then inspect DNS, connection, TLS, send, wait, and receive. TLS is a subset of connection time and must not be added twice. A value of -1 means unavailable, not zero. A HAR only contains captured browser data: status 0 alone cannot identify CORS, offline conditions, or browser blocking.
Frequently asked questions
How do I get a HAR file?
Open the browser developer tools Network panel, reproduce the issue, then export a sanitized HAR file. The analyzer reads an existing recording; it does not capture other tabs.
Will the analyzer send the recorded requests?
No. Requests, images, scripts, and response HTML are treated as data. Converting to cURL only generates text and does not execute it.
Is a redacted HAR always safe to share?
No. Common authorization headers, cookies, and sensitive fields can be removed, but secrets can appear in arbitrary URLs, headers, or response bodies. Inspect the resulting file and share only the minimum required data.
Does it replace live browser diagnostics?
No. A HAR reflects what was recorded. Missing timings or response bodies cannot be reconstructed, and request failures do not by themselves prove a CORS or server configuration issue.