The css in between the noscript tags is the fallback for the javascript-delivered one at the further down in the html. It is not render blocking, as it is only executed if there’s no javascript in the first place.
What specifically does google identify as render blocking?
Frank
Well if you run my site in google page speed insights, you’ll see!
I get:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Approximately 5% of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Optimize CSS Delivery of the following:
http://www.skyfoxdesign.com/wp/wp-content/cache/autoptimize/css/autoptimize_bee43246710581674b255a9850fd77ee.css
It also reckon you could minify the Javascript further, but I think thats a pretty petty thing google wants as it would only save a whole 1kb!
I’ll have a look when I get back from my holidays skyfox.
Frank
ah, now I see, you’re using “defer & inline” without actually inlining anything. this obviously results in your “above the fold” part not being styled until the CSS is loaded, even if it is deferred. either identify your “above the fold” CSS as per the FAQ or just inline all your CSS (if it’s not too big, that is) instead of deferring.
regarding JS minifaction; Google indeed claims to be able to squeeze out just a little more, but the JS minifiction component used in AO does not succeed in doing that. the 1KB indeed is pretty unimportant in the grand scheme of things 😉
hope this helps,
frank
