Resource waterfall
Inspect browser-recorded resource phases and overlap locally, from this page or a redacted capture of your own application.
Inspect recorded resource timings
Capture the browser’s existing timing entries for this page, or analyse a capture from your own application. No test requests are sent, no page is reloaded and no performance buffer is cleared.
Analyse my own application
On a page you own or are authorised to inspect, open the browser developer console and evaluate this read-only expression. Copy the resulting JSON text without its surrounding console quotes, then paste it below. This expression excludes resource URLs, origins and headers at collection.
Pasted text is parsed as data, never executed. Imported observations are unverified. Limit: 128 KiB and 50 resources plus the document entry. Use a foreground page and record consistent conditions.
What these timings do not establish
A zero transfer size alone does not prove a cache hit. Zeroed timing fields can reflect restricted visibility or an unobserved phase; they do not prove zero network delay. Connection reuse, service workers, caches, browser scheduling and reduced precision affect interpretation.
Bars can overlap without revealing dependencies. Request-to-first-byte includes network and service work; it is not server CPU time. This tool cannot inspect another tab, fetch an arbitrary URL or determine where a physical-network fault occurred.