As mentioned by @ori during out last meeting, we should come up with the main metrics we aim to move the needle on as a team and decide what form it should take in terms of dashboard.
Some ideas we might want to explore further. This is my take on it, and can be subject to further debating:
- Maybe all our core performance metrics should be expressed in terms of end-user experience. I.e. "as a reader how long does it take for me to be able to view an article". This pretty much maps to firstPaint 1-to-1. If we go down this road, we should always remember to start the thinking from the UX, and not start from the technical data. This vast amount of data we have can trick us into tracking the wrong thing. Another UX metric idea that came up was "as an editor, how long does it take for my contribution to be visible by everyone". We should probably brainstorm more of those in this task.
- Time to edit - we have it today in our RUM metrics: https://grafana.wikimedia.org/dashboard/db/visualeditor-load-save?refresh=5m&panelId=14&fullscreen&orgId=1 and we can highlight it more. We could also think about if there's a way to get the same information for WebPageTest (would it help us?).