Open johnbillion opened 6 years ago
Really the only thing I can think of that would make sense, is the amount of time that QM (collectors and output) adds to the document's response; would be helpful for gaining a more accurate understanding of QM's impact when evaluating a page's performance.
Perhaps QM could use #309 to time itself?
I didn't find it very useful
Could this be useful to measure/debug the time each plugin is taking to load? (or there another way to do that already?)
or there another way to do that already?
You could use QM's timing functions on plugin_loaded
and plugins_loaded
actions.
The Server Timing API will appear in Chrome stable soon.
I've already messed around with an implementation in QM but I didn't find it very useful. Maybe it needs some more thought.