TTFB Analyzer
Review saved HAR, Navigation Timing, Lighthouse, PageSpeed or endpoint notes. Compare first-byte timings by measurement basis and inspect recorded cache, protocol and backend evidence.
Investigate Slow First Bytes in Captures
TTFB Analyzer: how to use it
- Open a saved diagnostic or paste its text or JSON. Try the HAR or text example to see the expected evidence.
- Select Analyze TTFB. Review the slowest entries within a measurement basis, then look for recorded cache, CDN and duration clues.
- Copy or download the filtered JSON. The report retains endpoint paths while dropping URL queries, fragments, user information and unneeded headers.
Limits and notes
Uses up to 512 KiB and 500 entries or lines. Lighthouse input requires a numeric server-response-time audit or a PageSpeed TTFB percentile. Distinguishes request wait from navigation time and field percentiles. Opens no network connections to endpoints.
How your privacy works →TTFB Analyzer: common questions
Why is HAR wait separate from Navigation TTFB?
HAR wait measures the time waiting for the recorded request's first response. Navigation TTFB runs from navigation start and can include prior work such as redirects.
Can a cache miss explain the full timing?
A miss identifies a state in the capture. Compare recorded server durations, network phases and a comparable second capture before assigning a cause.
What happens to a retry limit or missing timing?
The row stays in the report with the recorded outcome or Unavailable and appears below measured rows in the same basis.