A good TTFB (time to first byte) is 0.8 seconds or less, according to Google’s web.dev guidance. Between 0.8 and 1.8 seconds needs improvement, and anything above 1.8 seconds is poor. TTFB measures how long a browser waits before the server sends the first piece of your page, so it mostly reflects hosting, caching, and backend code.
Why Your Site Feels Slow Before Anything Even Loads
You click your own homepage and stare at a white screen. Nothing happens for a second or two, then everything appears at once. That blank pause is the problem this article is about.
Most speed advice jumps straight to compressing images or removing plugins. Those things matter, but they happen after the server responds. If the server itself is slow to answer, every other optimization starts from behind.
This guide explains what TTFB really measures, what numbers you should aim for, how to test it yourself in under five minutes, and how to tell whether the fix belongs to your website or your hosting.
What Is TTFB (Time to First Byte)?
TTFB is the time between a browser requesting a page and receiving the very first byte of the response from the server.
It is not a single delay. It bundles several steps together:
- Redirects, if the visitor typed an old or non secure address
- DNS lookup, where the browser finds your server’s IP address
- Connection setup, including the TCP connection and the TLS (SSL) handshake
- Server processing, where your host runs PHP, queries the database, and builds the page
- The first byte traveling back across the network to the visitor
Think of ordering at a restaurant. TTFB is not how long the whole meal takes. It is how long you wait before the waiter brings anything to the table. A slow kitchen, a waiter who got lost, or a restaurant across town all make that wait longer.
What Is a Good TTFB Score?
Google recommends a TTFB of 0.8 seconds or less for most sites, measured at the 75th percentile of real visits.
| TTFB (75th percentile) | Rating | What it usually means |
|---|---|---|
| 0.8 seconds or less | Good | Caching and hosting are doing their job |
| 0.8 to 1.8 seconds | Needs improvement | Something is uncached, overloaded, or far away |
| Over 1.8 seconds | Poor | Server, database, or plugin bottleneck worth fixing now |
Two details are worth knowing here.
The 75th percentile matters. Google looks at real visitor data, and the score reflects the experience of most visitors, not your best test. A page that loads in 0.3 seconds for you but 2 seconds for mobile users in another country is not “good.”
Lower is better, but chasing zero is pointless. In our experience, well cached pages on decent hosting typically land between 0.1 and 0.4 seconds. Uncached dynamic pages like a WooCommerce cart will usually be slower, and that is normal.
Is TTFB a Google Ranking Factor?
No, not directly. TTFB is not one of the three Core Web Vitals, but it strongly influences Largest Contentful Paint (LCP), which is.
The current Core Web Vitals are:
| Metric | Measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading speed of main content | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness to clicks and taps | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
Here is why TTFB still matters for SEO. Your largest image or headline cannot start loading until the HTML arrives. If TTFB eats 1.5 seconds, you have only about 1 second left to hit a good LCP. That is a tight budget, especially on mobile.
Our take: treat TTFB as the foundation of LCP. Fixing it rarely produces a dramatic ranking jump on its own, but a poor TTFB makes a good LCP score very hard to reach, and slow first loads cost you visitors regardless of rankings.
How Do You Check Your TTFB?
The fastest free method is Google PageSpeed Insights, which shows real user TTFB from the Chrome User Experience Report when your site has enough traffic.
Method 1: PageSpeed Insights (real user data)
- Go to pagespeed.web.dev and enter your URL
- Look at the top section labeled with real user experience data
- Find “Time to First Byte (TTFB)” in the expanded metrics
If your site is too small for field data, you will only see lab results. Those are still useful for spotting obvious problems.
Method 2: Chrome DevTools (quick spot check)
- Open your site in Chrome and press F12
- Click the Network tab and reload the page
- Click the first document request (your page URL)
- Open the Timing tab and read “Waiting for server response”
That “waiting” figure is the server processing portion of TTFB, which is the part your host controls most.
Method 3: WebPageTest (location testing)
WebPageTest.org lets you test from different cities and devices. This is the best way to see how distance affects your TTFB. Run one test near your server and one far away, then compare.
A testing tip most guides skip
Always test at least three times. The first request often hits an empty cache and looks slow. If the first test is slow but the second and third are fast, your caching works but expires too quickly. If all three are slow, caching is missing or bypassed entirely.
What Causes a High TTFB?
A high TTFB almost always comes from one of five places: no page caching, slow or overloaded hosting, heavy backend code, distance between server and visitor, or extra redirects and DNS delays.
1. No page caching
This is the most common cause we see on WordPress sites. Without a page cache, every visit forces the server to run PHP and query the database from scratch. With caching, the server hands over a ready made HTML copy instead.
2. Underpowered or crowded hosting
On budget shared hosting, your site shares CPU and memory with many others. When a neighbor gets a traffic spike, your response time can climb even though nothing on your site changed. Old hard drives instead of NVMe SSD storage also slow database reads.
3. Heavy plugins, themes, and database bloat
Page builders, related post plugins, live chat widgets that run server side, and bloated wp_options tables all add processing time. Each database query adds a few milliseconds. Hundreds of them add up.
4. Outdated PHP versions
Newer PHP 8 releases are measurably faster than PHP 7, and older versions no longer receive security updates. Running PHP 7.4 in 2026 costs you speed and exposes you to risk.
5. Physical distance and network setup
Data travels fast, but not instantly. A visitor in Los Angeles loading a site hosted in Singapore waits longer on every round trip. Missing HTTP/2 or HTTP/3 support, older TLS versions, and a slow DNS provider stack more delay on top.
Is It My Website or My Hosting? A Simple Diagnostic
This is the question website owners ask us most, and the answer is usually findable in ten minutes.
| What you see | Most likely cause | Where to fix it |
|---|---|---|
| Slow TTFB everywhere, even on a blank test page | Server or hosting plan | Hosting |
| Fast static files, slow HTML pages | Missing page cache or heavy PHP | Website |
| Fast for you, slow for distant visitors | Server location, no CDN | Hosting and CDN |
| Fast most of the day, slow at peak hours | Shared resource limits | Hosting |
| Slow only when logged in or on cart pages | Uncached dynamic pages, database load | Website and hosting |
| Slow after a plugin update | That plugin | Website |
A practical test: upload a plain test.html file with one line of text to your site’s root folder and check its TTFB in DevTools. Static HTML needs no PHP or database. If even that file is slow, the problem is the server or network, not WordPress.
How to Reduce TTFB: 9 Fixes Ranked by Impact
Start with page caching and a current PHP version, since those two changes fix the majority of slow TTFB cases on WordPress sites.
- Turn on full page caching. Use a server level cache such as LiteSpeed Cache on LiteSpeed servers or NGINX FastCGI cache, or a plugin like WP Rocket or W3 Total Cache. This single step often cuts TTFB by more than half.
- Upgrade to a supported PHP 8 version. Check your control panel for the PHP selector, and test your site on a staging copy first in case an old plugin breaks.
- Enable OPcache. It stores compiled PHP code in memory so the server does not recompile it on every request. Most good hosts enable it by default.
- Add object caching with Redis or Memcached. This speeds up repeated database queries, which helps logged in users, membership sites, and WooCommerce stores that cannot use full page caching everywhere.
- Use a CDN. Services like Cloudflare cache content on servers closer to your visitors, shrinking the distance problem. Some CDNs can also cache full HTML pages at the edge.
- Choose a server location near your audience. If most customers are in the United States, a US data center beats a European one for them.
- Clean up plugins and the database. Remove plugins you do not use, clear expired transients, and limit post revisions. Query Monitor is a free plugin that shows which plugins run slow queries.
- Eliminate redirect chains. Make sure
http,www, andhttpsversions all point straight to your final URL in one hop, not two or three. - Enable HTTP/3 and TLS 1.3. TLS 1.3 needs fewer round trips to set up a secure connection than TLS 1.2, and HTTP/3 over QUIC can speed up connections on unstable mobile networks.
A Real World Example
Here is a typical pattern we see with small business WordPress sites. The numbers below are illustrative, but the sequence is common.
A local service business runs a page builder theme on a basic shared plan with PHP 7.4 and no caching. PageSpeed Insights flags “Reduce initial server response time,” and TTFB sits around 1.9 seconds.
| Step taken | Approximate TTFB |
|---|---|
| Starting point | 1.9 seconds |
| Enabled full page caching | 0.6 seconds |
| Upgraded PHP 7.4 to PHP 8.3 | 0.5 seconds |
| Added Cloudflare CDN | 0.25 seconds for distant visitors |
Notice where the biggest gain came from. Caching did most of the work. The CDN mattered most for visitors far from the server. Your results will differ, but the order of priorities usually holds.
Shared vs VPS vs Managed Hosting: How Each Affects TTFB
| Hosting type | Typical TTFB behavior | Best for |
|---|---|---|
| Shared hosting | Can be fast with caching, but varies with neighbors and resource limits | New sites, blogs, brochure sites |
| VPS hosting | More consistent, since CPU and RAM are reserved for you | Growing businesses, stores, agencies |
| Managed WordPress hosting | Fast by default with server caching and tuning handled for you | Owners who want speed without the setup |
| Dedicated server | Most consistent under heavy load | High traffic sites and custom apps |
An honest opinion: a well configured shared plan with server caching can outperform a poorly configured VPS. Upgrading your plan is not automatically the answer. Configuration matters as much as raw power, so fix caching and PHP first, then upgrade if you still hit limits.
Common TTFB Mistakes to Avoid
- Testing once and panicking. A single cold cache test is not your real TTFB.
- Stacking two caching plugins. They conflict and can make pages slower or break them.
- Judging from your own fast connection. Your office fiber line does not represent a mobile visitor three states away.
- Blaming images for slow TTFB. Images load after the first byte. They affect LCP, not TTFB.
- Upgrading hosting before enabling caching. You may pay more and see little change.
- Ignoring the host’s resource usage graphs. CPU or entry process limits hit at peak times are a clear signal it is time for more resources.
When Should You Call in Professional Help?
Most caching and PHP fixes are safe to do yourself with a backup in place. It makes sense to get help when:
- TTFB stays poor even for a plain static HTML file
- Your site runs WooCommerce, memberships, or custom code that cannot be fully cached
- You see database errors, 503 errors, or timeouts during traffic spikes
- You are planning a migration to a new server and cannot afford downtime
A good hosting support team can read server logs, check slow query logs, and spot resource limits that are invisible from the WordPress dashboard.
Key Takeaways
- TTFB measures how long a browser waits for the first byte of a page from the server.
- A good TTFB is 0.8 seconds or less at the 75th percentile, per Google’s web.dev guidance. Over 1.8 seconds is poor.
- TTFB is not a Core Web Vital, but it directly limits how fast your LCP can be.
- The biggest causes are missing page caching, weak or crowded hosting, heavy plugins, old PHP, and distance.
- Fix caching and PHP first, then add a CDN, then consider a hosting upgrade.
- Test at least three times from more than one location before drawing conclusions.
- A static HTML test file tells you quickly whether the problem is WordPress or the server.
Frequently Asked Questions
What is TTFB in simple terms?
TTFB, or time to first byte, is how long a visitor’s browser waits after requesting a page before the server sends back the first piece of data. It includes DNS lookup, connection setup, secure handshake, and server processing time. A low TTFB means the server starts responding quickly, which lets the rest of the page begin loading sooner.
What is a good TTFB for WordPress?
For WordPress, aim for 0.8 seconds or less to meet Google’s “good” threshold. With full page caching on quality hosting, cached WordPress pages often respond in 0.1 to 0.4 seconds. Uncached pages such as carts, checkouts, and logged in dashboards will usually be slower, so judge them separately from your public content pages.
Does TTFB affect SEO?
TTFB is not a direct ranking factor and is not one of Google’s Core Web Vitals. However, it strongly affects Largest Contentful Paint, which is a Core Web Vital. A slow TTFB leaves less time for your main content to load within 2.5 seconds, and slow first loads also increase the chance visitors leave early.
Why is my TTFB high but my site loads fast afterward?
This usually means the server is slow to build the page, but the files it sends afterward are well optimized. Common causes are missing page caching, a cache that expires too often, slow database queries, or an outdated PHP version. Test several times; if later tests are fast, your cache is working but needs a longer lifetime.
Can a CDN reduce TTFB?
Yes. A CDN like Cloudflare reduces TTFB by serving content from locations closer to your visitors and by speeding up connection setup. The biggest gains come when the CDN caches full HTML pages, not just images and scripts. For visitors far from your server, the improvement can be significant, while nearby visitors may see only modest changes.
What is the difference between TTFB and page load time?
TTFB measures only the wait until the first byte of the HTML arrives. Page load time covers everything afterward, including images, stylesheets, scripts, and fonts. A site can have a fast TTFB but still load slowly because of heavy images, or a slow TTFB with lightweight pages. Both need attention for a genuinely fast site.
Will upgrading my hosting plan fix a slow TTFB?
Sometimes, but not always. If your site already uses page caching and a current PHP version but TTFB stays high, or your host shows you hitting CPU and memory limits, an upgrade to VPS or managed hosting often helps. If caching is missing, fix that first, because a bigger plan alone may not change much.
How often should I check my TTFB?
Check it after any major change, such as a new theme, plugin, PHP upgrade, or hosting move. Otherwise, a monthly check in PageSpeed Insights or Google Search Console’s Core Web Vitals report is enough for most small business sites. Sudden jumps usually point to a recent update or a resource limit on the server.
Conclusion
A slow TTFB is one of the few speed problems you cannot fix with image compression or a lighter design. It lives in your caching setup, your PHP version, your database, and your hosting environment. The good news is that most sites can move from “poor” to “good” with a short list of changes: turn on page caching, run a current PHP 8 version, clean up heavy plugins, and put a CDN in front of the site.
If you have worked through those steps and your server still takes too long to answer, the hosting itself may be the bottleneck. The team at WebHostServers can review your current setup, check how your server handles real traffic, and point you toward the plan that fits your site’s needs. Reach out to our team whenever you would like a second opinion on your site’s speed.