Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is TTFB? A Plain Explanation

Short answer

TTFB, or Time to First Byte, measures the time between starting to load a page and the arrival of the first byte of the server's response. It covers the redirect, DNS lookup, connection and server work that happens before anything can render. A good TTFB is 0.8 seconds or less, and it sets a floor for every later metric, including LCP.

Key takeaways

  • TTFB measures the time until the first byte of a server response arrives.
  • A good TTFB is 0.8 seconds or less, and a poor one is over 1.8 seconds, as of November 2026.
  • TTFB covers redirect, DNS, connection, TLS and server work, not just the server.
  • A slow TTFB delays every later metric, including First Contentful Paint and LCP.
  • Caching and a fast host are the two fixes that move TTFB the most on WordPress.

What is TTFB?

Time to First Byte (TTFB) measures the time between starting to navigate to a page and the arrival of the first byte of the response.

It is a server metric, not a page metric. It tells you how long the visitor waits before the browser gets anything back at all. Until that first byte arrives, the browser cannot paint a single pixel.

The name is literal: the clock stops at the first byte, not at the first full page. A page can have a fast TTFB and still load slowly, but it cannot have a fast load with a slow TTFB.

What makes up TTFB?

TTFB is the sum of five phases, and each one adds its own delay to the total.

PhaseWhat happens
RedirectThe browser follows redirects to the final URL
DNS lookupThe domain name is turned into an IP address
Connection and TLSThe browser connects and agrees on encryption
Server workWordPress builds the page from the database
Response startThe first byte travels back to the browser

Server work is usually the largest phase on WordPress, because the page is built fresh on every visit without a cache. DNS and connection time matter most for visitors far from the server.

The browser measures TTFB as the gap between startTime and responseStart in the Navigation Timing API. Developers can read that value with a PerformanceObserver, or with the onTTFB function from the web-vitals library.

What is a good TTFB score?

A good TTFB is 0.8 seconds or less, and Google judges it at the 75th percentile of users.

TTFBRatingWhat it means
0.8 seconds or lessGoodThe server answers quickly
0.8 to 1.8 secondsNeeds improvementVisitors wait longer than they should
Over 1.8 secondsPoorThe server is slow to answer

Google's guide says most sites should aim for 0.8 seconds or less, because TTFB comes before First Contentful Paint and LCP. A slow first byte pushes every later metric back by the same amount.

TTFB is not a Core Web Vital, so it does not have its own ranking signal. It matters because it feeds LCP, which is a Core Web Vital, and because visitors notice a page that sits blank.

What causes a slow TTFB on WordPress?

The most common cause is a page built from scratch on every visit, with no page cache to serve a ready-made copy.

  • No page caching: WordPress runs PHP and database queries for every single visit.
  • Slow or crowded hosting: a shared server with too many sites answers slowly.
  • Too many plugins: each one can add queries and work to every page load.
  • No object cache: the server reads the same options from the database again and again.
  • Far-away server: the response travels a long way to reach the visitor.

WordPress's own optimization guide warns that without caching, performance slows to a halt as page requests stack up. It recommends a caching plugin first, because it gives the biggest gain for the least work.

Database work is the hidden cost. WordPress repeats many queries on every request, so a persistent object cache that keeps options in memory can cut TTFB a lot. Your host must offer a cache server for this to work.

How do you check TTFB on your WordPress site?

Open Chrome DevTools, go to the Network tab, reload the page and read the TTFB of the first document request.

PageSpeed Insights also reports TTFB in its lab results, and the web-vitals library can measure it from real visitors. For a quick check, online speed tools list TTFB next to the other timings for each request.

Test from a location near your visitors, because distance adds time to every phase. A TTFB of 0.3 seconds near the server can be 1.2 seconds on the other side of the world.

If your site gets enough traffic, the Chrome User Experience Report holds field TTFB data too. See our guide on lab data versus field data to learn why the two numbers can differ.

How do you improve TTFB in WordPress?

Start with page caching, because it removes the slowest phase, which is building the page on every visit.

  1. Turn on a page caching plugin so the server sends a ready-made page.
  2. Ask your host about a persistent object cache such as Redis or Memcached.
  3. Delete unused plugins and themes, and keep PHP and WordPress current.
  4. Use a CDN with full-page caching, or move closer to your visitors with a better host.
  5. Cut redirects, because each one adds a full round trip before the server even starts.

For hosting, read whether hosting affects WordPress speed before you pay for an upgrade. A host with solid-state drives and enough memory often cuts TTFB more than any plugin can.

Measure after each change in DevTools, where the new TTFB shows at once. Field data takes up to 28 days to catch up, so use lab numbers to confirm the fix and field numbers to confirm the trend.

What mistakes should you avoid?

Do not judge TTFB from a single test, because server load and network conditions change the number from minute to minute.

  • Testing only from your own city and missing slow times for far-away visitors.
  • Adding a CDN and skipping the cache, when the server is the real problem.
  • Installing three caching plugins at once, which can fight each other.
  • Forgetting that uncached pages, such as carts and checkout, will always be slower.

Also avoid blaming the theme first. A heavy theme can slow a page, but TTFB is set before the theme's files even arrive. Fix the server and the cache, then look at the theme.

How is TTFB different from LCP and FCP?

TTFB measures when the first byte arrives, while First Contentful Paint measures when the first content appears, and LCP measures when the largest content appears.

The three metrics form a chain: the server must answer before the browser can paint, and it must paint before the largest element can render. A slow TTFB pushes the whole chain back, which is why fixing it helps LCP too.

TTFB is the only one of the three that is purely about the server and the network. LCP and FCP also depend on images, fonts and scripts, so they need different fixes once the server is fast.

If your LCP is slow, check TTFB first. Our guide to how fast a WordPress site should load puts the numbers side by side so you can see which part of the chain is slow.

Frequently asked questions

Is TTFB a Core Web Vital?

No. TTFB is a supporting metric, not one of the three Core Web Vitals. It still matters, because a slow first byte delays LCP, which is a Core Web Vital, and because a blank page makes visitors leave.

Why is my TTFB high only sometimes?

TTFB changes with server load, cache state and network conditions. A page served from cache answers fast, while the same page built fresh after the cache clears is slower. Traffic spikes, slow database queries and far-away visitors can all push it up.

Can a CDN fix a slow TTFB?

A CDN helps when the slow part is distance, because it serves files from a server near the visitor. It does not fix a slow WordPress server, since the page still has to be built. For that, you need page caching, an object cache or a faster host.

What is the difference between TTFB and server response time?

Server response time is one part of TTFB: the time the server spends building the page. TTFB adds the redirect, DNS lookup, connection and TLS phases on top of it. A fast server can still show a slow TTFB if the connection is slow.

Does TTFB matter for SEO?

Only through LCP, which is a Core Web Vital that Google's ranking systems use. A slow TTFB drags LCP down, and that can cost rankings. Fixing TTFB is also worth doing for visitors, since a page that sits blank loses readers.

Sources

  1. Time to First Byte (TTFB) web.dev
  2. Web Vitals web.dev
  3. Largest Contentful Paint (LCP) web.dev
  4. Optimization WordPress Developer Resources
  5. Overview of CrUX Chrome for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test