Reading/Web/Performance/Removal of srcsets

As of 17th February 2016 (00:54) the mobile web site no longer serves srcset attributes.

Impact on bytes
For the Barack Obama article this halved the amount of bytes of images we shipped to users on initial load from 1.12mb to 450kb.

Impact on render and fully loaded time
Using webpagetest we can see the impact on production for the loading of Barack Obama simulated under 2G connections.

There seems to be a minor improvement, but despite the big difference in bytes there are still the same amount of HTTP requests competing against one another. It is expected that lazy loading images will have a much greater impact on these graphs.

Generally this looks positive, but not massively impactful. Measuring the average of all median fully loaded times before and after the change, using a script, it seems to have improved fully loaded time by 5%.

Global impact
This change to be accurately measured, due to internal caching would take 30 days to completely roll out across the entire site. It should be noted that other changes post this change could have improved or reduced performance. Since a change was made on the 16th March we consider data collected up to this date and post the roll out of the change. Given the leap day in this period this is a 27 day period.

Impact on bytes
Before the change we were serving roughly 1.6gb of images to users, 30 days afterwards we were serving 0.9gb of images. Given the text served didn't see a drop I believe we can probably attribute this to the srcset removal.

Impact on fully loaded time
That said looking at `frontend.navtiming.totalPageLoadTime.mobile.anonymous` for global traffic the fully loaded time median time also appears to have improved by around 5% over a 27 day period

That said, the fully loaded times we are currently collecting are sub 5s so do not reflect 2G connections. It is suspected that on 2G, page loads take so long that these users are currently not represented in the data we collect.

Impact on page views
According to the page view API, there was no significant and obvious spikes in page view traffic relating to this change a week after it had occurred.