HAR Analyzer

Sample report

A typical report groups requests by resource type, lists third-party hosts, and surfaces failed requests, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., and explicit cache missesCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency. for review. The values always come from the selected HAR; this sample description is not a benchmark.

How it works

The browser reads the HAR locally, validates its shape and limits, removes sensitive URL and header values, then classifies the bounded request entries. No request or response bodies are included in the displayed or exported report.

What the report can show

• Failed requests and redirect responses.
• Transfer bytes and summed request duration as HAR-recorded evidence, not a page-load score.
• First-party versus third-party hosts based on the first valid request host.
• Cache hit, miss, and revalidation evidence from recorded response status and headers.
• Tag-manager, analytics, advertising, and consent loader/request patterns.

Privacy and interpretation boundaries

HAR files are sensitive source material. Analysis is local, but the original file remains your responsibility. The sanitized export contains redacted URLs and header names only—not header values, bodies, post data, or cookies. Timings can overlap, browser HAR exporters differ, and a network request does not prove a vendor processed it.

Frequently asked questions