TTFB, or Time to First Byte, is the time between a visitor’s browser requesting a page and receiving the very first byte of the response from your server. It measures how quickly your server starts responding, so it reflects server speed, caching, and network distance rather than how long the whole page takes to load. A low TTFB means a responsive server and is an important early contributor to overall page speed; a high TTFB signals a slow server, missing caching, or distance that drags down every page load.
This guide explains what TTFB is, what affects it, what counts as good, and how to improve it, so you understand this key server-speed metric and how to keep it low.
Did you know?
TTFB is the first thing that has to happen on every page load, so a high TTFB delays everything that follows. Cutting it is one of the most direct ways to make a whole site feel faster.
What TTFB measures
Time to First Byte measures the delay between the browser sending a request and receiving the first byte of the server’s response. It captures three things happening in sequence: the request travelling to the server, the server processing it and building the response, and the first byte travelling back.
Importantly, TTFB is about how quickly the server starts responding, not how long the full page takes to finish loading. It is the opening step of every page load, so a slow TTFB delays everything that comes after — which is why it is a closely watched server-performance metric.
What affects TTFB
Several factors determine your TTFB, and they map neatly onto the things that make hosting fast:
- Server speed and resources: a faster, better-resourced server responds sooner.
- Caching: a cached page is served instantly, slashing TTFB.
- Network distance: a far-away visitor waits longer for the round trip.
- Dynamic processing: heavy uncached page-building raises TTFB.
- Database and code efficiency: slow queries or bloated code delay the response.
Pro Tip
If your TTFB is high, caching is usually the first and biggest fix. A cached page skips the slow page-building step entirely, so the server sends the first byte almost immediately.
What counts as a good TTFB
As a rough guide, a TTFB under about 200 milliseconds is good, 200-500ms is acceptable, and consistently above 500ms-600ms is slow and worth improving. These are general benchmarks — the exact target varies — but the principle holds: lower is better, and a fast server on a cached page should respond very quickly.
Because TTFB is the first step of loading, keeping it low benefits every page. Tools like PageSpeed Insights, WebPageTest, or your browser’s developer tools report TTFB, so you can measure yours and see whether it is in the good range or dragging down your load times.
How to improve TTFB
The most effective fix is caching: a cached page is served ready-made, so the server skips the slow work of building it and sends the first byte almost immediately. Enabling server-level caching (or a caching plugin) usually produces the biggest TTFB improvement.
Beyond caching, faster hosting (good resources, fast NVMe storage, a current PHP version) speeds up the processing step, a CDN reduces network distance for far-away visitors, and optimising your database and code makes dynamic page-building quicker. Together these attack every component of TTFB.
TTFB and overall page speed
TTFB is important but it is only the start of the story. It measures how fast the server begins responding; the rest of page speed depends on how quickly the browser then downloads and renders everything — images, CSS, JavaScript. So a low TTFB is necessary for a fast site but not sufficient on its own.
Think of TTFB as the server’s reaction time and the rest of page speed as the delivery and rendering that follow. You want both: a quick TTFB from good hosting and caching, and a lean, optimised front end so the page finishes loading fast after that first byte arrives.
Why TTFB reflects your hosting
Because TTFB is largely determined by server speed, caching, and infrastructure, it is a good proxy for hosting quality. A host with fast servers, NVMe storage, server-level caching, and a nearby data centre tends to deliver a low TTFB, while a slow or overloaded host shows a high one.
So if your TTFB is stubbornly high even with caching enabled and a lean site, your hosting may be the limitation. Choosing quality hosting with fast infrastructure and built-in caching is one of the most direct ways to keep TTFB low — and, because TTFB comes first on every load, to make your whole site feel faster.
Want a genuinely fast website?
Hostinger’s plans include NVMe storage, LiteSpeed servers, built-in caching, and a free CDN — the speed stack this guide describes, ready to go. From a few dollars a month; use code PROTIPS for the reader discount.
FAQs
What is TTFB (Time to First Byte)?
TTFB is the time between a browser requesting a page and receiving the first byte of the server’s response. It measures how quickly your server starts responding — reflecting server speed, caching, and network distance — rather than how long the whole page takes to finish loading.
What is a good TTFB?
As a rough guide, under about 200 milliseconds is good, 200-500ms is acceptable, and consistently above 500-600ms is slow and worth improving. Lower is better, and a fast server serving a cached page should respond very quickly. Tools like PageSpeed Insights report your TTFB.
What affects TTFB?
Server speed and resources, caching, network distance to the visitor, how much dynamic processing the page needs, and database and code efficiency. These map onto what makes hosting fast, so TTFB is a good proxy for server and hosting quality.
How do I improve TTFB?
Caching is usually the biggest fix — a cached page is served ready-made, so the server sends the first byte almost immediately. Also use faster hosting with good resources and NVMe storage, a CDN to reduce distance, a current PHP version, and an optimised database and code.
Does TTFB affect overall page speed?
Yes, because it is the first step of every page load, so a high TTFB delays everything after it. But it is not the whole story — the rest of page speed depends on how fast the browser downloads and renders images, CSS, and JavaScript. You want a low TTFB and a lean front end.
Does TTFB reflect hosting quality?
Largely, yes. TTFB is mostly determined by server speed, caching, and infrastructure, so a host with fast servers, NVMe storage, server-level caching, and nearby data centres delivers a low TTFB. A stubbornly high TTFB despite caching and a lean site often points to slow hosting.
The bottom line
TTFB (Time to First Byte) is how quickly your server starts responding — the delay between a request and the first byte of the reply. It reflects server speed, caching, and network distance, and because it is the opening step of every page load, a high TTFB drags down everything that follows. Under about 200ms is good; consistently above 500-600ms is worth fixing.
The biggest lever is caching, which lets the server send a ready-made page almost instantly; faster hosting, a CDN, current PHP, and an efficient database and code address the rest. Since TTFB is largely set by your infrastructure, quality hosting with fast servers and built-in caching keeps it low — and a low TTFB makes your whole site feel faster.
When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. TTFB is your server’s reaction time — keep it low with caching, fast hosting, and a CDN.