Ao is not Working with CDN

I don’t think the CDN is the problem actually. looking at the pagespeed insights score, the problem is rather with the inlined (critical) CSS which (according to GPSI) is not sufficient to render your above-the-fold content @postali

hope this clarifies,
frank

Thank you for your reply, I read a lot of the support topics about (in lining the css) which you recommend checking (Inline and Defer css) so thats what I did, I also followed the video that you posted about how to extract the critical css and use it as above the fold content.
What I did now is checking (inline all css) which took care of everything and now the score is back to 97/97 with the CDN being enabled. I’m still not sure about the difference between (Inline and Defer css) and (inline all css) and how they affect each site differently, but I’ll give it sometime and see if what I did really worked for this site or not (because usually GPSI tricks me and after an hour I find different results).

Thank you again!
I’ll mark this topic as solved once I make sure the score is the same after sometime.

I think it did help slightly. I was trying to look into it to help while having lunch at work and in terms of loading and speed index its slightly faster:

Before: https://www.webpagetest.org/result/170331_DS_62GK/

After: https://www.webpagetest.org/result/170331_H4_63H2/

I think I would consider installing also Frank’s other plugin WP YouTube Lyte to decrease some requests unless you already have it and I missed it.

And disable emojis from WordPress if you do not use them, there is a plugin for that also.

the difference between “inline all CSS” and “inline & defer CSS”:
* “inline all” is easy
* if you have a lot of CSS, “inline all” will have GPSI complain about multiple round-trips (on TCP/IP level) before the real content is loaded (which is sub-optimal)

* “inline & defer” is more difficult as you need a tool to extract your critical CSS and you might have to tweak the result
* if your critical CSS is not to google’s liking (because it’s not sufficient to render your above the fold content) GPSI will complain (as the deferred CSS will still be needed to render your above the fold content)
* despite “inline & defer” google migth keep on complaining if you have JS changing the layout of your above the fold contents

so indeed “inline all” can give better results then “inline & defer”, although the latter generally is the better approach. as always; test, configure, re-test, re-configure, rinse and repeat ??

frank

@lutechi
Thank you, yea it defiantly made a difference, and I will check the other plugins.

@futtta thank you Frank, that clears things a bit I’ll try this with my other websites because I have one site that 88/96 and GPSI is complaining in the desktop only about above the fold content.
Ah yes thats what I do test,configure,re-test, re-configure all in infinite loop haha … Thanks again