What Is TTFB?
Time to First Byte (TTFB) is the time it takes for a browser to receive the first byte of data from your server after making a request. It is measured in milliseconds and is one of the most important signals in Google’s Core Web Vitals framework.
A good TTFB is under 200ms. An acceptable TTFB is under 500ms. Anything above 600ms is actively hurting your PageSpeed score and your search rankings.
Why TTFB Matters
TTFB is not just a speed metric — it is a diagnostic. A high TTFB tells you the problem is at the server level, not the browser level. No amount of image optimization or minification will fix a slow TTFB. You have to address the root cause: server response time.
Google’s documentation explicitly states that TTFB affects Largest Contentful Paint (LCP), the Core Web Vital that carries the most ranking weight in 2026.
8 Fixes That Actually Work
1. Upgrade Your Hosting
This is the single most impactful fix. Shared hosting TTFB averages 400 to 800ms. Cloud hosting with dedicated resources averages 80 to 150ms. Kinsta consistently produces the lowest TTFB numbers we have tested — their C2 machines with Google Cloud infrastructure regularly hit under 100ms TTFB from US locations.
2. Enable Server-Side Caching
Full-page caching stores a static HTML version of your pages so the server can skip PHP and database processing entirely. WP Rocket, LiteSpeed Cache, or Nginx FastCGI caching all accomplish this. Expect TTFB to drop 50 to 70 percent after enabling full-page caching.
3. Enable Redis Object Caching
Object caching stores the results of database queries in memory so they do not have to be repeated on every request. If your host supports Redis, turn it on. The improvement is immediate and dramatic on content-heavy sites.
4. Upgrade to PHP 8.2 or 8.3
PHP 8.x is significantly faster than PHP 7.x for most WordPress operations. If your site is still running PHP 7.4, upgrading is free and takes two minutes in most hosting dashboards. Expect 10 to 20 percent improvement in server response time.
5. Optimize Your Database
WordPress databases accumulate overhead from revisions, transients, and orphaned metadata over time. Use WP-Optimize or Advanced Database Cleaner to remove post revisions, clean transients, and optimize database tables. Run this monthly.
6. Use a CDN With Edge Caching
A CDN does not just serve static assets faster — when configured properly, it can cache full HTML responses at edge locations worldwide. Cloudflare’s APO (Automatic Platform Optimization) for WordPress caches entire pages at the edge, effectively making TTFB under 50ms for repeat visitors regardless of server location.
7. Reduce External HTTP Requests
Every external script call — Google Tag Manager, fonts, analytics, chat widgets — adds DNS lookup time to your effective TTFB. Self-host Google Fonts, load scripts asynchronously, and audit every third-party resource loading on your site.
8. Enable HTTP/2 or HTTP/3
HTTP/2 and HTTP/3 allow multiple requests to be served over a single connection in parallel. Most modern hosting setups support HTTP/2 already, but confirm in your server configuration. HTTP/3 (QUIC) further reduces connection overhead, especially on mobile networks.
What Good TTFB Looks Like
- Under 100ms: Excellent — this is what premium cloud hosts like Kinsta deliver
- 100 to 200ms: Good — Google’s recommended threshold
- 200 to 500ms: Acceptable — room for improvement
- 500ms+: Poor — actively hurting your Core Web Vitals and rankings
Test your TTFB at web.dev/measure or GTmetrix. If you are over 300ms, the hosting and caching fixes above will have the biggest impact. If you are already under 300ms and still scoring poorly on PageSpeed, the problem is elsewhere — images, render-blocking resources, or JavaScript execution time.
Not sure what is causing your TTFB? Request a free speed audit and we will pinpoint the exact cause and send you a fix list within 24 hours.
Is Your Site Slow? Get a Free Speed Audit
Disclosure: Some links in this article are affiliate links. We may earn a commission at no extra cost to you.
