EWWW seems to be working on a standalone version, I am looking forward to that
https://ewww.io/plugins/
Sebastian Haselbeck <rebastion@mailbox.org> hat am 4. März 2017 um 13:02 geschrieben:that is useless for me. I would need something that goes through my entire MW images directory and compresses gigabytes of images
Nischay Nahata <nischayn22@gmail.com> hat am 3. März 2017 um 19:23 geschrieben:Can also try https://github.com/tjko/jpegoptimSee example here: compressor.io_______________________________________________Regards,
Nischay NahataOn Thu, Mar 2, 2017 at 5:08 PM, Sebastian Haselbeck <rebastion@mailbox.org> wrote:There is a CLI version at least. Have a look. It might help if more people asked himOn March 2, 2017 10:05:14 AM GMT+01:00, Nischay Nahata <nischayn22@gmail.com> wrote:Is that an open source library we can download and develop an extension ourselves?Regards,
Nischay NahataOn Thu, Mar 2, 2017 at 2:11 PM, Sebastian Haselbeck <rebastion@mailbox.org> wrote:I keep emailing the ewww.io guy to port his extension to mediawiki. That would be yuuge, believe me
On March 1, 2017 11:00:45 PM GMT+01:00, Tom <tom@hutch4.us> wrote:One thing I really investigated yesterday was compressing images. Image compression has gotten really good and I cannot believe how much the file sizes reduced. I cut a page load size in half by compressing three images on that page. Which in turn dropped the page load speed by one full second.It's too bad files that are uploaded aren't automatically compressed. I know there are online tools where you can upload an image and then download the compressed version. I just don't know if there's anything that's open source that could be built into MediaWiki's core, what take into account, file type, etc. Or would it explode into a what file type is better. ;)TomI have to say my wikis run very well on Cloud ways. Never thought so but super low maintenanceOn March 1, 2017 12:01:15 AM GMT+01:00, "[[kgh]]" <mediawiki@kghoffmeyer.de> wrote:Heiya,
I must also note that the virtual host for the foreground wiki was badly configured when it comes to page speed. After adding some fluff the rating from Google went up from 60 to now 77. Basically I added configurations for mode headers, expires and deflate which I did not have in there before. Also I upgraded the Header Tabs extension to master which now uses the ResourceLoader (not yet released). To cut it short: It is not just the skin but also other factors which enormously impact page speed which are beyond the things MediaWiki as such can do.
Tom's link already included the fluff I added.
Cheers Karsten
Am 28.02.2017 um 15:00 schrieb Tom:Hi Nischayhttps://tools.pingdom.com/#!/dxXmf4/https://foreground.wikip roject.net/wiki/Main_Page
In actuality it's about 5% of the page load. Don't chase Google's page speed insights, technically has nothing to do with page speed. Minifying HTML is a joke, to what saving 10% of that actual load which is barely nothing. MediaWiki minifies CSS output already.Even Google is own site doesn't get a stellar mobile rating nor does Facebook and some of the other big ones. I have sites that I actually get flagged because Google analytics and their tag manager doesn't have a high enough expiration passed in its header.Quite frankly you do you want some CSS above the fold because you don't want to have a flash of unstyled content, https://en.wikipedia.org/wiki/Flash_of_unstyled_con tent. If you need to improve speed, a lot of it's going to have to do with your server hosting your site. Header expires, response, php caching, gzip compression of output, etc...Having said all the above, there is a mobile out module for resourceloader. It might be worth a look at ways to reduce js because that's the large target in loading a page.TomHi,I am trying to make my site load faster on mobile and consulting Google's PageSpeed tool for the same. I see that the styles loaded by Foreground skin is pretty huge. Any idea how we can work to reduce this?See:Regards,
Nischay Nahata_______________________________________________
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
_______________________________________________ Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/ma ilman/listinfo/foreground
--
Sent from my Android device with K-9 Mail. Please excuse my brevity._______________________________________________
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
Sebastian Haselbeck (rebastion@mailbox.org)
_______________________________________________
Foreground mailing list
Foreground@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/foreground
Sebastian Haselbeck (rebastion@mailbox.org)