Hi, Jürgen

I hope you find this topic:)

It is about your Page Loader "Work In Progress" plugin. I have tried it and found, that I cant change Overlay background Color. More precisely, the overlay is not shown. At my site it looks like on your page (http://typesetter-addons.grafikrausz.at/Page-Loader) in "demo" mode.

When I change  

body:last-child #page-loader-overlay {...}

to 

#page-loader-overlay {...}

all works as expected.

 

Best regards

mahotilo

body:last-child is a CSS hack to prevent Internet Explorer 8 to interpret the rule.
First Firefox Quantum (56) also had issues with it but it works again here.
Didn't know about Opera (must have changed recently).

In fact, we shouldn't have to care about IE 8 anymore. I'll remove it.

Thanks for spotting it.

As you know I'm fighting for 100 points in PageSpeed ​​Insights :)

I've found that such page loaders are very useful. If I load CSS asynchronously, the page appears to the user ugly at start. If I use a page loader, I can hide this moment from user. At the same time Google PageSpeed is happy with that "no one blocks page loading".

Now I'm trying to change your plugin to use  $(document).ready( function() {..} to hide loader overlay after loading all CSS (not images). Also, I have moved loader styles to PageLoader.php.

Sometimes I still have a couple of seconds of an unformatted page, but in general it looks like a workable solution.

Do you find it interesting to make some switch in plugin options (and functionality :) - "show loader till": "css are loaded", "all images are loaded"?

It will be great, as for me.

If I load CSS asynchronously, the page appears to the user ugly at start. If I use a page loader, I can hide this moment from user.

So you show a loader to your visitors where Google wants to see a 'fast first render' (which actually is a 'ugly but fast first render').

If Google really takes the first-render time into account for page rank … well, I guess they will catch you doing so - sooner or later ;-)

 

$(document).ready( function() {..}

I'm not sure about it but domready might fire too early.

If Google really takes the first-render time into account for page rank … well, I guess they will catch you doing so - sooner or later ;-)

Oh yes it will happens! But now this solution makes site owners so happy:)