We should discuss what we should do with https://performance.wikimedia.org
* Why
* Who is the audience?
* Content?
### Why?
I kind of like the idea that this is the starting point for performance. Going to performance.wikimedia.org should give you an of overview of the performance of Wikipedia and make it easy to dig deeper. I think we also should give the user an overview what we are measuring and why.
### Who is the audience?
Performance interested users and web engineers.
### Action items
* [ ] Make front-end as performant as possible (skip Bootstrap CSS, inline CSS, defer/async js where possible)
* [ ] List the latest blog posts from the performance team. (Create sidebar?)
* [ ] Add descriptions to coal graphs. T97088
* [ ] Display large number next to graph (like <https://status.github.com/>)
### Ideas for later
- Coal graphs like today and make it easier to dig deeper into the data
- Iframe graphs from Grafana? The Grafana graphs is better in the way that we compare metrics that are 7 days back, so it is easier to understand if we get an regression or not.
- Collect alert JSONs from Grafana and show alert status
- Describe each tool we use, not only link to them.
- How can you help out (link to Phabricator and what we do and how you can help).