Moving to mobile-l.
The main page changes a lot so it is not the best example. Today for example our image weight is 15.36 kB I'm a little confused what strategy=mobile does differently to strategy=desktop - any idea what that is doing differently?
Note there is also a verbose mode:
tmi en.m.wikipedia.org/wiki/Main_page --verbose
With recommendations to optimise the following images (there is one more but that is outside our control - it is a thumbnail of an image): http://en.m.wikipedia.org/images/mobile/wikipedia-wordmark-en.png Size: 1.8KiB Can be improved by 61% (good to know - I'm not sure where this file lives... how can we get this optimised?)
The Barack Obama article is more damning (~1.97 MB with strategy=mobile whatever that means and 590.06 kB with strategy desktop). Sam Smith and I have been talking about only rendering the lead section in a future version of mobile and delaying loading of images / sections until they are needed. We previously explored this but it didn't get enough support and I think it is worth revisiting now the MobileFrontend code is in a stronger place.
I have setup https://phabricator.wikimedia.org/T87664
On Tue, Jan 27, 2015 at 10:39 AM, Jon Robson jrobson@wikimedia.org wrote:
Moving to mobile-l.
The main page changes a lot so it is not the best example. Today for example our image weight is 15.36 kB I'm a little confused what strategy=mobile does differently to strategy=desktop - any idea what that is doing differently?
Note there is also a verbose mode:
tmi en.m.wikipedia.org/wiki/Main_page --verbose
With recommendations to optimise the following images (there is one more but that is outside our control - it is a thumbnail of an image): http://en.m.wikipedia.org/images/mobile/wikipedia-wordmark-en.png Size: 1.8KiB Can be improved by 61% (good to know - I'm not sure where this file lives... how can we get this optimised?)
The Barack Obama article is more damning (~1.97 MB with strategy=mobile whatever that means and 590.06 kB with strategy desktop). Sam Smith and I have been talking about only rendering the lead section in a future version of mobile and delaying loading of images / sections until they are needed. We previously explored this but it didn't get enough support and I think it is worth revisiting now the MobileFrontend code is in a stronger place.
Is this https://phabricator.wikimedia.org/T68819 again? As an example, I prefer http://www.webpagetest.org/result/140527_0F_HE3/4/details/ JPG rarely get unwiedly, but it's very easy to reach multiple megabytes with a handful PNG and GIF files. On [[w:en:Barack Obama]], the biggest image (25 KB) is a PNG thumb of a SVG graph; the main JPG of the page follows. Do we have stats for 75th/99th percentile of image size downloaded upon article requests? In some popular pages I ended up converting PNG to JPG manually, to save some hundreds KB... maybe that's something worth doing on the fly. https://phabricator.wikimedia.org/T56291 is still open too.
Nemo
On Jan 27, 2015, at 10:39 AM, Jon Robson jrobson@wikimedia.org wrote:
We previously explored this but it didn't get enough support and I think it is worth revisiting now the MobileFrontend code is in a stronger place.
I was not part of the previous conversation, but I guess one of the reasons against it was that we wanted users to be able to view images when they go offline. How can we solve this problem if we delay loading images?
No, the main reason this got abandoned was it also tried to do ajax page loading (lazy loading) and there were not enough people developing on it.
Yes an image would not be loaded if you go offline but if it's hidden behind a section I think this is acceptable.
Basically the tdlr is: Let's reduce what we serve to our users in that initial page load and get things snappy :-) Sam and I have been fiddling with this already here: https://gerrit.wikimedia.org/r/#/c/187062/
On Tue, Jan 27, 2015 at 12:58 PM, Bahodir Mansurov bmansurov@wikimedia.org wrote:
On Jan 27, 2015, at 10:39 AM, Jon Robson jrobson@wikimedia.org wrote:
We previously explored this but it didn't get enough support and I think it is worth revisiting now the MobileFrontend code is in a stronger place.
I was not part of the previous conversation, but I guess one of the reasons against it was that we wanted users to be able to view images when they go offline. How can we solve this problem if we delay loading images?