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

Better visualization of Lantern simulation (filmstrip & net requests) #5844

Open
Munter opened this issue Aug 16, 2018 · 2 comments
Open

Better visualization of Lantern simulation (filmstrip & net requests) #5844

Munter opened this issue Aug 16, 2018 · 2 comments

Comments

@Munter
Copy link
Contributor

Munter commented Aug 16, 2018

Feature request summary

In the new lantern simulation it seems simulated timings aren't applied to numbers inside different audits, like network-requests or screenshot-thumbnails, making visualizations of these audits incompatible with the reported perceived performance metrics

What is the motivation or use case for changing this?

Visualizations are helpful in drilling down into reasons for performance issues. Having a report of slow perceived performance metrics without being able to correlate them with a network waterfall or screenshots of rendering over time makes it hard to debug issues

How is this beneficial to Ligthhouse?

The lighthouse output could be used to drive more detailed reports than the one that is currently produced by the html reporter

@patrickhulce
Copy link
Collaborator

I like this @Munter thanks for filing! We've been working on pieces of this. There's somewhat of a debug option currently if you're running with the CLI, use the --save-assets flag to dump traces and set the env variable LANTERN_DEBUG=true then you'll get traces with the lantern timings for each metric (at which point you can view the waterfall by opening it in DevTools performance panel).

Agreed this hardly a first class visualization, but it's progress so stay tuned :)

@paulirish paulirish changed the title Lantern simulation in audit details Aug 27, 2018
@martinschierle
Copy link

+1 for getting this fixed, I also rely on the resource and screenshot timings for my project (see g.co/perfgame)

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