Speed Guide
What TTFB Means and How to Bring It Down
Time To First Byte measures how long a visitor waits before your server sends anything back, and it sets the ceiling for every other speed metric.
NVMe
SSD storage cutting server response time
24/7
Support for server-side troubleshooting
99.9%
Uptime keeping response times consistent
Free
Migration to faster infrastructure
In short
TTFB, Time To First Byte, is the time between a browser requesting a page and receiving the first byte of the server's response, covering DNS lookup, connection setup, server processing, and the start of data transfer. A slow TTFB delays everything that follows, since the browser can't begin rendering until that first byte arrives, making it a foundational metric rather than a cosmetic one.
It's easy to focus on visible things like image size or script count when chasing page speed, but TTFB happens before any of that even starts. If your server takes 1.5 seconds to respond before sending a single byte of HTML, no amount of image compression or script minification on the front end will make the page feel fast, because the visitor is stuck waiting on the server itself.
TTFB is also a component that Google's Core Web Vitals and PageSpeed Insights specifically call out, since it directly affects Largest Contentful Paint. A page that scores poorly on LCP but has fast, compressed assets often has its real bottleneck sitting in a slow TTFB that no amount of front-end tuning can fix.
What actually happens during TTFB
The TTFB window covers several steps in sequence: the browser resolves your domain's DNS, opens a TCP connection (and a TLS handshake if the site uses HTTPS), the server receives the request and processes it, whether that's a static file lookup or a full database query and template render, and finally the first byte of the response begins transferring back. Any one of these steps running slow adds directly to the total.
For a static HTML page, most of that time is connection setup and file lookup, which should be fast on decent hosting. For a dynamic CMS like WordPress, the processing step often dominates, since the server has to run PHP, query the database for the page content, and assemble the final HTML before sending anything back.
The most common causes of a slow TTFB
Shared hosting with too many accounts competing for the same CPU and disk resources is a frequent culprit, since your site's database query has to wait its turn behind everyone else's traffic. Slow storage is another major factor, spinning hard drives read and write far slower than SSDs, and that gap shows up directly in how long it takes to fetch page data from the database.
No server-side caching is another common cause specific to CMS sites: without a page cache, WordPress rebuilds the entire page from scratch, running PHP and database queries, on every single request. Physical distance between the visitor and your server also adds latency to every step of the connection process, which is why visitors far from your server's data center often see a noticeably slower TTFB than local visitors.
Server-side fixes that actually move the number
Faster storage is one of the most direct fixes, moving from spinning disks to NVMe SSD cuts the time it takes the server to read and write data during page processing, which shows up immediately in a lower TTFB. Server-level page caching, whether through LiteSpeed Cache, a similar caching layer, or a CMS caching plugin, means repeat requests for the same page skip the database query and PHP processing entirely, serving a pre-built copy instead.
Reducing plugin bloat on WordPress sites also helps meaningfully, since every active plugin can add its own database queries or processing on each page load, and disabling ones you don't actually use trims that overhead. Choosing a data center location close to your main audience, or adding a CDN in front of your origin server, reduces the network latency portion of TTFB for visitors further away.
Measuring TTFB correctly
Browser DevTools' Network tab shows TTFB directly for any request, listed under timing when you click a request and look at the waterfall breakdown. Third-party tools like PageSpeed Insights and GTmetrix report it as part of their full page audit, usually with a benchmark noting whether your value falls in a good, needs improvement, or poor range.
Testing from multiple locations matters, since a single test from one region won't reveal that visitors on the other side of the world are seeing double the TTFB due to distance. Testing both a logged-out cached page and a logged-in or uncached page separately is also useful, since caching can mask a slow underlying server that only becomes obvious once the cache is bypassed.
Storage and Server Choices Drive TTFB
Since TTFB is fundamentally about how quickly your server can process a request, the underlying infrastructure matters more here than almost any front-end optimization. A visitor waiting on a slow database query or a congested shared server will feel that delay no matter how well-compressed the rest of the page is.
Hosting Cheap runs every account on pure NVMe SSD storage paired with LiteSpeed, giving page processing and database queries faster read and write access than spinning disks, plus built-in caching support that skips repeat processing for cached pages entirely.
- NVMe SSD storage for faster database and file read speed
- LiteSpeed server with built-in caching to skip repeat processing
- 99.9% uptime keeping response times consistent, not just fast
- Free managed migration if your current host is the bottleneck
Why Hosting Cheap
What you get
Faster perceived load
A low TTFB means the browser starts rendering sooner, improving felt speed.
Better Core Web Vitals
TTFB directly feeds into Largest Contentful Paint scoring.
Higher search visibility
Page experience signals factor into how Google ranks competing pages.
More consistent under load
Fast storage and caching keep TTFB steady even during traffic spikes.
Better mobile experience
Slower mobile connections are especially sensitive to server response delays.
Lower bounce risk
Visitors are less likely to leave before the page even starts to appear.
How It Works
Get set up in a few steps
Measure current TTFB
Check DevTools Network tab or a tool like PageSpeed Insights for your baseline.
Enable server-side caching
Turn on LiteSpeed Cache or a CMS caching plugin to skip repeat processing.
Move to faster storage
Host on NVMe SSD infrastructure so database and file reads happen quicker.
Included
Everything you need, on every plan
- Measure TTFB with browser DevTools or a speed testing tool
- Enable a server-side or CMS-level page cache
- Reduce active plugins that add unnecessary database queries
- Confirm your hosting runs SSD or NVMe storage, not spinning disks
- Check data center location relative to your main audience
- Add a CDN if visitors are geographically spread out
- Re-test TTFB after each change to confirm improvement
- Test both cached and uncached page loads separately
FAQ
Frequently asked questions
What is TTFB in simple terms?
TTFB is the time between requesting a page and receiving the very first byte back from the server, covering connection setup and server processing before any content starts arriving.
What is a good TTFB value?
Under roughly 200-400ms is generally considered good, with anything above 600-800ms usually flagged as needing improvement by speed testing tools.
Does TTFB affect SEO?
Yes, TTFB feeds directly into Largest Contentful Paint, one of Google's Core Web Vitals, so a slow TTFB can hold back your page experience score.
Can a CDN fix a slow TTFB?
A CDN helps mostly with the network distance portion for visitors far from your origin server, but it won't fix slow database queries or processing at the source.
Why is my TTFB slow only on some pages?
Pages that run more database queries or aren't covered by your cache configuration, like search results or account pages, often show a slower TTFB than a cached homepage.
Is TTFB the same as page load time?
No, TTFB is only the time until the first byte arrives, page load time includes everything after that, including downloading and rendering all images, scripts, and styles.
Lower Your TTFB With Faster Infrastructure
Move to NVMe SSD hosting with built-in caching and let free migration handle the switch.
Get Started