Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #892021

    Hi guys, Merry Christmas!

    I have noticed that the Lazy Load image feature on WP-Rocket causes a conflict with the Masonry Content Element in the theme. All the images stack up on each other and don’t render in their own placeholder properly.

    I have had to disable Lazy Load on the affected pages (as you would expect) but have kept this one ‘live’ so you can see the problem: https://www.swarez.co.uk/recently-sold-art/

    It should look like this: https://www.swarez.co.uk/sold-work-2015/

    Can someone take a look at it please?

    Thanks in advance
    Ed

    • This topic was modified 6 years, 11 months ago by Swarez.
    #892225

    Hey Ed,

    You can try to disable the Lazy Load on specific pages. Here is an article about it:
    http://docs.wp-rocket.me/article/15-disabling-lazy-load-on-specific-images

    If you need further assistance please let us know.
    Best regards,
    Victoria

    #892636

    Hi Victoria

    I am aware that you can turn off Lazy Loading on specific pages; if you read my question again you’ll see I have already mentioned that I have done that.

    But this doesn’t solve the problem of the Enfold Masonry elements causing a conflict with Lazy Load on WP Rocket.
    The problem ideally needs resolving don’t you think? Not just turning off an ignoring.
    Can you help?
    Thanks in advance and Happy New Year!
    Ed

    #893095

    Hi,

    Lazy load for that element won’t work as the script which controls the size of the images need to be loaded in the header which your caching plugin blocks.

    Best regards,
    Rikard

    #893488

    Hi Rikard
    So how do we change this then so that it does work?
    I can exclude scripts from minification in WP-Rocket so what do I need to exclude?
    Thanks
    Ed

    #893812

    Hi Ed,

    You need to exclude avia.js and shortcodes.js.

    If you need further assistance please let us know.
    Best regards,
    Victoria

    #893926

    Hi Victoria
    Thank you for that.
    Still doesn’t work when the files are excluded from minification and load in the header.
    Any ideas please? I really need to get this sorted on Masonry elements otherwise Lazy Loading is pointless and that would be a great shame.
    Thanks
    Ed

    • This reply was modified 6 years, 10 months ago by Swarez.
    #894141

    Hi Ed,

    It could be very much the case. Have you excluded jQuery as well?

    Best regards,
    Victoria

    #894187

    Yes I have Victoria
    Still the same – overlapping etc…
    Oh well, not to worry. I have put everything back now.
    It’s a great shame as it would have halved the size of the page and probably given me a small ranking boost but it sees the theme doesn’t like WP-Rocket for that so I guess I will have to abandon that idea.
    Thanks anyway.
    Best Ed

    #894293

    Hi Ed,

    Since you are loading that element first on the page, I don’t think lazy load will do much good anyway to be honest, since it will load directly. The size of the page won’t be smaller in reality either, since it will load at the same size when it’s in view.

    Best regards,
    Rikard

    #894356

    Hi Rikard
    Not quite correct – the Lazy Load script will load 1.2mb of 2.5mb page (on load and according to Pingdom) so in a mobile scenario it makes the render appear quicker. Although ultimately the page will be rendered it will only be on scroll – which is the whole point. A mobile user, on 3G shouldn’t need to load all 2.5mb if they don’t need it and certainly not all at the point of connection.

    I want Lazy Load to take advantage of the zero byte placeholder principle (as HTTP/2 favours parallel loading) so it makes sense to make the initial page load as small as possible. This is about perceived load and TTFB (Time To First Byte). Go check Google Lighthouse to learn more.

    Lazy Load does this on my biggest page and I need it to work for those reasons.

    It’s very disappointing (again) that a really good plugin can’t function properly with Enfold. (I fought with you guys for 2 years to get Yoast to crawl images properly for the sitemap function (which you eventually did).

    I wish Kreisi would prioritize the changes in User Experience and the move towards a mobile-first index. As we move forward in the way search is evolving it’s these kind of small adjustments that can make massive differences to the rank, and performance, of a business website. It is a selling point. We need this more than we need animations and scrolling banners and sliders.

    You can close the thread if you want because I’m not going to get anywhere am I?
    Thanks for your time
    Ed

    • This reply was modified 6 years, 10 months ago by Swarez.
    #894471

    Hi Ed!

    Thank you. I forwarded your thread to Kriesi.

    Best regards,
    Victoria

    #894477

    Thanks Victoria

    That’s a great proactive response and one I am most grateful for.

    All the best
    Ed

    #1028388

    Hi guys,

    is there already a solution? I’m facing the same issue with the Masonry Content Element and Lazy Load in WP-Rocket. My website is stretched over the whole screen width, and it will have a big number of images within post previews on several pages. I want to display the post previews with the Masonry Content Element. It would be very bad for the website speed to disable Lazy Load on these pages.

    Best regards,
    Michael

    #1029775

    Hi,


    @elskeletto1
    : Please create a new thread with the site url and login credentials. We’ll check it there.

    Best regards,
    Ismael

Viewing 15 posts - 1 through 15 (of 15 total)
  • The topic ‘Masonry element and WP-Rocket LazyLoad’ is closed to new replies.