Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Are these WebP images? Could this issue be related to the one we responded to yesterday? That problem will be solved in the next version (v2.2), which is due to be released early next week.

    Thread Starter relle

    (@relle)

    No, this is a different website / domain name.
    And I’m not using WebP images for this site

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi, @relle

    Please share your Environment Report: Navigate to LiteSpeed Cache > Report, press the Send to LiteSpeed button, make note of the “Report Number”, and post the number here so we can look it up.

    Thanks!

    Thread Starter relle

    (@relle)

    Hello,

    Here you go
    Report number: RNAASIJB

    The reason the cache has been disabled is that this is a staging site. And on my live site I currently use WP Rocket for caching… If all my images will be lazy loaded properly with LiteSpeed. I’m ready to make the switch!

    Thanks!

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi, @relle,

    We’ve been looking at your site, and honestly, since the page is so short to begin with, it’s hard to tell whether lazy load is working or not. The way lazy load is implemented, it loads the images in the viewport as well as those just below it.

    We can see that the proper lazy load code is there in the source, so in theory it should be working.

    What do you see in the pingdom report that leads you to believe it is not working?

    Thread Starter relle

    (@relle)

    Hi,

    The pingdom result shows their are 21 image requests. And only 4 empty gif requests.

    Please click the “VIEW MORE” button below the images on the homepage.

    Is Litespeed’s lazy load compatible with Isotope?

    Thanks!

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    When I click “view more” it brings me to a whole new page, and all of the images are visible.

    It seems to me that there are only 4 placeholder images being shown because that is all that is needed. The remainder of the images either fit inside the viewport, or are near enough to it that they are loaded anyway.

    If you want to test it further, you’ll need to add more images, or add a big block of text at the top to force the images further down the page. Either of those things should result in fewer images being loaded initially.

    Is Litespeed’s lazy load compatible with Isotope?

    I don’t know. What is Isotope?

    When you view the source, you see that the necessary lazy load tags are being added to the images. LiteSpeed’s lazy load is doing its job properly, from what I can see.

    Thread Starter relle

    (@relle)

    Hello,

    It seems to me that there are only 4 placeholder images being shown because that is all that is needed. The remainder of the images either fit inside the viewport, or are near enough to it that they are loaded anyway.

    For testing purposes I added a block of text to the homepage.

    And I did another pingdom test: https://tools.pingdom.com/#!/nEzCx/https://testing.6x6project.com/

    For me, it looks like the same result as before: There are 21 image requests. And only 4 empty gif requests.

    I don’t know. What is Isotope?

    Isotope is a JavaScript library to create masonry layout (and filtering): https://isotope.metafizzy.co/

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    We’re not sure whether masonry and our lazy load are compatible. We need to test it. This may take a day or two, given our current workload. We’ll get back to you soon!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Images masonry layout not being Lazy Loaded’ is closed to new replies.