TTFB: diagnose the delay before the first byte

At a glance

TTFB helps locate delay before a response arrives. It measures neither complete loading, server execution alone nor task completion.

Empty intelligence archive with dossiers and maps Illustration · fictional scene
In this article

Understand what the tool times

Navigation TTFB can include redirects, DNS, connection, TLS and response waiting. Check the starting point and handling of interim responses such as Early Hints. The 0.8-second web.dev benchmark is a rough guide; TTFB is not a Core Web Vital.

SignalWhat it describesUseful check
Browser TTFBDelay to the measured first byte.Identify phases and the tool’s convention.
Server trace durationTime within the instrumented scope.Do not equate it with full network delay.
LCPDisplay of the largest visible content.Check resources and rendering after the response.
Task completionThe outcome actually achieved.Check forms, reading or payment.

Isolate a cause before changing hosting

  • Compare the same URL and region under documented device, network, cache and connection-reuse conditions. Separate field measurements from lab tests.
  • Distinguish cached responses from origin requests. Correlate network timing with server traces to identify slow queries, external dependencies or connection waiting.
  • After a fix, also measure LCP and task completion. A fast first byte can still precede a long wait for useful content.

Connect measurement with an actual improvement

Check that gains do not merely reflect earlier headers or an incomplete response. Compare distributions rather than one visit and monitor errors, freshness and cache privacy. Better TTFB guarantees neither ranking nor conversion growth.

Primary references

Locate TTFB delay before changing infrastructure

Time to First Byte captures only part of loading, not the whole experience. Connection, generation, dependency work or a cache miss can contribute; relate the diagnosis to affected pages and regions.

  • Compare dynamic pages, cached responses and static resources.
  • Trace dependency and processing time on a representative request.
  • Retest LCP and interaction after the fix to confirm user benefit.

Primary reference: Google Search Central — page experience. Related method: read the practical guide.