-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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(metrics): add lantern speed index #4695
Conversation
316ff44
to
923f05a
Compare
923f05a
to
a1b18b1
Compare
OK folks FYI I've updated this and it's ready for review! |
a1b18b1
to
70b534c
Compare
friendly reminder here that I/O-Expedite policy has this currently auto-merging at 2pm today folks ;) |
* @param {number} fcpTimeInMs | ||
* @return {number} | ||
*/ | ||
static computeLayoutBasedSpeedIndex(nodeTiming, fcpTimeInMs) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add some documentation that explains the approach here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 done
7648797
to
cf0417c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM2
closes #4639
blocked from merging on #4966
predicts speed index by using the real speed index as the optimistic estimate and a layout-based speed index approximation from the pessimistic TTI graph as the pessimistic estimate
accuracy is decent. probably wouldn't recommend making it a headline metric as-is, but correlates slightly better than FCP (less than TTI/TTFCPUI)
spearman's rho ~.78, MAPE ~47%