Skip to main content

INP by HTTP status code

INP by HTTP status code without noise

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


What is INP by tab navigations

INP by tab navigations shows how Interaction to Next Paint (INP) varies depending on the HTTP status code the page received when it loaded. These codes — like 200 OK, 301 Moved Permanently, or 404 Not Found — can influence how fast or responsive the page feels to user input.

This lens helps you detect whether certain types of server responses correlate with slower or more laggy interaction performance, especially on error or redirected content.


Healthy INP by tab navigations sample

​
Should you worry

A healthy INP by HTTP status code lens shows:

  • Most INP values are fast and tied to 200 status codes — your core, fully functional pages

  • Minimal to no interaction delays on fallback or alternate responses (3xx, 4xx)

  • Predictable responsiveness even on custom error or redirect pages

This suggests your interactive performance is consistent, regardless of how the user ends up on the page.

Unhealthy INP by tab navigations sample

An unhealthy profile may reveal:

  • Long input delays on 404 or 500 pages, often due to heavy fallback logic or missing JS

  • Poor responsiveness on redirected pages (301 or 302) where hydration fails post-redirect

  • Unexpected user interaction lag caused by edge-case templates or non-primary content paths

These issues tend to frustrate users trying to recover from navigation errors or explore deeper pages.

Resolving unhealthy INP by tab navigations

Go-to action plan to resolve an unhealthy INP by tab navigations:

  1. Ask Uxi to analyze your INP by tab navigations values and suggest improvements.
    ​

  2. Use Filters to focus on sessions with non-200 codes and compare them against the core interaction baseline.
    ​

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

  4. Use an automated INP optimization tool like INProve to improve your INP by tab navigations values.
    ​

  5. 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.
​

Try it in Uxify Experience
Related Articles
LCP by HTTP status code
TTFB by HTTP status code
INP by element
CLS by HTTP status code
PLS by HTTP status code
Did this answer your question?