Live data from Hacker News

Interaction to Next Paint (INP)

web.dev

1–10 of 77 posts

Re: Interaction to Next Paint (INP)

#3

At first glance, 200ms INP is a pretty high latency for a "good" rating. As a comparison, I believe 200ms is an average https roundtrip. I'd expect most interactions to be much lower than that.

I guess it depends on how your interactions are implemented. If it’s an SPA then 200ms is absurdly slow. But if it’s a more traditional form submit or something then it would take a lot longer for your next set of pixels to comes through.

Re: Interaction to Next Paint (INP)

#5

At first glance, 200ms INP is a pretty high latency for a "good" rating. As a comparison, I believe 200ms is an average https roundtrip. I'd expect most interactions to be much lower than that.

That was my first impression too but then I thought about what it’s actually measuring: page responsiveness, not animation jank.

I’m not going to expect a 16ms response or anything for every animation but much slower & you see jank.

For page interactivity though? 0.2s is pretty damn fast. Human response time is 0.15-0.25s

So it’s pretty reasonable

Re: Interaction to Next Paint (INP)

#7
I'm lacking lots of context obviously but: What good is a sophisticated metric when the pages they index are mostly blogspam SO clones etc? I'm not interested in the "most responsive" SO clone. Seems out of touch with what Google search is struggling with these days.

Re: Interaction to Next Paint (INP)

#9

The real metric: INP with ad blocking enabled. Example: NYTimes.com on Mobile Safari with AdGuard. 18 seconds. Google is being really disingenuous with its so called metrics. A stroke of the pen could make INP 200ms across the top 500 sites.

That's all Google cares about. How to invade our privacy and force us to see more ads?

Re: Interaction to Next Paint (INP)

#10
We started seeing reports about it in GSC early July, when over a single day all our scores turned to crap with no explanation.

We are in the yellow, but the biggest culprits for blocking time are...Google Tag Manager, GAds (and Ganalytics where we still have it). So yeah, thanks Google, can't wait to lose on SEO due to your own products. And also, thanks for releasing this without the proper analysis tooling. (https://web.dev/debug-performance-in-the-field/#inp : this is not tooling, this is undue burden on developers. Making people bundle an extra ["light" library](https://www.npmjs.com/package/web-vitals) with their clients, forcing them to build their own analytics servers to understand what web-vitals complains about...or is often wrong about)

Post reply on HN