Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 37 ยท Metrics and Core Web Vitals

TTFB, FCP and Other Performance Metrics

Learn the supporting performance metrics beyond Core Web Vitals, including TTFB, First Contentful Paint, Total Blocking Time, Speed Index and Time to Interactive, and when to use each.

Core Web Vitals tell you how the experience feels. A second group of metrics tells you why. They split the load into smaller moments so you can see whether the delay is on the server, in the network, in render-blocking resources or in JavaScript.

This lesson covers the supporting metrics you will meet in Lighthouse reports and monitoring tools.

Time to First Byte (TTFB)

TTFB is the time from the start of navigation until the first byte of the HTML response arrives. It includes redirects, DNS, connection, TLS, the request and the server's thinking time. A common target is 800 ms or less at p75.

Because everything else waits for the HTML, a slow TTFB pushes every later metric back. Fixes: caching HTML at a CDN, faster back-end code and queries, fewer redirects, HTTP/2 or HTTP/3 and edge rendering.

First Contentful Paint (FCP)

FCP marks when the browser first paints any content from the DOM: text, an image, an SVG or a non-white canvas. It is the moment the user first sees that "something is happening". Good is 1.8 s or less.

FCP is earlier than LCP; the gap between them shows how long it takes for the main content to arrive after the first scrap.

First Paint

First Paint (FP) is any pixel that differs from the blank page, even just the background colour. It is rarely used on its own. Prefer FCP.

Total Blocking Time (TBT)

TBT is a lab metric. It sums the "blocking" part of every long task between FCP and Time to Interactive: for each task, the time beyond 50 ms counts. A 120 ms task adds 70 ms. TBT is a good lab proxy for INP, because field INP needs real interactions that a lab run does not have. A good TBT is 200 ms or less on mobile.

JS Compute Total Blocking Time

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The 400 ms task contributes 350 ms alone. Breaking it into eight 50 ms tasks would drop TBT to zero, even though the total work is identical.

Speed Index

Speed Index describes how quickly the visible part of the page is filled in. A tool records a video of the load, compares each frame to the final one, and gives a score in milliseconds: lower is better. Two pages with the same LCP can differ in Speed Index if one shows content gradually and the other all at once at the end.

Time to Interactive (TTI)

TTI was the moment a page became reliably responsive. Lighthouse removed it from its score because it was fragile and sensitive to outliers; use TBT and INP instead.

The load event and DOMContentLoaded

  • DOMContentLoaded fires when the HTML is parsed and deferred scripts have run.
  • load fires when all resources, including images, have finished.

These describe browser mechanics, not experience. A page can fire load long after the user has what they need, or before an image-heavy hero is visible.

A map of the metrics

flowchart LR
  A["TTFB"] --> B["FCP"]
  B --> C["LCP"]
  B --> D["TBT (lab)"]
  C --> E["Speed Index"]
  D --> F["INP (field)"]

TTFB and FCP come first; LCP and INP are the vitals they feed into.

Metric Type What it tells you Target
TTFB Field and lab Server and network speed 800 ms or less
FCP Field and lab First sign of life 1.8 s or less
LCP Field and lab Main content ready 2.5 s or less
TBT Lab Main thread congestion 200 ms or less
INP Field Interaction responsiveness 200 ms or less
CLS Field and lab Visual stability 0.1 or less
Speed Index Lab Visual progress Lower is better

Reading FCP and TTFB in code

Read FCP and TTFB with the Performance API

Choosing what to watch

Start with the three vitals as your scoreboard. Add TTFB and FCP to spot server and render-blocking issues. Add TBT in lab tests to catch JavaScript regressions early, before real users feel them. Avoid collecting a metric nobody acts on.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does TTFB include?

    TTFB spans everything from navigation start to the first response byte.
  2. 2. A 180 ms task adds how much to TBT?

    Only the portion above 50 ms counts: 180 - 50 = 130 ms.
  3. 3. Which metric is a lab proxy for INP?

    TBT measures main-thread congestion, which is the main cause of poor INP.
  4. 4. FCP marks

    First Contentful Paint is the first text, image or non-blank content shown.

Summary

  • TTFB shows server and network speed; FCP shows the first visible content.
  • TBT (lab) sums the time beyond 50 ms of each long task and approximates INP.
  • Speed Index measures how quickly the viewport fills; TTI is retired in favour of TBT and INP.
  • load and DOMContentLoaded are mechanics, not experience.

Next: HTTP Requests and Latency