• Resolved testwp75

    (@testwp75)


    Hello,

    What do you think about this conversation about your tool ?

    You are using autoptimize do concatenate and merge all scripts, thus giving a slighter edge to the chunkier elementor, and losing all the benefits of lazy loading of k/g. Your autoptimize setup was ok for 5 year ago http 1.1, but is bad for modern h2/h3 connections.

    So yes, using your 2015 setup, elementor+autoptimize may be a bit better, but if you were using a 2021 setup (k/g and optionally wp rocket or any lazy loading cache) things would be much different.

    k/g = kadence/gutenberg. Check the tutorials about http2 (and now h3), concatenating is not recommended, autoptimize is cool, but there are much better tools like perfmatters or it’s free siblings for selectively loading scripts.

    Regards,

    • This topic was modified 3 years ago by testwp75.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter testwp75

    (@testwp75)

    and any recommendation of settings with your tool + litespeed + perfmatter ?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, the nice thing is Autoptimize is flexible in that respect; you can have it aggregate (concatenate) or you can configure it not to but to defer JS anyhow (with a sub-option to also defer inline JS). same for CSS; even when aggregating is off, you can still use “remove render-blocking CSS”. that way you can test different options and pick the one that gives the best performance for your setup (and sometimes aggregating still does give better results despite http2/3, as the original poster somewhat reluctantly admitted ?? )

    re. litespeed & perfmatters; don’t know those well enough to make recommendation except for making sure not to have different tools act on your JS or CSS (or do lazyload or …)

    hope this clarifies,
    frank

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Issue with http2/3 & concatenate’ is closed to new replies.