Problem with option “Optimize HTML Code” and “Revolution Slider”

ik vervolg in het Engels zodat toevallige passanten kunnen meegenieten @viet0viet ??

in that case you’ll have to exclude js/jquery/jquery.js from optimization.

frank

Ofcourse! That solution works partially. The slider will show but my testmysite.thinkwithgoogle.com score stays the same and the page speed score drops from 100/100 to 91/97.

Is there a workout around for this problem?

Well, I would try

* OR keep “also aggregate inline JS” active but exclude any inline JS that changes, e.g. the JS for the contact widget which you could exclude by adding toAppend+=String.fromCharCode to the comma-separated list of JS optimization exclusions.

if I were you B-)

Can you give me some more information about this option? The developer and I don’t know quite sure what we have to do with the solution you are giving.

Im talking about this part: “exclude any inline JS that changes, e.g. the JS for the contact widget which you could exclude by adding toAppend+=String.fromCharCode to the comma-separated list of JS optimization exclusions. ”

Thanks in advance!

well, you want to make sure AO does not have to re-minify for every request (because the time it takes + cache size impact). to do that you need to either disable “aggregate inline JS” OR keep that on but exclude the inline JS that has changing variables. In your case an example of that “cache-busting inline JS” is the JS that is included in the “contact”-widget, which reads;

var t=[61,-1,98,-66,170,-56,157,-55,116,-82,191,-94,199,-91,207,-96,154,-116,151,-94,151,-92,130,-95,144,-95,144,-85,123,-88,137,-88,136,-77,115,-80,129,-80,134,-75,113,-78,135,-80,139,-101,136,-79,136,-77,115,-80,129,-80,134,-75,113,-78,132,-80,139,-101,136,-87,135,-87,146,-108,143,-86,141,-82,120,-85,134,-86,139,-80,118,-83,132,-82,132,-73,111,-76,125,-75,124,-65,103,-68,120,-66,125,-87,122,-73,121,-64,123,-85,120,-71,119,-70,129,-91,126,-77,125,-77,136,-98,133,-84,132,-79,138,-100,135,-78,133,-74,108,-46,129,-13,130,-13,127,-95,206,-96,211,-179,280,-179,289,-257,358,-249,346,-241,349,-316,376,-329,426,-364];var toAppend='';for(var i=1;i<t.length;i++)
{toAppend+=String.fromCharCode(t[i]+t[i-1]);}
document.getElementById('8457dbbd0103a28122f0f5ddf55bac72').innerHTML=toAppend;;

so to exclude that block of JS from optimization, you would add toAppend+=String.fromCharCode to the comma-separated list of JS optimization exclusions. and then you should check if you have other cache-busting JS and again apply the same principle.

Can so show me an example of this added to the comma-separated list of JS optimization exclusions? Some kind of screenshot?

errr … OK ??

View post on imgur.com

Ah.. this get’s more clear to me. Can you tell more about: “check if you have other cache-busting JS and again apply the same principle.”

well, look in your HTML source if there are other bits of inline JS that are also subject to change (time-based or URL-based or session-based) and if so also exclude those from optimization.