How can this work with Plugin Optimizer?

  • Resolved meadows19

    (@meadows19)


    8 years ago

    Yes, a minified and concatenated .js file is better that the standard, but the best .js file is one that doesn’t ever load in the first place!

    My idea is to use a something like Plugin Optimizer to stop plugins loading on pages where they are not needed.

    My question is: how will this work with Autoptimize? Should I disable the .js functions and only leave the html and css functions operating?

    If anyone can offer any suggestions, because I’m really confused about how to do it and how it would work.

Viewing 1 replies (of 1 total)
  • Plugin Author Frank Goossens

    (@futtta)

    it can work even without putting any thought in it; you plugin-optimize your site and AO aggregates & minimizes all outputted JS.

    but there’s more to it; if you use plugin optimizer, you could theoretically end up with different JS on each means, which would mean that the autoptimized JS is different on each page which is far from optimal (as not cached in browser and AO having to recreate the optimized file for each page).

    what you could do is exclude the biggest abusers (those loading on each request but only needed in e.g. the payment-page or a contact-form) in plugin-optimize but ALSO in autoptimize.

    it’s all about finding a good balance ??

    have fun!
    frank

Viewing 1 replies (of 1 total)
  • The topic ‘How can this work with Plugin Optimizer?’ is closed to new replies.