Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Clarification about some metrics #1229
recently a bunch of questions came up about some metrics that I wasn't able to explain from any documentation or code, so I wanted to ask them here.
I'd be happy to document these things anywhere. Which is the desired format? Google Sites (is it even possible to contribute there?) or markdown in this repo?
2 - Missing FirstInteractive and ConsistentlyInteractive are usually when there isn't a 5-second window of idle in the main thread before the recording stopped so neither could be calculated. LastInteractive is the last time the thread went idle for > 50ms and is the earliest that either of the interactive metrics could possibly be assuming the main thread would have stayed idle for 5 seconds after the test stopped. TTIMeasurementEnd is basically the end time of the timeline data that we have recorded for calculating the interactive metrics.
The WPT UI will show "> xxx" when FirstInteractive isn't available and will use LastInteractive in it's place basically saying that it is at least that long.
Relative to lighthouse:
i hope that my question fits this issue.
Suddenly some of our WebPagetest runs that are trigged via the API are missing the Interactive metrics like
Is there maybe a setting that we could apply to increase the wait time?
I have some further questions about interactive metrics in WPT:
Wouldn't it make sense to use the same names as in lighthouse to avoid confusion (at least in the GUI)?
Sometimes, in addition to
Thanks in advance, Nils