What is INP by data save mode
INP by data save mode shows the Interaction to Next Paint (INP) segmented by whether users have enabled their browser or device’s Data Save mode.
This lens helps identify whether input responsiveness is impacted when users try to conserve data — especially relevant for mobile users on limited plans or slower networks.
Healthy INP by data save mode sample
Should you worry
In a healthy setup:
INP is low for both enabled and disabled users
Data Saver users may even benefit slightly from reduced layout shifts or animation complexity
The experience remains consistently responsive across the board
This suggests your site degrades gracefully under lean conditions — a sign of robust and flexible interaction handling.
Unhealthy INP by data save mode sample
If Data Saver users experience significantly worse INP, it often means:
Critical scripts are deprioritized or stripped, delaying input response
Event handlers rely on heavy dependencies or hydrate late
Input delays stack up due to constrained CPU or stripped assets
This can feel especially frustrating for users actively trying to conserve data — often those most sensitive to delays.
Resolving unhealthy INP by data save mode
Go-to action plan to resolve an unhealthy INP by data save mode:
Ask Uxi to analyze your INP by data save mode values and suggest improvements.
Use Filters to isolate enabled Data Saver sessions, then check other INP lenses.
Simulate INP of the suspected lens to see if fixing it will resolve the INP by data save mode. If yes, this is where the resolution focus should be.
Use an automated INP optimization tool like INProve to improve your INP by data save mode 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.