What is INP by redirects
INP by redirects tracks how Interaction to Next Paint (INP) is impacted by whether the session began with a redirect — such as a marketing tracker URL, a switch from HTTP to HTTPS, or a domain redirect (like from example.com to www.example.com).
While redirects are often considered a loading concern, they can subtly influence interactivity as well. Here’s how:
Redirected journeys may hit slower infrastructure or include heavier client-side scripts.
Users coming from redirected sources (like email or ad campaigns) may land on pages with extra tracking or personalization logic, which slows input handling.
Some redirect chains impact INP indirectly — by delaying hydration or frontloading background tasks.
Healthy INP by redirects sample
Should you worry
If both "Redirect" and "No redirect" sessions show fast INP (green), you’re in the clear.
That means:
Redirected entry points aren’t introducing interactivity lag.
Any additional logic triggered by redirects (like analytics or personalization) is well-optimized.
Your page stays responsive regardless of how users arrived.
You might still see some variance, especially on slower devices, but as long as both groups stay green, there’s no red flag.
Unhealthy INP by redirects sample
Slower INP on redirected visits often signals:
Redirect targets are overloaded with client-side logic (e.g., personalization, A/B testing).
Extra tracking scripts delay interactivity on redirected paths.
Poor cache policies or hydration logic make redirected visits more JS-heavy.
Redirects are common on mobile or campaign traffic, where performance matters most — amplifying the pain.
If redirected users consistently experience slower taps, clicks, or hovers, you risk higher drop-offs on your most valuable acquisition channels.
Resolving unhealthy INP by redirects
Go-to action plan to resolve an unhealthy INP by redirects:
Ask Uxi to analyze your INP by redirects values and suggest improvements.
Filter down to sessions with high INP and a redirect, then inspect other lenses for bottlenecks.
Simulate INP of the suspected lens to see if fixing it will resolve the INP by redirects. If yes, this is where the resolution focus should be.
Use an automated INP optimization tool like INProve to improve your INP by redirects 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.