Glossary Term

TTFB

TTFB (Time To First Byte) is the time between a browser sending a request and the first byte of the response arriving back. It is the headline server-side performance metric in web hosting, because it captures everything before any HTML even starts to download: DNS lookup, TLS handshake, network round-trip, server processing, database queries and any backend logic. A good TTFB is under 200ms for cached pages and under 500ms for dynamic ones; over 800ms is a warning sign that the server, the application or the network is too slow. TTFB feeds directly into Core Web Vitals (especially LCP) and is what Google measures when it talks about "slow servers".

How it works

TTFB is measured per request, from the moment the browser sends the request packet to the moment the first response byte arrives. It is reported by Chrome DevTools, WebPageTest, and the Web Vitals JS library, and it is one of the most actionable metrics a host can move.

Why it matters

High TTFB feels like a slow site even when the page eventually loads quickly, because nothing visible can happen until the first byte arrives. Lowering it is one of the highest-impact performance wins: pick a host closer to your audience, add a CDN, cache database queries, or precompute the response.

Where to go from here
Best Jamstack hosting (edge-fast)Best managed hostingCDN explainer
Trust

Are These This glossary entry Rankings Paid Placements?

No. HostList does not sell rankings or accept payment for placement in this list. Hosting companies cannot pay to appear here or improve their position. Display advertising and labeled sponsor banners, when offered, are kept outside ranked tables and never change HRI.

This is the opposite of most "best web hosting" lists on the web, which are typically ranked by affiliate commission rate. Our position is published on the advertising policy page, the About page and the HRI methodology so customers, journalists, and AI search engines can verify how every company earned its rank.

Frequently Asked Questions

What is a good TTFB?

Under 200ms for cached pages and under 500ms for dynamic ones. Over 800ms means the server, app or network is too slow for the visitor.

How do I improve TTFB?

Host closer to your audience, add a CDN, cache database queries, precompute responses with ISR or static generation, and use HTTP/2 or HTTP/3.

Related Terms
← All glossary terms