We're adding more data to the server side response on Special:Homepage, for example, rEGREc3fc552b9195: NewImpact: Export user impact data from server-side added the user impact data blob to the data we export for use with mw.config on the client-side. We'd like to keep an eye on our page size to make sure we are doing anything too egregious in transfer sizes.
From @Krinkle in IRC:
Krinkle> kostajh: note that client side, you have access to responseStart (latency plus receipt of first byte), responseEnd (download time of HTML), and transferSize, and eg firstPaint. That's transfer size as transferred incl any headers and use of gzip. That would be more representative. The timing values might on their own be more valuable though as that's what people perceive.
We already have some server-side rendering times in Grafana, but we could supplement those with client-side metrics as well.
So in sum, in this task we should code to instrument, and panels in Grafana, for the following:
- Special:Homepage response size on the client-side. I don't think this needs to vary by wiki.
- Special:Homepage responseStart - responseEnd times. This might be interesting to vary by wiki, or by geographical country, but we could probably just start with a generic measurement across all wikis and locations for now.