TTFB in One Paragraph

Time to First Byte is the milliseconds between a browser’s request and the server’s first response byte. Before any HTML, CSS, or images can load, TTFB must complete — it’s the gate every visitor passes through.

Unlike total load time (which depends on your page design), TTFB is almost entirely your hosting’s responsibility. That’s why it’s our primary benchmark in every review.

What’s a Good TTFB in 2026?

Under 200ms: excellent — premium/cloud hosting territory. 200–500ms: good, typical of quality shared hosting. 500–800ms: acceptable but leaves speed on the table. Over 800ms: visitors feel the lag; Google’s PageSpeed Insights flags it.

Geography matters: measure from your audience’s region. A 400ms TTFB from Singapore to a Jakarta server may be a 40ms experience for actual local visitors.

Advertisement

The 4 Components of TTFB

TTFB = DNS lookup + connection/TLS handshake + server processing + first-byte transfer. For HTTPS sites, the TLS handshake alone adds 2–3 round trips.

This is why server location matters so much: at light speed, every 1,000km adds ~10–20ms per round trip, and a typical request needs 3–5 round trips before the first byte.

💡 In short: TTFB is the purest measure of hosting quality. If yours exceeds 500ms from your audience’s location after enabling caching, the host — not your website — is the problem.

7 Ways to Reduce TTFB (Ranked by Impact)

1. Server caching. Skip PHP/database on repeat visits — the single biggest lever (40–70% improvement). Enable your host’s server cache or LiteSpeed Cache.

2. Better hosting hardware. NVMe SSDs serve data 3–6× faster than SATA. Cloud VPS typically beats crowded shared servers.

3. Data center closer to users. Jakarta server for Indonesian audiences; add a CDN for global reach.

4. PHP 8.2+. Each major PHP version renders WordPress 10–20% faster.

5. Database optimization. Clean revisions and transients; slow queries delay every response.

6. Faster DNS. Premium DNS (Cloudflare’s free tier included) resolves quicker than registrar-default DNS.

7. Reduce redirects. Every redirect is a full extra request cycle before content starts.

🏆 The Bottom Line

TTFB is the purest measure of hosting quality. If yours exceeds 500ms from your audience’s location after enabling caching, the host — not your website — is the problem.

Advertisement

Frequently Asked Questions

Does TTFB affect SEO?

Yes — it’s a core component of Core Web Vitals’ server-response metric. Google rewards fast-responding pages, and users reward them even more directly with lower bounce rates.

How do I measure TTFB correctly?

Use WebPageTest or GTmetrix with a test location matching your audience. PageSpeed Insights’ TTFB is measured from Google’s US infrastructure — misleading for local sites.

Is low TTFB possible on shared hosting?

Absolutely. Hostinger and SiteGround regularly deliver sub-300ms TTFB on shared plans thanks to LiteSpeed/NGINX and solid caching. It’s the cheap, overcrowded hosts that can’t.

NH
NgeHost Editorial Team

We buy hosting plans with our own money, run benchmarks from multiple continents, and publish the results. No sponsored placements, ever — read our editorial policy.