INP
The INP page of RUM Monitoring shows how fast pages react to taps, clicks and key presses, which phase is slow and which scripts cause it.
The INP page of RUM Monitoring shows how quickly your pages react when real visitors tap, click or press a key. It also shows which phase of the reaction is slow and which scripts cause the delay.
What INP means
INP (Interaction to Next Paint) measures how quickly the page reacts when a visitor taps, clicks or presses a key. It reflects the slowest reactions during the visit. INP is one of Google's three Core Web Vitals.
A slow INP makes the page feel broken. Visitors tap again, or they leave. INP has a value only for visits where the visitor did something on the page.
INP thresholds
| Band | INP value |
|---|---|
| Good | 200 ms or less |
| Needs improvement | 500 ms or less |
| Poor | More than 500 ms |
The headline value is the value of a typical visit: 3 out of 4 page loads were this fast or faster. Google passes INP when at least 75% of visits are Good. See Metrics and thresholds.
Before you start
- RUM Monitoring needs the RUM script on your pages. See Install the RUM script.
- In the sidebar, open Web performance > RUM Monitoring > INP.
- Select Phone or Desktop in the filter dock. Every card on the INP page shows the selected device only.
You can also filter by date, URL Path, Country and Browser, and compare with an earlier period. See Filters and the device.
The INP verdict
The verdict is one sentence at the top of the INP page. It shows only when it says something new:
- "On Phone, INP fails" when the typical INP is not Good. If the value is only a little over the limit, it adds "Just over the limit."
- "On Phone, INP passes but is close to the limit" when the typical INP is Good, but within 10% of 200 ms.
- "On Phone, INP got 20% slower" or "got 20% better" when compare is on and INP changed by 15% or more.
The verdict needs 30 visits or more. If INP passes with room to spare, the INP page shows no verdict.
Site Health Monitoring banner
If Site Health Monitoring found issues or opportunities about the Core Web Vitals of the selected device, a banner shows their number. Click Open in Site Health Monitoring to see them. See Site Health Monitoring.
Interaction to Next Paint card
The Interaction to Next Paint on Phone card (or on Desktop) has two tiles and one chart. Click a tile to show its chart.
- Interaction to Next Paint: the typical INP in the period, colored by its band.
- Good visits: the share of visits with a Good INP. The tile is green at 75% or more, orange at 50% or more, and red below 50%.
A tile from fewer than 30 visits is gray, with a note such as Only 12 visits. A tile without data shows Not measured for this period.
The INP chart
For Interaction to Next Paint, the chart shows the typical INP over time. Two lines mark the Good limit (200 ms) and the Poor limit (500 ms). With compare on, a dashed line shows the earlier period.
For Good visits, the chart shows the share of Good, Needs improvement and Poor visits over time, stacked to 100%. A line marks Passes at 75%, where Google passes INP.
Use the Hour, Day, Week or Month control to group the chart. A note on a day of the chart tells you that VitalSentinel changed what RUM Monitoring measures, or calculated stored data again, on that day.
Google and your own visitors
The Google and your own visitors card compares your INP with the INP that Google publishes for your site. It has four tiles:
| Tile | What it covers |
|---|---|
| Google, Phone and Google, Desktop | Chrome visits to the whole site, last 28 days |
| Your visitors, Phone and Your visitors, Desktop | All visits in the selected period and filters |
Google rates your site from Chrome visits only. RUM Monitoring measures all of your visitors, so the two can differ. A big gap means that Chrome users have a different experience than other visitors.
Click Open CrUX Monitoring to see Google's data. If Google has not published data for your site, the card says "Google has not published data for this site yet". See CrUX Monitoring.
If CrUX Monitoring is not set up for the domain, the card shows Set up CrUX Monitoring instead. A tile without a figure says "Google has not published enough visits for this device yet." or "Too few visits measured this yet."
Where it is slow
The Where it is slow card lists your pages for the selected device. By default, the pages with the most visits that were not Good come first.
| Column | What it shows |
|---|---|
| Page | The page address. The menu opens the page in other modules. |
| Visits | The visits to the page in the period |
| Google clicks | The clicks from Google web search, from Google Search Console |
| INP | The typical INP of the page, with its change when compare is on |
| Good visits | The share of visits with a Good INP |
| Visits affected | The visits on the page that had an INP above the Good limit |
Click a header to sort. A page with fewer than 30 visits shows a dash in INP. Owners and admins can click Watch in Page Monitoring on a row. Fix the first page in the list first.
Countries
The Countries card shows a world map for the selected device. Each country has the color of its typical INP: Good, Needs improvement or Poor. Low sample means too few visits to rate, and No data means no visits.
Hover a country to see its visits, its figures, the change from the earlier period and the visits affected. A slow country can point to slower devices in that country.
Where the time goes
The Where the time goes on Phone card (or on Desktop) splits INP into three phases. The chart shows the average time in each phase over time, stacked. The three phases add up to the total time of an interaction.
| Phase | What it is |
|---|---|
| Input delay | The wait before the page starts to handle the tap, click or key press |
| Processing time | How long the code of the page takes to run after the tap, click or key press |
| Presentation delay | The gap after the code finishes before the screen updates |
Hover a point to see each phase and the total. With compare on, a line shows the total of the earlier period. If one phase has no reading for a point, the chart shows a gap.
Shorten the longest phase first.
Scripts that slowed interactions
The Scripts that slowed interactions card lists the scripts that were running when interactions were slow, the most frequent first. It shows the selected device only.
| Column | What it shows |
|---|---|
| Script URL | The full address of the script, with a Your site or Third party chip |
| Count | How often the script was running during a slow interaction |
| INP | The typical INP of those interactions, with its change when compare is on |
A Third party script comes from another site, for example a chat widget, an ad or a tag. You can often remove or delay these scripts. The table shows 20 scripts on each page of results.
If interactions were fast, the card can be empty: "No script data available". The browser reports scripts only when a long task blocks the page.
How to improve INP
Use the Where the time goes card to find the slow phase, then act on it:
- Input delay is long: other scripts keep the browser busy. Remove or delay third-party scripts, and split long tasks into smaller ones.
- Processing time is long: the code that answers the tap is slow. Make the event handlers do less, and move heavy work after the screen update.
- Presentation delay is long: the screen update is large. Keep the page smaller, and change fewer elements at a time.
Check the Scripts that slowed interactions card for the scripts to work on first.
Troubleshooting
Why do fewer visits measure INP than LCP?
INP has a value only when the visitor taps, clicks or presses a key. Visits where the visitor only reads or scrolls have no INP. So the INP tiles and the INP column can rest on fewer visits than LCP.
Why does the INP page say "No Interaction to Next Paint data for this period"?
There were no visits on the selected device in these dates and filters. Select the other device in the dock, select a longer date range, or remove a filter.
Why is the Scripts that slowed interactions card empty?
The browser reports a script only when a long task blocks the page during an interaction. If interactions were fast, there is no script to show. This is a good sign.
Why is a script marked Third party?
The address of the script is on another host than your domain. VitalSentinel marks scripts from your own domain and its subdomains as Your site.
Related
- Overview - all Core Web Vitals, filters and page-view limits
- Page Views - the INP phases and element of one visit
- Engagement - whether slow pages get more rage clicks
- Metrics and thresholds - the limits of every metric
