> Bad because many of Lighthouses best practices aren't always applicable It's tough to create an auditing tool that caters to the web at large. See my other c

> Bad because many of Lighthouses best practices aren't always applicable It's tough to create an auditing tool that caters to the web at large. See my other comment in this thread: https://news.ycombinator.com/item?id=18442686 https://news.ycombinator.com/item?id=18442686 > This all also overlooks the value that something like the Browser's User Timings provides... which Lighthouse doesn't surface up. Lighthouse does surface up this info in the "User Timing Marks and Measures" audit: https://developers.google.com/web/tools/lighthouse/audits/user-timing https://developers.google.com/web/tools/lighthouse/audits/us... But I'm getting the impression that you want Lighthouse to surface up this information in a different way. Please feel free to elaborate. Disclaimer: I write the docs for Lighthouse. I'm speaking from my general knowledge of the project but haven't vetted these comments with my team. So consider all comments my own.