Time to First Byte (TTFB) Definition

Time to first byte (TTFB) is a web performance metric that measures the time between the start of a page request and the moment the browser receives the first byte of the response from the server.

TTFB is not a Core Web Vital itself, but it comes before everything else: nothing can be displayed until the first byte arrives. A slow TTFB delays Largest Contentful Paint and every other loading metric. As a rough guide, web.dev suggests a TTFB of 0.8 seconds or less.

time to first byte definition

What Is Time to First Byte?

When a visitor opens a page, several steps happen before the browser receives any content. TTFB covers them all:

  1. Redirects, if the requested URL redirects to another one;
  2. DNS lookup, to find the server’s address;
  3. Connection to the server, including the secure TLS handshake for HTTPS;
  4. Request and server processing: the server receives the request, runs code, queries the database and starts sending the response.

On dynamic sites, such as WordPress without caching, server processing is often the largest part.

📌 In brief
Time to first byte (TTFB) definition: what this server response metric measures, the 0.8-second guideline, why it affects LCP and how to reduce it.
On the menu:
  • TTFB Guidelines
  • Why TTFB Matters for SEO
  • Common Causes of a Slow TTFB
  • How to Reduce TTFB
  • How to Measure TTFB
By SeoYass, SEO consultant since 2010 · Updated on

TTFB Guidelines

TTFB Rating
0.8 seconds or less Good
Between 0.8 and 1.8 seconds Needs improvement
More than 1.8 seconds Poor

web.dev presents these values as a rough guide. Because TTFB is not a Core Web Vital, meeting the threshold is not strictly required, as long as the page achieves good results on the metrics that matter, such as LCP.

Why TTFB Matters for SEO

  • It delays LCP: time to first byte is the first of the four parts of Largest Contentful Paint; a 2-second TTFB makes a good LCP almost impossible.
  • Crawling: Google adapts how much it crawls to how quickly and reliably a server responds. Slow responses can reduce crawling, which matters for large sites. See crawl budget.
  • User experience: a blank screen during the wait makes visitors doubt the page is loading.
  • Diagnosis: a high TTFB points to the server side, hosting, caching or redirects, rather than to images or scripts.

Common Causes of a Slow TTFB

  • Slow or overloaded hosting, especially low-cost shared servers.
  • No page caching: every visit forces the server to build the page from scratch.
  • Heavy database queries and too many plugins running on each request.
  • Outdated server software, such as old PHP versions.
  • Distance: visitors far from the server wait longer without a CDN.
  • Redirects before the final URL, each adding a round trip. See redirect chain.

How to Reduce TTFB

  1. Enable page caching so the server delivers ready-made HTML instead of generating it for each visit.
  2. Use a CDN to serve content from locations close to visitors, ideally including cached HTML.
  3. Choose suitable hosting with enough resources and a recent PHP version.
  4. Reduce server work: remove unnecessary plugins, optimise database queries and use object caching where available.
  5. Avoid redirects: link directly to final URLs and use one redirect at most for HTTP and www variants.
  6. Keep connections efficient: modern protocols such as HTTP/2 or HTTP/3 and proper TLS configuration.

How to Measure TTFB

  • PageSpeed Insights: shows TTFB from real visitors in the field data section, when enough data is available.
  • Chrome DevTools: the Network panel shows the waiting time for the server response of each request.
  • Online speed tests: let you test from different locations.
  • Search Console Crawl Stats: shows the average response time of the server to Googlebot’s requests.

Test several times and from the visitors’ region: a single measurement can be distorted by a cold cache or a temporary load peak.

TTFB on WordPress Sites

On WordPress, the biggest TTFB gains usually come from a page caching plugin or server-level cache, which can turn a dynamic response of a second or more into a fast delivery of cached HTML. Pages that cannot be cached, such as carts, accounts or pages with personalised content, depend more on hosting quality and on reducing the number of active plugins. After any change, check that the cache is actually served, for example by looking at the response headers, and that logged-out visitors receive cached pages.

Example: A Driving School Website

A driving school in Leicester has a TTFB of about 2 seconds on mobile, measured repeatedly. The site runs on an old PHP version, with 35 active plugins and no page cache. The PHP version is updated after testing, unused plugins are removed and a page cache is enabled, with a CDN for visitors elsewhere in the UK. The TTFB drops well under the 0.8-second guideline for cached pages, and LCP improves as a direct result, since the browser receives the HTML much sooner.

Common Misconceptions

  • “TTFB is a Core Web Vital”: it is not; it is a supporting metric that strongly influences LCP.
  • “A fast TTFB means a fast page”: heavy images or scripts can still make the page slow after the first byte.
  • “Only the hosting matters”: caching, plugins and redirects often matter as much as the server itself.

TTFB, Mobile Networks and Field Data

Field data measures TTFB from real visitors, on their own devices and networks. A visitor on a weak mobile connection or far from the server will see a higher TTFB than a test run from a fast office connection close to the hosting provider. This is why lab tests can look excellent while PageSpeed Insights field data shows a slower TTFB. When comparing results, look at the device type, the location of the test and whether the page was already in cache. Improvements to caching and CDN coverage usually benefit mobile visitors most, since every round trip on a mobile network costs more time.

Time to First Byte: Key Takeaways

TTFB measures the time until the browser receives the first byte of a page, including redirects, DNS, connection and server processing. It is not a Core Web Vital, but it directly delays LCP and influences crawling. Aim for roughly 0.8 seconds or less with page caching, a CDN, suitable hosting, fewer plugins and no unnecessary redirects. See also Core Web Vitals.

From theory to a faster server

Knowing what TTFB measures is the first step. The next is checking how fast your server answers, and what slows it down.

  • An action plan adapted to your situation
  • Clear explanations, no needless jargon
  • Direct application to your sector
TTFBDefinitionCustomers ↑
// RESULTS & REFERENCES

From diagnosis to results, step by step

Here is how I handle ttfb issues on client sites, and what my clients say about my work.

+350COMPLETED PROJECTS
+320SATISFIED CLIENTS
5.0 ★VERIFIED GOOGLE REVIEWS
+17YEARS OF EXPERIENCE
001REFERENCES / VERIFIED REVIEWS

What Is Time to First Byte?

When a visitor opens a page, several steps happen before the browser receives any content. TTFB covers them all:

EXPERTISEMETHODFIELD WORK
11ACTIVE PROJECTS
5.0GOOGLE RATING
READ THE REFERENCES →
002PORTFOLIO / PROJECTS

TTFB Guidelines

TTFBRating0.8 seconds or lessGoodBetween 0.8 and 1.8 secondsNeeds improvementMore than 1.8 secondsPoor
web.dev presents these values as a rough guide. Because TTFB is…

EXPERTISEMETHODFIELD WORK
6-12MONTHS FOR SOLID RESULTS
+350COMPLETED PROJECTS
VIEW THE PORTFOLIO →
003METHOD / EXPERTISE

Why TTFB Matters for SEO

It delays LCP: time to first byte is the first of the four parts of Largest Contentful Paint; a 2-second TTFB makes a good LCP almost impossible.Crawling: Google adapts…

EXPERTISEMETHODFIELD WORK
100%POSITIVE REVIEWS 2026
11ACTIVE PROJECTS
SEE MY SEO SERVICES →
WANT TO BE THE NEXT CASE?Tell me about your project and I will reply with a first diagnosis.
SEND A BRIEFFREE MINI-AUDIT

FAQ: TTFB

What is time to first byte?

The time between the start of a page request and the moment the browser receives the first byte of the server's response.

What is a good TTFB?

web.dev suggests 0.8 seconds or less as a rough guide; more than 1.8 seconds is considered poor.

Is TTFB a Core Web Vital?

No. It is a supporting metric, but it directly affects Largest Contentful Paint, which is a Core Web Vital.

What causes a slow TTFB?

Slow hosting, no page caching, heavy database work, too many plugins, distance from the server and redirects.

How do I reduce TTFB on WordPress?

Enable page caching, use a CDN, update PHP, remove unnecessary plugins and avoid redirects.

Does TTFB affect crawling?

Google adjusts crawling to the server's speed and health, so slow and unreliable responses can reduce how much is crawled.

Do you want to work with me?

SeoYass, SEO consultant17+ years of SEO
Your SEO consultant
SeoYass

I am SeoYass, an SEO expert with over 17 years of experience. I have worked with small and medium-sized businesses, successfully completing more than 350 projects.

Passionate about local SEO, I continue to learn and refine my strategies to deliver the best performance for my clients.

350+Projects
5.0 ★Google reviews
17+Years of experience