What is INP by pageview type
INP by pageview type shows how the Interaction to Next Paint (INP) performance for two key moments in a user session:
First in session pageviews – the very first pageview in a session
Subsequent in session pageviews – any pageviews that follow during that session
This breakdown helps you understand whether users experience responsive pages right from the start — or only after the session gets rolling.
Healthy INP by pageview type sample
Should you worry
A healthy INP by pageview type breakdown shows both bars well below the 200ms threshold. It's okay for First in session to be slightly slower, but you want to see both in green and ideally below 100ms for a truly responsive feel.
Unhealthy INP by pageview type sample
In this case, First in session INP is the slowest and most frequent pageview type. That means users are likely interacting with unresponsive elements before hydration is done — and it leaves a bad first impression.
You may also see degraded INP on Subsequent pageviews if:
You’re loading new JavaScript or layouts between routes
Scripts rehydrate full layouts instead of reusing cached elements
Background activity (like analytics or ads) hogs the main thread
Resolving unhealthy INP by pageview type
Go-to action plan to resolve an unhealthy INP by pageview type:
Ask Uxi to analyze your INP by pageview type values and suggest improvements.
Use Filters to isolate slow interactions on First in session vs. Subsequent views
Simulate INP of the suspected breakdown to see if fixing it will resolve the INP by pageview type. If yes, this is where the resolution focus should be.
Use an automated INP optimization tool like INProve to improve your INP by pageview type values.
Once you’ve improved INP, 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.