Cache size: also merge inline JS?

  • Resolved espox

    (@espox)


    3 years, 7 months ago

    Hello dear team,

    your work is amazing!

    Can you give us an Einshcätzung here, in what way a big cache is bad in your perspective?

    “Autoptimize should also extract JS from the HTML (not recommended because it can quickly grow the size of the Autoptimize cache)”

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 7 months ago

    have a look at this explanation I wrote a couple of years back, it’s still valid 🙂

    hope this clarifies,
    frank

    Thread Starter espox

    (@espox)

    3 years, 7 months ago

    Hey,

    I really appreciate your work and fast reply but I did not get the meaning of the post.

    1.) “1. you will be generating new autoptimized JS very regularly, which slows your site down for users who happen to be the unlucky ones requesting that page”

    When you have alot of users, you really should care about the unlucky one who enter the uncached page?

    2.) “a visitor going from page X to page Y will very likely have to request a different autoptimized JS file for page Y instead of using the one from page X from cache, again slowing your site down”

    But I think that AOO cache all pages of my page and as long as all pages are cached this “slow-down-problem” does not appear anyway? And if so, I would like to jump to “1.)” Should I really turn off a big AOO cache only to have 1 or 2 unlucky users less? I mean AOO does not clear the cache so often and when I have a only shop there will be not so much related cache clears / new content.

    Thank you! WOuld it be possible to surprise me with 1-2 sentences? Would be amazing!

    • This reply was modified 3 years, 7 months ago by espox.
    Plugin Author Optimizing Matters

    (@optimizingmatters)

    3 years, 7 months ago

    I’m afraid you’re a little bit to optimistic; there are plugins that change inline JS (or CSS) on every page request, so the impact would be significant.

    That being said; you are obviously free to turn “also aggregate inline JS” on, but instead of aggregating all JS, you might (the proof is in testing the pudding) in the context of HTTP2 be better off with the combination of “don’t aggregate but defer” and “also defer inline JS”? 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cache size: also merge inline JS?’ is closed to new replies.