Hi @lencw, can you link me to the page in question?
Thread Starter
lencw
(@lencw)
It happens on all sites where I have this combination set, its on a live site. The site is:
http://www.dgl-ilkley.co.uk/
I have temporarily set Autoptimize on, so the slider is not displayed.
Let me know when you are done, I need to turn the Autoptimize off again.
there’s more info on troubleshooting in AO’s FAQ, but to cut to the chase;
1. try disabling “force JS into head” + optionally enable “aggregate inline JS”
OR
2. alternatively add “js/jquery/jquery.js” to the JS optimization exlusion list.
frank (ao dev)
Thread Starter
lencw
(@lencw)
Thanks, the combination sorts this issue out.
I have disabled Force Javascript in Header, and enabled Aggregate inline javascript.
This raises another issue with autoptimze, I will raise that there.
Thanks for the help Frank. Let me know if I can be of more assistance.
I was able to eliminate the conflict with the Revolution Slider, and Avada menu by adding “js/jquery/jquery.js” to the JS optimization exclusion list.
However, this allowed 100 blocking script resources, and 5 more blocking CSS resources. It dropped the PageSpeed score from 84 to 48 for mobile, and from 90 to 79 for desktop.
Is there some middle ground I can try to gain a speed advantage while still being able to use the Revolution slider and Avada menu tree?
100 blocking script resources, and 5 more blocking CSS resources. It dropped the PageSpeed score from 84 to 48 for mobile, and from 90 to 79 for desktop.
and that by only adding js/jquery/jquery.js to the JS optimization exclusion list? that’s weird @ccbackus … can you share your URL?
can you copy/paste the contents of the “exclude scripts from optimization”-input field here @ccbackus?
Here’s a screen shot to validate I pulled the right field:
https://www.screencast.com/t/ohjxHmu5
looks correct … can you remove that exclusion again so I can see your page source with and without that exclusion?
frank
Sure. I removed the exclusion. You’ll notice that the slider is gone, and the drop down menu which normally expands on hover no longer functions.
ok; compared HTML source with jquery.js excluded and not excluded and this appears to be a google pagespeed insights fluke; in the version where jquery.js is not excluded is still see a significant amount of JS (mostly Avada theme ones) which remain unoptimized i.e. render-blocking, even if Google doesn’t complain about them. So given you’d want your site to work, I would exclude js/jquery/jquery.js and look into why so many JS-files are not optimized (might be Avada hooking into AO’s API).
Thanks for your insight into this.
