The Time to First Byte (TTFB) is the time between the moment a browser requests a page and the moment the server sends back the first bit of data. A high TTFB feels to visitors like a slow website, even before a single image has loaded. The cause usually lies in slow hosting, heavy scripts on the server, or a poorly configured database. In this article you’ll learn how to measure TTFB, what a good value is, and which steps really help.
What exactly is TTFB?
TTFB consists of three parts: the time to look up the DNS and establish a connection, the time the server needs to process the request, and the time it takes to send the first byte of the response to the browser. Most of the delay is usually in the middle part: how long the server takes to generate the page, for example due to database queries, PHP processing, or plugins running in the background.
A low TTFB means your server responds quickly, which not only improves the user experience but also factors into how search engines evaluate your site.
Measuring TTFB: here’s how
You don’t need complicated tools to measure TTFB. You can see this directly in any modern browser:
Open the developer tools
Press F12 in your browser and go to the ‘Network’ tab.
Reload the page
Refresh the page with the cache cleared (Ctrl+Shift+R) so you get an accurate measurement.
View the main request
Click on the first line (usually your domain name) and look at the ‘Timing’ tab. The TTFB is listed there separately.
Test at multiple times
Measure at different times and from different locations to get a realistic picture, since server load varies throughout the day.
Causes of a slow TTFB
There are a few recurring culprits that push TTFB up:
- Slow database queries: unoptimized queries or a database without proper indexes make the server wait unnecessarily long.
- Too many plugins or modules: every active plugin that executes code on every page request costs time.
- No server-side caching: without caching, the server rebuilds every page each time, even if the content hasn’t changed.
- Overloaded or outdated hardware: slow disks and insufficient processing power directly cause delays with every request.
- Large distance to the server: a server far from your visitors increases the request’s travel time.
- DNS delay: a slow-responding DNS provider adds delay even before the server is reached.
Reducing TTFB: step by step
Most improvements come from a combination of server settings and optimizing your website itself.
Activate server-side caching
With a caching solution such as LiteSpeed Cache, the server doesn’t need to rebuild pages every time, significantly reducing response time.
Optimize your database
Clean up unnecessary tables, add indexes where needed, and check for slow queries. In Plesk you’ll find tools for this such as phpMyAdmin.
Disable unnecessary plugins
Deactivate plugins or modules you don’t use, especially if they execute extra code on every page request.
Use object caching
With Redis or Memcached, repeated database requests are temporarily stored, reducing the amount of work the server needs to do.
Check your hosting
With fast NVMe storage and a well-configured web server, you’ll immediately notice a difference in response time. Check out the options at webhosting if you’re unsure whether your plan still fits your website.
Is your current hosting struggling with slow response times and are you considering switching? Via switching to Tandata, the migration is arranged for you, including a check for these kinds of bottlenecks.
Frequently asked questions
What is a good TTFB value?
The lower the better. A fast, well-configured server with caching typically responds within a few tens to a few hundred milliseconds.
Does TTFB affect my Google ranking?
Server speed is one of the factors that contributes to overall page speed, which in turn is part of how search engines evaluate your site.
Can a CDN lower TTFB?
Yes, a CDN can deliver static content closer to the visitor, but for dynamic content, the speed of your own server remains decisive.
Why does my TTFB sometimes vary?
This is often due to fluctuating server load, database congestion, or slow external connections used by the page.
Conclusion
A high TTFB can almost always be traced back to the server: slow database queries, missing caching, or too many active plugins. By enabling caching, cleaning up your database, and removing unnecessary plugins, you’ll notice a significant drop in response time. Good hosting with fast storage and a modern web server forms the foundation for this.