Interaction to Next Paint (INP)

Interaction to Next Paint (INP) is one of the three Core Web Vitals and a key measure of how responsive your site feels during user interaction. At Uxify, we use INP as a checkpoint for diagnosing input responsiveness issues that frustrate users - especially on slower devices or heavier pages.
​

INP measures the delay between a user interaction (like clicking a button or tapping a link) and the next time the screen visibly updates in response. Unlike earlier responsiveness metrics, INP considers the worst interactions rather than just the average - making it a more reliable indicator of how users truly experience responsiveness.
​
​

To deliver a smooth and interactive experience, the 75th percentile (P75) of Interaction to Next Paint (INP) should be under 200 milliseconds. This means 75% of your users get near-instant feedback from the UI. Here’s how Uxify categorizes INP performance:

Two words: users and Google. Let’s start with your users. If clicking a button or opening a menu takes forever to show a response, the experience instantly feels broken or sluggish. A fast INP helps create a fluid, satisfying interface that users love to engage with.
​

Then there's Google. INP is now a part of the Core Web Vitals that feed into your site’s performance score and search visibility. Sites that feel laggy under load, especially on mobile, can take a hit in rankings. A better INP isn’t just about speed - it’s about trust, usability, and retention.

Real User INP is captured from every user interaction on your site - clicks, taps, keyboard presses - and reflects the delay between a user’s input and the next paint. Uxify tracks this in full fidelity, across all devices, regions, and sessions, giving you a complete and unsampled picture of interaction responsiveness. This data is crucial for understanding where your users experience sluggishness, whether it's due to heavy JavaScript execution, long tasks, or poor main thread availability. With Real User INP, you can surface real bottlenecks in responsiveness that directly affect engagement and usability.

This filter slices your Real User INP data to include only the URLs recognized by Google’s Chrome UX Report. It’s the perfect view when you need to validate or explain CrUX results using your own high-resolution data. If you’ve improved responsiveness across your site but aren’t seeing gains in Search Console, this filter helps answer why. It bridges the gap between what your users are experiencing and what Google is reporting - using your data, focused on CrUX-critical pages.

Google CrUX INP is based on anonymized interaction data collected from Chrome users and published weekly. It’s sampled, restricted to high-traffic URLs, and aggregated - but it’s what Google uses for Core Web Vitals scoring and SEO signals. Since INP has officially replaced FID as the responsiveness metric in Core Web Vitals, monitoring your CrUX INP is now essential. It tells you whether Google sees your site as responsive - and if not, which URLs are holding you back from passing Core Web Vitals.

Here are three of the most common and actionable reasons we see for high CLS in Uxify Experience:

With over 80 INP lenses in Uxify Experience, it’s easy to pinpoint what’s dragging down your site’s responsiveness. You can find the worst offending interactions in one dashboard view. Then use INProve to offload, prioritize, or defer work intelligently.