What Is TTFB? Time to First Byte Explained for 2026
TTFB measures how long your server takes to start responding, here is what counts as good and how to test yours properly.
TTFB in one sentence
Time to first byte is the delay between a browser requesting your page and the first byte of the response arriving, it captures DNS lookup, connection setup, and crucially, how long your server thinks before it starts answering. It is not how long the page takes to load; it is how long the load takes to begin. Everything else stacks on top of it.
What counts as a good TTFB
Under 200ms is excellent, under 500ms is solid for dynamic sites, and Google's guidance treats 800ms as the threshold where TTFB starts dragging down your Core Web Vitals. Dynamic platforms like WordPress naturally sit higher than static files because the server assembles each page. If uncached pages regularly exceed a second, the delay is usually your hosting or your database, not your visitors' connections.
What actually drives TTFB up
Three ingredients dominate: server processing time, distance, and caching. A shared server juggling too many tenants responds slowly; a visitor far from your datacenter waits on every network round trip; and an uncached page forces WordPress to rebuild what it could have served from memory. Slow database queries and bloated plugins stretch the thinking time further.
Caching is the great equalizer. A cached page skips nearly all processing, which is why the same site can post a quick TTFB on its cached homepage and a far slower one on a logged-in dashboard that bypasses the cache. When you test, check both paths so you know your true range rather than your best case.
How to test your TTFB
Use several tools and several locations. Chrome DevTools shows TTFB in the network panel under timing; PageSpeed Insights reports it within the Core Web Vitals section; WebPageTest lets you test from cities that match your actual audience. Run each test a few times and look at the pattern, not a single reading, one slow sample can be network noise rather than your server.
How to improve it
Order your fixes by leverage: enable full-page caching first, since it eliminates most server thinking time. Then look at hosting quality, an overloaded platform has a high floor no plugin can lower. SiteGround pairs its Google Cloud infrastructure with a Speed Optimizer plugin that handles the caching layer, an approach built around exactly this metric. Finally, prune slow plugins and heavy database queries.
Keep TTFB in perspective
TTFB is a diagnostic, not the destination. Visitors experience full page loads, so a brilliant TTFB with 5MB of unoptimized images still feels slow. Use TTFB to isolate where a delay lives, server versus front end, and fix accordingly. If TTFB is fast and the page is slow, work on images and scripts; if TTFB itself is slow, look at caching and hosting.
Frequently asked questions
What is a good TTFB for a WordPress site?
Does TTFB affect SEO rankings?
Why is my TTFB different every time I test?
Related reading
HostingHow to Speed Up Your Website in 2026, Ordered by Impact
Hosting quality, caching, image compression, and a CDN, ranked by how much faster each one actually makes your site.
HostingLiteSpeed vs NGINX vs Apache in 2026: Plain-English Guide
The web server your host runs shapes how fast pages leave the building, here is the difference without the jargon.
HostingWebsite Uptime Explained: What 99.9% Really Allows in 2026
Those reassuring nines conceal real hours of downtime; here is how to translate them, read an SLA, and verify your host.