A good Time to First Byte (TTFB) is 0.8 seconds or less, according to Google’s web.dev guidance. TTFB measures how long a browser waits to receive the first byte of a response from your server. A TTFB above 1.8 seconds is considered poor. Check yours with our free website speed test.
Key takeaways
- TTFB of 0.8 seconds or less is good, and over 1.8 seconds is poor (Google, web.dev).
- A slow TTFB delays every other metric, including Largest Contentful Paint.
- Caching, better hosting, a CDN and fewer plugins are the main fixes.
- TTFB is a diagnostic metric, not a Core Web Vital.
What is TTFB?
Time to First Byte (TTFB) is the time between a browser requesting a page and receiving the first byte of the response. It covers redirects, DNS lookup, connection setup and the time your server takes to build and send the page. TTFB shows how responsive your server and network setup is.
What is a good TTFB?
A good TTFB is 0.8 seconds or less. Google’s guidance on web.dev groups TTFB into three ranges, shown below.
| TTFB | Rating |
|---|---|
| 0.8 seconds or less | Good |
| 0.8 to 1.8 seconds | Needs improvement |
| More than 1.8 seconds | Poor |
TTFB is not a Core Web Vital, but it affects them. A slow server response pushes back when the main content can appear, which hurts your LCP in WordPress and your overall score.
How do you check your TTFB?
You check TTFB by running a speed test and looking for the server response time result.
- Enter your URL into our free page speed checker.
- Open the performance diagnostics and look for the server response time item.
- Test two or three times, because server response varies.
- Test a cached page and an uncached page to see the difference.
What causes a slow TTFB?
A slow TTFB is usually caused by slow hosting, no page caching, heavy plugins, a large or unoptimized database, or a visitor being far from your server. Redirects and slow DNS can also add delay before the server even starts working.
How do you reduce server response time in WordPress?
1. Enable page caching
Caching serves a ready-made copy of the page instead of rebuilding it for each visit. This is usually the biggest single TTFB improvement on WordPress.
2. Use a CDN
A content delivery network stores copies of your pages and files on servers around the world, so visitors connect to a location closer to them. Some CDNs can also cache full pages.
3. Upgrade your hosting
Crowded shared hosting can respond slowly at busy times. If caching and a CDN do not help enough, a plan with more resources or a better server stack is the next step.
4. Use a current PHP version
Newer supported PHP versions run WordPress faster. Check your hosting panel and update after testing for plugin compatibility.
5. Remove heavy plugins
Plugins that run many database queries or background tasks slow server response. Remove plugins you do not use and replace heavy ones with lighter options.
6. Clean up the database
Old revisions, expired transients and leftover data can slow queries. Back up first, then clean carefully with a trusted tool.
7. Reduce redirects
Every redirect adds a full request before the final page loads. Link directly to final URLs and avoid redirect chains.
Does TTFB affect SEO?
TTFB affects SEO indirectly. It is not a ranking factor on its own, but a slow server response makes it harder to pass Core Web Vitals, and those are part of Google’s page experience signals. Relevance and content quality still matter more.
Frequently asked questions
What is a good TTFB in seconds?
0.8 seconds or less is good, according to Google. Anything over 1.8 seconds is poor.
Is TTFB the same as page load time?
No. TTFB only measures how long it takes for the first byte to arrive. Page load time includes everything that happens afterward, such as downloading images, styles and scripts.
Why is my TTFB high only sometimes?
Server load, uncached pages and network conditions change over time. A page may be fast when cached and slow when the cache is cleared or expired.
Can a CDN improve TTFB?
Yes. A CDN reduces the distance between the visitor and the server that responds, and a CDN that caches full pages can cut TTFB further.
Does hosting affect TTFB?
Yes, hosting is one of the biggest factors. Slow or overloaded servers respond more slowly, no matter how well your site is optimized.
Conclusion
A good TTFB is 0.8 seconds or less, and the quickest ways to get there are caching, a CDN and better hosting. Test your server response with our free website speed test, apply one fix at a time and re-test. For more fixes, read our guide on how to improve website speed.
