TTFB (Time to First Byte) is the time that elapses from when the browser sends an HTTP request to when it receives the first byte of the server's response. In short, it measures how quickly your server "reacts" — and a high TTFB is often the root cause of slow pages, even when the design looks optimized.
What TTFB Actually Measures
TTFB is not just server processing time. It covers three phases:
- DNS lookup: the time to resolve the domain name to an IP address.
- TCP + TLS connection: the time to establish the connection and negotiate encryption (HTTPS handshake).
- Server processing time: the time the server takes to generate and begin sending its response.
When tools like PageSpeed Insights or Chrome DevTools report TTFB, they show the sum of all three. In practice, for users who have already resolved DNS and have an open connection (returning visitors), the dominant component is server processing time.
Reference Values: How Much Is Too Much?
Google classifies TTFB within its Core Web Vitals framework as follows:
| TTFB | Rating |
|---|---|
| Under 800 ms | Good |
| 800 ms – 1,800 ms | Needs improvement |
| Over 1,800 ms | Poor |
For e-commerce sites or highly competitive SEO niches, targeting a TTFB below 200–300 ms is a reasonable goal with the right hosting. A TTFB above 1 second almost always signals an infrastructure, configuration, or code problem worth investigating.
Why TTFB Affects SEO and User Experience
Google uses TTFB as a field signal in the Core Web Vitals report in Search Console. A high TTFB can:
- Delay the moment the browser can start parsing HTML, pushing back all downstream metrics (FCP, LCP, TBT).
- Increase bounce rates: Google studies show that more than half of mobile users abandon a page if it takes more than 3 seconds to load.
- Hurt search rankings when competitors have better load times.
On PHP-based sites without page cache (like uncached WordPress), every visit triggers a database query and rebuilds HTML from scratch, raising TTFB significantly.
How to Measure Your Site's TTFB
Several free tools can measure it without any paid subscription:
- Chrome DevTools: open developer tools (F12), go to the Network tab, reload the page, and click the main HTML resource. In the detail panel you'll see the Waiting (TTFB) row.
- PageSpeed Insights: shows TTFB under the diagnostics section as "Reduce server response times".
- WebPageTest: lets you measure from multiple geographic locations and break down each connection phase.
- GTmetrix: includes TTFB in its waterfall load report.
Always measure from at least two locations: one close to your server (pure processing time) and one far away (showing the impact of network latency).
How to Reduce TTFB: Causes and Fixes
The most common causes of high TTFB and how to address them:
Slow or Overloaded Hosting
Low-cost shared hosting groups hundreds of sites on the same server; when resources run thin, response time spikes. Migrating to a managed VPS or a hosting plan with resource isolation is the most effective and lasting fix. If you need guidance, the team at elenlace.com can help you choose the right plan for your traffic volume.
No Page Cache
Enabling a page cache (WP Super Cache or W3 Total Cache on WordPress; native cache in other CMSes; Varnish or PHP OPcache at the server level) eliminates the need to rebuild HTML on every request. This can drop TTFB from 800 ms to under 50 ms on a mostly static site.
Slow Database Queries
A single poorly indexed query can add hundreds of milliseconds to TTFB. Use MySQL/MariaDB's slow query log to find them, then add indexes or rewrite the query.
Server Geographically Far from Your Audience
If your audience is in Mexico but your server is in Europe, network latency adds an unavoidable 100–200 ms. Use a CDN with edge caching (Cloudflare, for example) or choose hosting in your audience's region.
Misconfigured HTTPS
The TLS handshake can add latency. Enabling TLS 1.3 and OCSP Stapling reduces the number of round-trips needed to establish the secure connection.
For more optimization techniques, explore our full web performance resource library.
Key Takeaways
- TTFB measures the time from an HTTP request to the first byte of response, covering DNS, TCP/TLS, and server processing time.
- Google considers TTFB under 800 ms good; under 300 ms is the target for competitive sites.
- A high TTFB delays all downstream load metrics (FCP, LCP) and can hurt SEO rankings.
- The most common causes are overloaded hosting, missing page cache, slow database queries, and a server that's geographically far from the audience.
- The highest-impact fix is usually combining good hosting with an active page cache.
Is your site showing a high TTFB and you're not sure where to start? Talk to us at elenlace.com — we'll run a performance audit and tell you exactly what to fix.
FAQ
Is TTFB the same as page load time?
No. TTFB measures only the time until the first byte of the server response. Total page load time also includes downloading all resources (images, CSS, JS), browser rendering, and script execution. A high TTFB drags down total load time, but optimizing TTFB alone doesn't guarantee a fast page if other bottlenecks remain.
Is a 200 ms TTFB good?
Yes. A 200 ms TTFB is considered excellent and is rarely the limiting factor for perceived user performance. If you're measuring from a location geographically close to the server, it's a sign that your infrastructure and code are well configured.
Does TTFB directly affect Google rankings?
Google has not confirmed TTFB as a standalone ranking signal. However, it directly influences LCP (Largest Contentful Paint), which is part of Core Web Vitals and does impact rankings. A high TTFB makes it nearly impossible to achieve a good LCP score.
Does Cloudflare improve TTFB?
Cloudflare can reduce TTFB for users far from your origin server by serving cached content from its edge nodes close to the user. However, for dynamic content that can't be edge-cached, TTFB still depends on the speed of your origin server.
Compare providers
Other providers and guides worth comparing:
