You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 :)
Feature request summary
In the new lantern simulation it seems simulated timings aren't applied to numbers inside different audits, like
network-requests
orscreenshot-thumbnails
, making visualizations of these audits incompatible with the reported perceived performance metricsWhat 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
The text was updated successfully, but these errors were encountered: