This may be controversial but I think this has the potential to be a brilliant metric because it measures some part of web UX that’s often neglected. It’s time consuming to make every single interaction display some sort of loading message but it really helps make the site feel responsive.
As long as they avoid the pattern of adding a global loading spinner that covers the whole screen. That’s just the worst possible loading screen. I suppose it would still pass this metric.
Also I’m not sure if I totally understand the metric - I think it’s simply when the next frame is rendered post interaction, which should easily be under 200ms unless you’re
1. doing some insane amount of client side computation
2. talking over the network far away from your service or your API call is slow / massive
and both of these are mitigated by having any loading indication so I don’t understand how this metric will be difficult to fix.
As long as they avoid the pattern of adding a global loading spinner that covers the whole screen. That’s just the worst possible loading screen. I suppose it would still pass this metric.
Also I’m not sure if I totally understand the metric - I think it’s simply when the next frame is rendered post interaction, which should easily be under 200ms unless you’re
1. doing some insane amount of client side computation
2. talking over the network far away from your service or your API call is slow / massive
and both of these are mitigated by having any loading indication so I don’t understand how this metric will be difficult to fix.