interaction-to-next-paint

How can the <html> be the INP penalty element?

I have set a very low internet speed, to 20kbps.

And when I try to click on a <i> element on the page, due to the low speed, the js event handler of that <i> is not loaded yet (on the bottom of the page). It has caused an INP. However, the target in INP report is not the <i> element but the html.

How can it be like this? This is local data and in my RUM I saw a lot of html as the element from my real users. How can I find the exact element that the users failed to click?

Thanks

enter image description here

Solution

  • Here's another example of html and body elements showing up in INP attribution data:

    enter image description here

    This is totally normal and it can happen when a user interacts with no particular UI elements on the page. For example, if they click on the background or use the keyboard when nothing is focused.

    But if they click on a part of the UI, I'd expect that to be the event target. Event listeners don't need to be attached for the target to be set, or for slow INP to occur for that matter. So I'm not sure what's happening in your case but to answer the general question, it's not unexpected for the html element to appear in your attribution data.