Optimization of the aggregated JS files

  • Resolved borish1

    (@borish1)


    3 years, 11 months ago

    Hi,

    I’m trying to analyze how AO performs aggregation of JS files.

    We are doing page caching via Nginx and we are also doing lots of dequeues per page level.

    Will these dequeues then mean that AO will create separate JS bundles per page level (because of the different dequeues)?

    I’m wondering then is it better to NOT dequeue anything and make AO bundle one big fat bundle.js which will get cached and be used throughout the pages OR to have multiple dequeues per page and have AO create multiple .js bundles?

    • This topic was modified 3 years, 11 months ago by borish1.
Viewing 1 replies (of 1 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Will these dequeues then mean that AO will create separate JS bundles per page level (because of the different dequeues)?

    correct

    I’m wondering then is it better to NOT dequeue anything and make AO bundle one big fat bundle.js which will get cached and be used throughout the pages OR to have multiple dequeues per page and have AO create multiple .js bundles?

    hard to give a definitive answer to be honest … If I were you I would experiment, comparing performance test results for “no dequeue + AO aggregated” with “dequeue + AO not aggregating but deferring (newer option) and go for the setup that yields best results?

    hope this helps,
    frank

Viewing 1 replies (of 1 total)
  • The topic ‘Optimization of the aggregated JS files’ is closed to new replies.