Jetpack’s Lazy load and Native Lazy Load

  • Resolved Alvin

    (@iluminancia)


    4 years, 7 months ago

    Hi,

    I hope someone can help with following issue:

    With WP 5.5, native lazy load has been added, so ?do we need to keep Jetpack’s lazy load actived or anyother plugin?

    This why I’m asking:

    WP 5.5 and Jetpack’s lazy load OFF:
    – GTMetrix shows total file size 540 kB, FLT < 2 seconds, I can see all homepage images in the waterfall
    – PageSpeed Insights is always below 80
    – Images load fine in Chrome, Firefox and Edge after clearing all caches.

    WP 5.5 and Jetpack’s lazy load ON:
    – GTMetrix shows total file size 340 kB, FLT < 2 seconds, I can see only images above the fold in the waterfall
    – PageSpeed Insights is (usually) above 90
    – I need to refresh pages in order to see images.

    Any suggestions?

    Stay safe,

    Alvin

    • This topic was modified 4 years, 7 months ago by Alvin.
    • This topic was modified 4 years, 7 months ago by Alvin.
    • This topic was modified 4 years, 7 months ago by Alvin.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor James Huff

    (@macmanx)

    The two use very different protocols.

    WordPress 5.5 uses native browser lazy loading, which is not compatible with all browser (particularly older browsers), but it is more efficient.

    Jetpack uses JavaScript-based lazy loading, which is compatible with all browsers, but not as efficient.

    When our lazy loading is enabled, it overrides WordPress’s lazy loading. When our lazy loading is disabled, WordPress’s lazy loading takes over.

    Thread Starter Alvin

    (@iluminancia)

    Hi James,

    Thanks a lot for a quick reply!

    Best regards,

    Alvin

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Jetpack’s Lazy load and Native Lazy Load’ is closed to new replies.