TTFB (Time to First Byte) is the time it takes for a browser to receive the first byte of data from a server after sending a request. It is one of the most important technical metrics for SEO and user experience, yet it is often overlooked. A slow TTFB delays everything else — HTML parsing, CSS loading, JavaScript execution, and rendering. In this guide, you will learn what TTFB is, why it matters, how to test it with a free TTFB checker, and what to do if your server response time is too slow.
What is TTFB and why does it matter
TTFB measures three phases of a request:
1. DNS lookup. The browser resolves the domain name to an IP address.
2. Connection and TLS handshake. The browser connects to the server and establishes a secure connection.
3. Server processing. The server receives the request, processes it, and sends back the first byte of the response.
TTFB is the sum of these three phases. If any of them is slow, the whole page load is delayed.
Google uses TTFB as part of its page experience signals. While TTFB is not a direct ranking factor, it influences Core Web Vitals — specifically LCP (Largest Contentful Paint). A slow TTFB makes it almost impossible to achieve a good LCP score. In 2026, Google continues to prioritize fast, responsive pages, and TTFB is one of the first things to check.
What is a good TTFB score
There is no universal threshold, but Google recommends the following benchmarks:
Good: under 200 ms
Needs improvement: 200-500 ms
Poor: over 500 ms
For dynamic websites (e-commerce, SaaS, blogs with heavy databases), TTFB under 500 ms is acceptable. For static sites and CDN-backed pages, TTFB should be under 200 ms.
In 2026, with growing competition in search results, even a 100 ms improvement in TTFB can lead to a measurable increase in conversions. Studies show that a 100 ms delay can reduce conversions by up to 7%.
How to test TTFB with a free TTFB checker
The fastest way to check TTFB is to use an online TTFB checker. The SerpMax TTFB checker tests any URL and returns the server response time in milliseconds.
Step 1. Open the TTFB checker.
Step 2. Enter the URL of the page you want to test.
Step 3. Click Check. The tool sends a request to the server and measures the time until the first byte arrives.
Step 4. Review the result. The tool shows TTFB in milliseconds and compares it to recommended benchmarks.
For accurate results, test the same page multiple times. TTFB can vary depending on network conditions, server load, and CDN caching. Test from different locations if possible — SerpMax tools support testing from multiple regions.
Common causes of slow TTFB
If your TTFB is over 500 ms, the cause is usually one of the following:
1. Slow server hardware or hosting
Shared hosting with overloaded servers is the most common cause. If your hosting provider oversells resources, your server response time will fluctuate. Check the hosting server signature via server signature checker and consider upgrading to a VPS or dedicated server.
2. No caching
Without caching, the server has to generate the page from scratch on every request. Enable server-side caching (Redis, Memcached, Varnish) and browser caching. Check your Cache-Control headers via HTTP headers lookup.
3. Slow database queries
For CMS-based sites (WordPress, 1C-Bitrix, Joomla), slow database queries are a frequent bottleneck. Optimize queries, add indexes, and reduce the number of database calls per page.
4. No CDN
If your server is in one region but your users are in another, TTFB will be slow for distant users. A CDN reduces TTFB by serving content from the nearest edge server.
5. Heavy server-side code
Slow PHP, Python, or Node.js code delays the response. Profile your code and optimize the slowest parts. For WordPress, check plugins — some add significant overhead.
6. No compression
If the server does not compress responses (gzip or Brotli), more data has to travel over the network. Check compression via server compression checker.
7. DNS issues
Slow DNS resolution delays the connection. Check DNS records via DNS lookup and consider using a fast DNS provider.
How to fix slow TTFB
Once you have identified the cause, use the following checklist to improve TTFB:
1. Upgrade hosting. Move from shared hosting to VPS or dedicated server. Choose a provider with fast SSD storage and sufficient RAM.
2. Enable caching. Set up server-side caching and browser caching. Set Cache-Control headers with long max-age for static assets.
3. Use a CDN. Connect a CDN to serve static and dynamic content from edge servers. This reduces TTFB for users worldwide.
4. Optimize database. Add indexes, optimize queries, reduce the number of database calls. For WordPress, use object caching (Redis).
5. Enable compression. Turn on gzip or Brotli compression on the server. This reduces response size and speeds up transfer.
6. Optimize server-side code. Profile slow scripts, reduce external API calls, and cache expensive computations.
7. Use HTTP/2 or HTTP/3. These protocols reduce latency and improve multiplexing. Check via HTTP/2 checker.
8. Check page size. Large pages take longer to transfer. Check page size via page size checker and reduce unnecessary HTML, CSS, and JavaScript.
After each change, re-test TTFB with the TTFB checker to measure the impact.
TTFB and Core Web Vitals
TTFB is not a Core Web Vital itself, but it directly affects LCP (Largest Contentful Paint). LCP measures how long it takes for the largest visible element on the page to render. If TTFB is 800 ms, LCP cannot be under 800 ms — the browser is still waiting for the first byte.
Google recommends LCP under 2.5 seconds. To achieve this, TTFB should be under 500 ms, ideally under 200 ms. Improving TTFB is one of the fastest ways to improve LCP and overall page experience.
For a full technical audit — TTFB, LCP, page size, DOM size, compression, HTTP/2 — use SEO Audit by SerpMax.
How often to check TTFB
TTFB can change over time: server load grows, database slows down, CDN cache expires. Recommended frequency:
— After any hosting change, server migration, or CDN setup.
— After major CMS or plugin updates.
— Monthly as part of routine technical SEO monitoring.
— Immediately if you notice slower page loads or increased bounce rate.
Frequently Asked Questions
What is a good TTFB score?
Under 200 ms is excellent. 200-500 ms is acceptable but can be improved. Over 500 ms is poor and should be fixed. For dynamic sites, aim for under 500 ms; for static sites, under 200 ms.
Is TTFB a ranking factor?
TTFB is not a direct ranking factor, but it affects Core Web Vitals — specifically LCP. Google uses page experience signals, and slow TTFB makes it impossible to achieve good LCP. Indirectly, TTFB affects rankings through user experience and bounce rate.
How do I test TTFB?
Use a free online TTFB checker like the SerpMax TTFB checker. Enter the URL, click Check, and review the response time. Test multiple times for accuracy.
Why is my TTFB so high?
Common causes: slow hosting, no caching, slow database queries, no CDN, heavy server-side code, no compression, DNS issues. Check each one with the tools listed in this guide.
Can I improve TTFB without changing hosting?
Yes. Enable caching, use a CDN, enable compression, optimize database queries, and reduce server-side code execution. These changes can reduce TTFB significantly without migrating to a new host.
What is the difference between TTFB and LCP?
TTFB measures the time until the first byte of the response arrives. LCP measures the time until the largest visible element on the page is rendered. TTFB is a component of LCP — a slow TTFB delays LCP.
Does TTFB affect mobile users more?
Mobile networks are slower and less stable than desktop connections. A slow TTFB has a bigger impact on mobile users because they wait longer for the response. Optimizing TTFB improves mobile experience significantly.
How often should I check TTFB?
Monthly as part of technical SEO monitoring, plus after any hosting change, CMS update, or CDN setup. If you notice slower page loads, check immediately.
Can TTFB be too low?
No. Lower TTFB is always better. If TTFB is under 100 ms, that is excellent. The only caveat: if TTFB is suspiciously low, check that you are not measuring a cached response instead of the real server response time.
