As you have Autoptimize optimizing the JS already, I’m not sure AsyncJS would be of much use to be honest Anne-Barbara. Any special reason why you’re trying it?
Thank you! With Async JS the page was 15% faster. But I just realized that I had to deactivate Autoptimize, too, because my menu on the mobile Version didn’t work either. It’s a pity, because my pagespeed was good. But now I have to look for another solution.
But I just realized that I had to deactivate Autoptimize, too, because my menu on the mobile Version didn’t work either.
you’ll probably just have to exclude one or more of your theme js-files from being optimized 🙂
How do I find these theme js-files? I’m not a developer…
I could do it for you, but you’d have to disable JS (and CSS) optimization in W3 Total Cache because that “hides” the original sources (and could conflict with Autoptimize if/ when you re-enable).
Wow, thank you very much! 🙂 I just disabled it.
OK, had a look; having “also aggregate inline JS” off and having js/jquery/jquery.js excluded from JS optimization should be sufficient. Can you try that? If not OK; what JS error is shown on the browser console?
Thanks, I had tested this setting before writing here, and js/jquery/jquery.js was already excluded from JS optimization as default. So this doesn’t work. I re-activated autoptimize with the settings you proposed, and there appear 2 errors on the console:
TypeError: jQuery(…).smartmenus is not a function
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://googleads.g.doubleclick.net/pagead/id. (Grund: CORS-Anschlag schlug fehl).
That means a cross-origin request was blocked, CORS didn’t work (I hope I translated it right)
OK, next up; also exclude themes/weaver-xtreme/assets/js/smartmenus/jquery.smartmenus.min.js or (if the former does not work even themes/weaver-xtreme/?
Thank you very much, excluding the smartmenus worked! I’m very happy with that. 🙂
But don’t you have a solution for thrive leads in Async JS? Cause my pagespeed on mobile is still bad (48%)… and with Async JS it was 75%!
Did you have the autoptimize integration on? what happens if you disable that? And was jQuery excluded from async/defer?
I just changed some settings in autoptimize and the pagespeed is getting much better (60% mobile, 96% desktop), but still worse than with Async JS. So I reactivated it, disabled the autoptimize integration and excluded jQuery as you proposed. Now Thrive Leads works, 🙂 but there is another strange effect:
On the desktop view there was an unstyled version of the page for a second or so, before the theme is loaded. There is no new error on the console.
But as I checked the pagespeed, it was worse than before re-activating Async JS with the new settings. So I think you were right in your first answer, that it makes no sense. I think 60% mobile and 96% desktop is o.k., so I will work with w3 total cache and autoptimize only. Thank you very much for your great support! 🙂
Bad news: The effect that the page is unstyled for some seconds stayed when I deactivated Async JS, so I had to deactivate Autoptimize, too… 🙁
I just found out that it was the critical path css, now the page is loading normally…
