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

UserFlow - show duration between timespan start and finish #15087

Open
doteric opened this issue May 17, 2023 · 4 comments
Open

UserFlow - show duration between timespan start and finish #15087

doteric opened this issue May 17, 2023 · 4 comments
Assignees

Comments

@doteric
Copy link
Contributor

doteric commented May 17, 2023

Feature request summary

I would like the lighthouse User Flow HTML report to contain the duration between the timespan start and finish alongside the metrics. Currently there is only TBT, CLS and INP displayed in the timespan report meanwhile a duration would be useful especially that timespans are often used to calculate the time to get from one place on the website to a different one.
What do you think of such addition?

If you would like this feature then I think I would be able to contribute with the addition.

What is the motivation or use case for changing this?
More informative metrics on the LH User Flow Report.

How is this beneficial to Lighthouse?
A useful metric on the timespan report for LH User Flow Report.

@adamraine
Copy link
Member

I don't no if this fits as an actual metric, but this is certainly diagnostic information that we can provide.

@doteric
Copy link
Contributor Author

doteric commented May 17, 2023

Hey @adamraine 👋
Sure, it's a good start. Would it be visible somewhere in the html report btw?
Tracking the time between certain steps seem like an essential think for the user journey/flow, what do you think?

@adamraine
Copy link
Member

Would it be visible somewhere in the html report btw?

Yes

Tracking the time between certain steps seem like an essential think for the user journey/flow, what do you think?

I do think it's useful, I just don't think it makes sense to work it into the score. I was imagining something at the bottom of the report in the run info section.

@doteric
Copy link
Contributor Author

doteric commented May 19, 2023

That would be totally fine. I also wouldn't put it in the scoring, instead somewhere apart from the scores that is easily accessible would be preferred. Initially it could be enabled/disabled on demand maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants