-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Metrics: rename "First Interactive" and "Time To Consistently Interactive" #3655
Comments
sg thx for filing this. Over on the "Loading Metric Prioritization" doc, Patrick and I wanted to bikeshed "first idle" some more. :) Also some potential other changes given this new framing:
We will be keeping perceptual speed index regardless, especially given that FMP is falling out of favor and no other metric tracks a midpoint like that. |
Np. Just commented there :) I'd be interested in the idea of adding FCP and FP - were you thinking weighting for perf might factor TTI more heavily than it does today? or..smth else? :) |
If we're going to adjust weighting, let's check in with xPA folks to make sure they're aware of the changes and adjustments in scoring that will happen. I'm going to shoot an email to some folks, but would be good to give others a heads up :) |
Yah. TBH FMP isn't useful when you've got FCP.
From what I've seen, the distinction between the two causes nothing but difficulty for people to understand. These names (while they may receive a tonne more discussion) SGTM. |
Totally agree on reducing the confusion here and I like the overall shift in loading metric story 👍 @benschwarz care to elaborate a bit more on...
I've frequently found FCP to be too early to express when useful content showed up and consider it as a useful addition to FP/FCP duo. I'm curious what your experience has been. |
little update here: there was consensus renaming FI to "First CPU Idle" |
First CPU idle sgtm. With that locked in, what do you see as the timeline for us making these changes in metric renaming?
|
this has been fixed in v3 :) |
There has been interest in reducing the developer confusion introduced by having two interactivity metrics. The latest thinking has been:
At CDS, we shopped this idea around with a few developers. Main feedback was that the TTCI ➡️ TTI change sounds reasonable. The second (FI) was consistently followed up by questions asking for clarity e.g "...is this main thread idle we're talking about?" "..CPU idle?" etc.
I believe there may be a desire to keep discussing the second point here, but filed an issue to track the update anyway.
cc @paulirish @patrickhulce @brendankenny
The text was updated successfully, but these errors were encountered: