Inspect

Inspect tells you where measured HTTP transfer time goes. Run it against an HTTP or HTTPS URL, save the recording and ask it to explain the observed events. Collect a second recording after a change and compare the two. The command is bitspeed-inspect; version 0.1.1 is released.

The useful distinction is between what the client saw and what it can infer. DNS events, connection attempts and response bytes are observations. An interval or median is calculated from those observations. Interpretations cite their evidence and rules. Missing or ambiguous events stay unavailable rather than quietly becoming zero.

First-byte waiting includes more than origin processing. Reading a response includes handling and scheduling as well as moving body bytes. Observed payload bytes are not total network traffic. Inspect does not identify a slow database, a saturated router or a busy CPU from one client trace.

Comparisons keep phase statistics when useful, flag changed targets, payloads, protocols and request settings, and withhold change verdicts for incomplete coverage, too few observations or overlapping ranges. They describe collected samples rather than establishing statistical confidence or a general performance improvement.

Start with the quick start, get a binary from Download or consult the reference. Requests use fresh direct connections, ignore proxy environment variables and verify TLS normally. Inspect makes real GET requests, including redirects, so choose targets you intend to access.