OOmnistu

Blog / Performance

Performance

Time to First Byte (TTFB): how to measure a slow server response and what can reduce it

Understand what TTFB measures, how field and lab results differ and which network, hosting or application work may reduce delays.

OOmnistu
Reviewed 2026-11-16 · 5 min read

TTFB is the time from starting to load a page until the first byte of the response arrives. Everything the visitor sees comes after it. This article summarises two web.dev pages, as read on 15 November 2026 (both pages carry late-2025 update dates). It is for people who commission or review a site: what to ask for, and how to tell a real problem from a measurement artefact. Our LCP and CLS workflow covers where TTFB sits among the other loading steps.

What TTFB includes

web.dev says TTFB is the sum of redirect time, service worker startup (if there is one), DNS lookup, connection and TLS negotiation, and the request up to the arrival of the first byte. So a slow server is one cause among several. Slow redirects or a distant server can look the same from the outside.

What counts as good, and why not to chase it blindly

How to measure it

What the page lists as ways to reduce it

Omnistu advice for a site project (not from the source)

Limits

Two web.dev pages, read in full on 15 November 2026. We did not read the pages they link to (the HSTS, Early Hints, Cache-Control, service worker and Server-Timing references), and we tested nothing. We make no claim about how much any change reduces TTFB for a particular site; the pages do not either. Browser and tool behaviour, such as what TTFB reports, has changed before and may again.

By Omnistu.

Sources

Previous
Back/forward cache (bfcache): why the Back button can be instant, and what blocks it