TTFB (Time to First Byte)

Time to First Byte (TTFB) measures the delay between a browser requesting a webpage and receiving the very first byte of data from the server. It’s the server’s “reaction time”—and if it’s slow, everything else on your page will be slow too.

Think of it like ordering at a restaurant: TTFB is the time between placing your order and the waiter acknowledging it. If that first response takes forever, you’re going to have a bad experience—even if the food is excellent.

What is a Good TTFB?

Rating	TTFB	What It Means
✅ Good	< 200ms	Server responds instantly. Users won’t notice any delay.
⚠️ Needs Improvement	200–600ms	Noticeable pause. Likely losing impatient visitors.
❌ Poor	> 600ms	Serious problem. Users will bounce before content loads.

Google recommends keeping TTFB under 800ms for Core Web Vitals, but for B2B sites where every second counts, aim for under 200ms.

How to Measure TTFB

You don’t need expensive tools. Here’s how to check your TTFB right now:

1. Chrome DevTools – Press F12 → Network tab → Reload the page → Click the first document request → Look for “Waiting (TTFB)”
2. Google PageSpeed Insights – Enter your URL and look for “Initial server response time”
3. WebPageTest.org – Run a test and check the waterfall chart for the green “TTFB” bar
4. Lighthouse – Built into Chrome, shows TTFB under “Server response time”

What Causes High TTFB?

If your TTFB is over 600ms, one of these is likely the culprit:

• Slow hosting – Cheap shared hosting puts you on an overloaded server
• No server-side caching – Your server rebuilds pages from scratch every request
• Unoptimized database – Slow SQL queries block the response
• Missing CDN – Users far from your server wait longer
• Heavy backend code – Too many plugins, middleware, or API calls
• SSL/TLS handshake delays – Misconfigured certificates add latency

How to Improve TTFB

1. Upgrade Your Hosting

Move from shared hosting to a quality VPS or managed WordPress host (Kinsta, Cloudways, WP Engine). This alone can cut TTFB by 50%.

2. Enable Server-Side Caching

Use page caching so your server serves pre-built HTML instead of generating it fresh. For WordPress, try WP Super Cache or W3 Total Cache.

3. Use a CDN

A Content Delivery Network (like Cloudflare or BunnyCDN) serves cached content from servers close to your users, dramatically reducing TTFB for global audiences.

4. Optimize Your Database

Clean up post revisions, transients, and spam comments. Use a plugin like WP-Optimize. For custom sites, add database indexes to slow queries.

5. Reduce Backend Complexity

Every plugin, every API call, every database query adds time. Audit your stack and remove what you don’t need.

Is TTFB a Core Web Vital?

No, TTFB is not one of the three official Core Web Vitals (LCP, INP, CLS). However, it directly affects LCP (Largest Contentful Paint)—if your server is slow to respond, your main content can’t even begin loading.

Think of TTFB as the foundation. You can’t have a fast LCP with a slow TTFB.

TTFB vs. Other Metrics

Metric	What It Measures	Affected by TTFB?
TTFB	Server response time	—
FCP	First paint visible	✅ Yes
LCP	Main content visible	✅ Yes
CLS	Layout stability	❌ No

FAQ

What is TTFB in simple terms? TTFB is how fast your server starts responding when someone visits your website. Lower is better.

Why is my TTFB so high? The most common causes are cheap shared hosting, no caching, and slow database queries. Check your hosting provider first.

Does TTFB affect SEO? Indirectly, yes. High TTFB slows down LCP, which is a Core Web Vital and a Google ranking factor.

What’s a normal TTFB for WordPress? On quality managed hosting with caching enabled, WordPress sites typically see 100-300ms TTFB. On cheap shared hosting, it can exceed 1-2 seconds.