Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1376231

    Hi,
    When I did pagespeed today on my page (after upgrade to 5.3) following is reported to my report (Array.isArray + babel/plugin-transform-classes)

    Avoid serving legacy JavaScript to modern browsers
    Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. 
    
    Potential Savings
    …js/avia.min.js?ver=5.3 - 6.6 KiB - …js/avia.min.js?ver=5.3:1:16 = Array.isArray
    …mediaelement/mediaelement-and-player.min.js?ver=4.2.17 - 0.1 KiB -…mediaelement/mediaelement-and-player.min.js?ver=4.2.17:12:12531 =
    @babel/plugin-transform-classes

    Can you please check if Enfold is using some legacy Javascript or why this would be reported?
    Thanks

    #1376480

    Hey Jaro,
    Thanks for the link to your Pagespeed report, the part you are talking about is in the PASSED AUDITS this means the theme passed this test and not something that needs to be addressed
    2022-12-17_003.jpeg

    Best regards,
    Mike

    #1376668

    Strange, it seems to be gone now. Thanks. Feel free to close this one.

Viewing 3 posts - 1 through 3 (of 3 total)
  • The topic ‘Legacy javascript Array.isArray and plugin-transform-classes on mobile’ is closed to new replies.