Chrome DevToolsVerified account

agreed. I have a #devtools talk that I'm making as accessible, comestible and inoffensive as possible for the everyday dev. But it should be something that stays open at all times. Browsers + devtools are like wine & cheese - perfect complement.

The Audits panel is one approach we're approaching as the gateway to performance analysis

If you have any ideas on how to fundamentally re-approach we'd love to hear 'em, and would be happy to give you ample credit

That sounds like a good thing to do, but my hunch is that many devs won't explore enough to find it. I know real estate and attention are expensive, but I'd love to see more flags surfaced in places all devs are already looking: on the page or in the console.

For example, in Chrome devtools, some of the warnings that show up when verbose mode is activated are really great. But, I've only met a handful of devs who actually know about this feature.

What if there was a threshold where these verbose flags spilled over into the non-verbose console, with information about how to see more stuff like that?

Or what if there was a setting that allowed me to say "I'm developing on this URL, so show me helpful stuff all the time"? Similar to the ideas here: https://github.com/blog/1252-how-we-keep-github-fast …

Also, one of the things I hear most frequently is that people don't know how to interpret the information they have. e.g. what is fast enough or what is too slow? More ways to flag these things and help with the interpretation would be really great.