Nice! Surprised how much I like seeing a simple tree view for HTML elements. I can imagine using this on front-end dev job applicants, replacing my current view

Nice! Surprised how much I like seeing a simple tree view for HTML elements. I can imagine using this on front-end dev job applicants, replacing my current view source + build quick mental model of how they approach structure. Don't see using it for evaluating performance, as it doesn't indicate the expensive paints etc (and nor should it) - problematic page weight would reveal itself in more direct diagnostics (pagespeed insight, etc). A view like this might be interesting in a larger tool, but no need to expand this into one. It would be nice if #id values were printed, as their prevalence and values can also tell you a lot about how a page is constructed. Printing classes would get excessive quickly.