= Background =
We need to find a way to make it easier for people writing articles to know if a page is fast or not and if they can do anything about it to make it faster. Today we have **mw.loader.inspect()** which is super cool and we could add some more help.
= How =
We can collect internal data like we do today with mw.loader.inspect() and external like Navigation Timing, Resource Timing and User Timing API. We should use both. There's two key issues:
* Only signal real problems
* Make the metrics understandable for everyone (like ranking from 1-5 or red/yellow/green).
We could push the code for this either by load it on demand when the user wants it or package it as bookmarklet or make a browser plugin.
A couple of things up for discussion:
* What metrics do we include?
* Pro and cons on how to distribute the code
* If we do bookmarklet/plugin would it be something that could be used for other web sites?
* Limits/budgets per metric
And some projects that can inspire us:
* Khalid Lafi: http://wpotools.github.io/perfBar/
* Mark Zeman: https://github.com/zeman/perfmap (this is really visual love it)
* DOM monster - https://github.com/madrobby/dom-monster (this classic could help us with DOM metrics)
Could it be that we could use on of these for the external metrics?