Reading/Web/Lazy loading of images and references on Russian Wikipedia

arge sized wiki, was the third and final test wiki to have both lazy loadedintention was to allow comparison with the large sized Japanese wiki which had lazy loading images enabled but not lazy loaded references enabled to inform whether it was worth pursuing lazy loaded references.

Sanity checking (10 days)
To get a general sense of impact after 10 days of the change being live it was possible to compare 10 days prior to the change with 10 days after the change. Using the following SQL query, it was possible to take a database dump of all NavigationTiming events logged for 10 days preceding the change and 10 days following the change. This SQL query gave a sample of 167844 rows of data (5 times the amount for the corresponding test in Thai Wikipedia in half the time).

With the result of the following query, using a Python script the following command was run

Conclusions
After almost a month of running this experiment it's clear that lazy loading references has minor impact on first paint or DomInteractive, but it does appear to improve things, but it could be argued this is due to lazy loading images. That said the performance improvements on Japanese Wiki were less significant. See Reading/Web/Lazy loading of images on Japanese Wikipedia.

The impact on fully loaded time is more significant on http1 than http2 (improving the 95th percentile by 4 seconds).

More analysis around the data savings at play here are needed.