Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core Web Vitals INP - Immediate Feedback - loading spinners / progress bar / acknowledgement pop-ups etc #2583

Open
patrjst opened this issue Jan 29, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@patrjst
Copy link

patrjst commented Jan 29, 2024

Is your feature request related to a problem? Please describe.
I'm trying to identify optimization opportunities for a web application using DataDog RUM to be ready for INP in 2024. Experimenting on a staging environment with many running testflows it looks like it does not have any visible effect on the INP calculation if I try to mitigate long running tasks for interactions by providing immediate feedback to the user. What I tried:

  • loading spinner covering the whole viewport
  • loading spinner next to single controls that might take long

E.g. in this staging environment I was able to affect the RUM metrics by artificially increasing response time for a single interaction (far more than 200ms, tested with 500ms, 1s, 5s). Expectation was, that this, as one of the overall slowest interactions but still part of quite many user flows, must affect the INP calculation. And it does. The INP metrics just incease in my DataDog dashboard. I can also verify this by manually clicking through userflows containing this interaction in the Chrome Web Vitals extension. But when I add a Loading spinner - Web Vitals Extension in Chrome shows improved times for the interaction and INP calculation, while Datadog still shows a bad INP (due to artificially extended loading times for this interaction).

For the the RUM script I'm using v5.8.0

I'm aware that the overall INP calculation depends on all the user flows and might be affected by the interactions with worst performance, even if all other interactions are quite ok. This is why I tried to verify the negative case, having one very long interaction in place that is affecting the measurement negatively.

Describe the solution you'd like
The INP calculation should take into account the usage of "immediate feedback" provided to a user, so that long loading interactions can be mitigated by taking measurements like progress bars, loading spinners, pop-ups, to cover the same behavior like tools as Web Vitals extension is showing, and probably Google will apply while collecting performance profiles as field data.

Describe alternatives you've considered
A clear statement about DataDog RUM INP metrics VS Google INP data collection, would be beneficial.

@patrjst patrjst added the enhancement New feature or request label Jan 29, 2024
@bcaudan
Copy link
Contributor

bcaudan commented Feb 1, 2024

Hi @patrjst,

Our INP implementation aims to be as close as possible as the google one.
In order to dig deeper into that, could you share a case where our implementation behaves differently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants