Hi,
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: results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fforeground.wikiproject.net%2Fwiki%2FMain_Page&tab=mobile
Regards, Nischay Nahata
Hi Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/...
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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki
Regards, Nischay Nahata _______________________________________________ Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/... https://tools.pingdom.com/#%21/dxXmf4/https://foreground.wikiproject.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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata <nischayn22@gmail.com mailto:nischayn22@gmail.com> wrote:
Hi,
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: results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fforeground.wikiproject.net%2Fwiki%2FMain_Page&tab=mobile
Regards, Nischay Nahata _______________________________________________ Foreground mailing list Foreground@lists.wikimedia.org mailto: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
I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/...
https://tools.pingdom.com/#%21/dxXmf4/https://foreground.wikiproject.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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata <nischayn22@gmail.com mailto:nischayn22@gmail.com> wrote:
Hi,
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: results for foreground wiki
Regards, Nischay Nahata _______________________________________________ Foreground mailing list Foreground@lists.wikimedia.org
mailto:Foreground@lists.wikimedia.org
Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
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. ;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck rebastion@mailbox.org wrote:
I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/...
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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki
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/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
Hi all,
Tom, you are right. I found out that the reason behind the "slowness" of the website was something else. Google checks for a few things and suggests based on that, whereas the real issue might be something completely different.
I was able to add Cloudflare to cache all our "load.php" calls and that has worked well. I am now also carefully using ResourceLoader for all my extensions.
I also found certain areas of improvement in some other extensions ( see https://github.com/SemanticMediaWiki/SemanticResultFormats/issues/193 ) - that I will be working on over the next few days.
Coming to image compression - Yes that's one of the "next" item on my plate as our wiki deals with lots of images. I am still looking for open source libraries for the same. Do reach out to me if you have something on this (maybe on a separate thread :p)
Regards, Nischay Nahata
On Thu, Mar 2, 2017 at 3:30 AM, 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. ;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck rebastion@mailbox.org wrote:
I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground. wikiproject.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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fforeground.wikiproject.net%2Fwiki%2FMain_Page&tab=mobile
Regards, Nischay Nahata
Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
Foreground mailing listForeground@lists.wikimedia.orghttps://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
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. ;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck
rebastion@mailbox.org wrote:
I have to say my wikis run very well on Cloud ways. Never thought so
but super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/...
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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com
wrote:
Hi,
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: results for foreground wiki
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/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
Is that an open source library we can download and develop an extension ourselves?
Regards, Nischay Nahata
On 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. ;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck rebastion@mailbox.org wrote:
I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground. wikiproject.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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fforeground.wikiproject.net%2Fwiki%2FMain_Page&tab=mobile
Regards, Nischay Nahata
Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
Foreground mailing listForeground@lists.wikimedia.orghttps://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
There is a CLI version at least. Have a look. It might help if more people asked him
On 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 Nahata
On 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.
;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck
wrote:
I have to say my wikis run very well on Cloud ways. Never thought so
but
super low maintenance
On 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 Nischay
https://tools.pingdom.com/#!/dxXmf4/https://foreground. wikiproject.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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki
Regards, Nischay Nahata
Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
Foreground mailing
listForeground@lists.wikimedia.orghttps://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
Can also try https://github.com/tjko/jpegoptim See example here: compressor.io
Regards, Nischay Nahata
On 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 him
On 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 Nahata
On 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. ;)
Tom
On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck rebastion@mailbox.org wrote:
I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance
On 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 Nischay
https://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_content.
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.
Tom
On Feb 28, 2017, at 3:05 AM, Nischay Nahata nischayn22@gmail.com wrote:
Hi,
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: results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fforeground.wikiproject.net%2Fwiki%2FMain_Page&tab=mobile
Regards, Nischay Nahata
Foreground mailing list Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground
Foreground mailing listForeground@lists.wikimedia.orghttps://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
-- 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
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/jpegoptim See example here: http://compressor.io Regards, Nischay Nahata On Thu, Mar 2, 2017 at 5:08 PM, Sebastian Haselbeck <rebastion@mailbox.org mailto: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 mailto:nischayn22@gmail.com > wrote: > > > Is that an open source library we can download and develop an extension ourselves?Regards, Nischay Nahata On Thu, Mar 2, 2017 at 2:11 PM, Sebastian Haselbeck <rebastion@mailbox.org mailto:rebastion@mailbox.org > wrote: > > > > I keep emailing thehttp://ewww.io guy to port his extension to mediawiki. That would be yuuge, believe meOn March 1, 2017 11:00:45 PM GMT+01:00, Tom <tom@hutch4.us mailto: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. ;) Tom On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck <rebastion@mailbox.org mailto:rebastion@mailbox.org > wrote: > > > > > > I 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 mailto: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 Nischay > > > > https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/... https://tools.pingdom.com/#%21/dxXmf4/https://foreground.wikiproject.net/wik... > > > > 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_content https://en.wikipedia.org/wiki/Flash_of_unstyled_content . > > > > 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. > > > > Tom > > > > > > On Feb 28, 2017, at 3:05 AM, Nischay Nahata <nischayn22@gmail.com mailto:nischayn22@gmail.com > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > 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: > > > results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Ffo... > > > > > > > > > > > > Regards, > > > Nischay Nahata > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Foreground mailing list > > > Foreground@lists.wikimedia.org mailto:Foreground@lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/foreground https://lists.wikimedia.org/mailman/listinfo/foreground > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Foreground mailing list > > Foreground@lists.wikimedia.org mailto:Foreground@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground 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)
EWWW seems to be working on a standalone version, I am looking forward to that
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/jpegoptim See example here: http://compressor.io Regards, Nischay Nahata On Thu, Mar 2, 2017 at 5:08 PM, Sebastian Haselbeck <rebastion@mailbox.org mailto: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 mailto:nischayn22@gmail.com > wrote: > > > > Is that an open source library we can download and develop an extension ourselves?Regards, Nischay Nahata On Thu, Mar 2, 2017 at 2:11 PM, Sebastian Haselbeck <rebastion@mailbox.org mailto:rebastion@mailbox.org > wrote: > > > > > I keep emailing thehttp://ewww.io guy to port his extension to mediawiki. That would be yuuge, believe meOn March 1, 2017 11:00:45 PM GMT+01:00, Tom <tom@hutch4.us mailto: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. ;) Tom On Mar 1, 2017, at 8:14 AM, Sebastian Haselbeck <rebastion@mailbox.org mailto:rebastion@mailbox.org > wrote: > > > > > > > I have to say my wikis run very well on Cloud ways. Never thought so but super low maintenance> > On March 1, 2017 12:01:15 AM GMT+01:00, "[[kgh]]" <mediawiki@kghoffmeyer.de mailto: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 Nischay > > > > > > https://tools.pingdom.com/#!/dxXmf4/https://foreground.wikiproject.net/wiki/... https://tools.pingdom.com/#%21/dxXmf4/https://foreground.wikiproject.net/wik... > > > > > > 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_content https://en.wikipedia.org/wiki/Flash_of_unstyled_content . > > > > > > 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. > > > > > > Tom > > > > > > > > > On Feb 28, 2017, at 3:05 AM, Nischay Nahata <nischayn22@gmail.com mailto:nischayn22@gmail.com > wrote: > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > 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: > > > > results for foreground wiki https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Ffo... > > > > > > > > > > > > > > > > Regards, > > > > Nischay Nahata > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Foreground mailing list > > > > Foreground@lists.wikimedia.org mailto:Foreground@lists.wikimedia.org > > > > https://lists.wikimedia.org/mailman/listinfo/foreground https://lists.wikimedia.org/mailman/listinfo/foreground > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Foreground mailing list > > > Foreground@lists.wikimedia.org mailto:Foreground@lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground 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 mailto:Foreground@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/foreground 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)
foreground@lists.wikimedia.org