What is TTFB by pageview type
TTFB by pageview type shows Time to First Byte (TTFB) for two types of pageviews:
First in session pageviews – the first pageview when a user starts a new session
Subsequent in session pageviews – all additional pageviews that follow in the same session
This lens is useful for pinpointing performance differences between initial and follow-up navigations. It answers a critical question: Are your first impressions holding users back?
Only pageviews that occurred during the selected period and device type are included.
Healthy TTFB by pageview type sample
Should you worry
A healthy TTFB by pageview type lens shows both bars in green. If First in session is a little slower, that’s expected. But as long as you’re under the 800ms threshold, you’re in a good place.
The smaller the gap between the two, the more consistent your back-end performance feels to users.
Unhealthy TTFB by pageview type sample
In the example below, First in session is not only slower — it’s unhealthy. This means that users entering the site are starting off with sluggish performance, increasing the chances of:
Higher bounce rates
Drop-offs before even rendering starts
Poor Core Web Vitals and SEO impact
Resolving unhealthy TTFB by pageview type
Go-to action plan to resolve an unhealthy TTFB by pageview type:
Ask Uxi to analyze your TTFB by pageview type values and suggest improvements.
Use Filters to zoom in on slow First in session navigations — where are they coming from, and what pages are affected?
Simulate TTFB of the suspected lens to see if fixing it will resolve the TTFB by pageview type. If yes, this is where the resolution focus should be.
Use an automated optimization tool like Navigation AI to improve your TTFB by pageview type values.
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.