• Resolved skillsharejp

    (@skillsharejp)


    WP Rocket adds “defer” attribute to end of flying-pages.min-2.4.1.js.

    Is it better to exclude it from WP Rocket?

    If yes, could you consider adding data-cfasync=”false”, so that WP Rocket automatically excludes flying page javascript, and also cloudflare rocket loader ignores it.

    Final code should look like

    <script data-cfasync="false" src='https://example.com/wp-content/cache/busting/1/wp-content/plugins/flying-pages/flying-pages.min-2.4.1.js'></script>

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Gijo Varghese

    (@gijo)

    @skillsharejp Flying Pages should start execution when the browser has completed downloading other critical resources. So defer is recommended (Flying Pages by default users defer).

    Even if you exclude it from defer or Cloudflare rocket loader, Flying Pages starts prefetching when browser becomes idle.

    Thread Starter skillsharejp

    (@skillsharejp)

    Thanks, I asked because I can’t confirm “prefetch cache” in network when I open pages preloaded by flying page plugin just like your demo youtube. I thought defer tag was preventing it function properly.

    Let’s see what else is doing wrong…

    Plugin Author Gijo Varghese

    (@gijo)

    @skillsharejp can you pls share the URL?

    also, check out the ‘Compatibility’ tab inside Flying Pages settings

    Thread Starter skillsharejp

    (@skillsharejp)

    Sorry, I just realized I checked disable cache on network tab for debug purpose…

    Plugin Author Gijo Varghese

    (@gijo)

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP Rocket defer attribute compatibility’ is closed to new replies.