Skip to main content

TTFB by page

TTFB by page without noise

Vasil Dachev avatar
Written by Vasil Dachev
Updated over 3 weeks ago


What is TTFB by page

TTFB by page shows the Time to First Byte (TTFB) for your most visited pages. This lens is useful to find pages that are experiencing backend or network delays, starting from the most visited pages first. To view all pages, maximize the lens widget to see the full list, sorted by traffic.

Pages are only the website pages that have been accessed by your real users for the selected period and device. If a page has not been visited, this means it has not reported TTFB and it will not show up in the widget.

TTFB is a foundational performance metric that represents how quickly your server responds with the first byte of data after a request is made.



Healthy TTFB by page sample


Should you worry

A healthy TTFB by page lens looks all green. Some pages may be greener than others, but as long as there's no yellow or red, it’s considered healthy. The greener the page, the faster your server is responding.

Unhealthy TTFB by page sample

In the example below, the TTFB by page reveals that the /blog page is the most visited and at the same time has the slowest real user TTFB values, whereas the rest of the popular pages are fast.

Resolving unhealthy TTFB by page

Go-to action plan to resolve an unhealthy TTFB by page:

  1. Ask Uxi to analyze your TTFB by page values and suggest improvements.

  2. Use Filters to focus on slow segments in your TTFB by page, then look across the other TTFB lenses to find which ones show the worst backend response times with the most pageviews.

  3. Simulate TTFB of the suspected lens to see if fixing it will resolve the TTFB by page. If yes, this is where the resolution focus should be.

  4. Use an automated optimization tool like Navigation AI to improve your TTFB by page values.

  5. Once you’ve improved TTFB, set an alert to be the first to know if it starts worsening again.

Try it yourself

Discover how your website performs with real user data.

Did this answer your question?