Exclude javascript from optimization

when “optimize JavaScript” is on, what errors do you see on the browser console?

re. twig JS; if that is inline simply deactivate the option to aggregate (or defer) the inline JS?

I am not getting any error in the console but the js code is not visible in the view page source for non-logged in users, how to fix this issue and this is dropping the core web vitals, so I need to keep js code visible and also to fix core web vitals

Also aggregate inline JS?
when I check this option I am getting that issue, as the non-logged in users are not able to view the js code in the view source code, how to fix it

• This reply was modified 1 year, 4 months ago by impex23.

well, JS code does not have to visible, the reason it’s not visible is that it’s part of the aggregated file. but if you don’t want that you can keep that option disabled?

if that option is disabled, then core web vitals will be more than 9.5 s

well, as JS code does not have to be visible in the HTML to function, you could simply let the inline JS be aggregated?

OR you could exclude specific inline JS by adding a (unique) keyword that is in the block of inline JS you would like to keep in the HTML?

desktop will be fixed, I am talking about mobile core web vitals

I had a quick look at the Pagespeed Insights for mobile; the biggest issue by far currently is the “server response time”, for which you should implement page caching (this is not part of Autoptimize, but you can install e.g. KeyCDN Cache Enabler for that or you could give Autoptimize Pro a try).

Javascript-wise the biggest issue seems to be with the Google Tag Manager code which AO can’t optimize. consider simplifying the amount of logic implemented in GTM?

Okay, thanks for the quick response so issue is not from Autoptimize then, we will try to check with server response time then, thank you

you’re welcome, feel free to leave a review of the plugin and support here! ??

frank