Did people voting up this comment just not read the linked docs, or do you maybe not have the context to understand what this library does?
It instruments your code so you can get call stack traces with timing information associated. Unless your calls into the DOM are blocking, they aren't going to show up there (that's what the browser dev tools are for). There's a reason that the only HTML element explicitly mentioned in the docs is the canvas element. It even says, explicitly, "Though it's certainly useful to see the ways your application is interacting with the browser and vice versa, often there is much more work occurring within your call trees than not."
This has almost nothing to do with HTML. It's a profiling tool for a garbage-collected scripting language, and it looks more than a little useful.