SG-Optimizer lazy loading images is not SEO friendly

  • Resolved alfrex92

    (@alfrex92)


    5 years, 4 months ago

    Hi SG,

    First of all, I would like to congratulate all of you for this great plugin.

    It was so excited when I read in SG blog that SG Optimizer has the feature of lazy loading images. Also, that you using the technique of base64 for the placeholder which is great for performance.

    Even though that the plugin is amazing, there is something HUGE that you are missing.

    The plugin is not adding a NO-SCRIPT below the images, which makes the lazy-loading feature not very helpful.

    Why the NO-SCRIPT? What are you talking about?

    Google mentioned in May of 2018 that is CRUCIAL to add the NO-SCRIPT tag below images that are using lazy loading.
    This is the video at the exact moment when they mentioned it.

    You can find more info here.

    What is needed to make this plugin awesome is this:

    
<img class="lazy" src="placeholder-image.jpg" data-src="image-to-lazy-load.jpg" alt="I'm an image!">
<noscript>
  <img src="image-to-lazy-load.jpg" alt="I'm an image!">
</noscript>

    I am sure that many of your client’s website relies extremely on SEO. So, not having this feature will negatively impact them.

    I was about to write a post in my blog saying that SG Optimizer is great and is one of the many reasons why SG is the best hosting. But, when I noticed that you are not adding the no-script I was quite disappointed.

    Thank you and I hope that you can add this feature very very soon.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    5 years, 4 months ago

    Thanks for the awesome feedback! We will check that on our dev meeting and make the necessary changes to our plugin for the next update for sure.

    Thread Starter alfrex92

    (@alfrex92)

    5 years, 4 months ago

    Another issue that I found is you are not preventing content reflow.

    You can find more information here.

    The easiest way to avoid content reflow is by using the padding-bottom technique.

    Take a look at this plugin. You can see how that plugin is avoiding the content reflow by adding the padding-bottom in the container of the image.

    Thread Starter alfrex92

    (@alfrex92)

    5 years, 4 months ago

    Any update?

    Thread Starter alfrex92

    (@alfrex92)

    5 years, 4 months ago

    I noticed that the plugin has been updated. But, there are 2 issues.

    1 )The noscript is being added inside the figcaption. According to google it needs to be outside.

    Now: 

    <figcaption>
<noscript> <img> </noscript>
The caption
</figcaption>

    According to google, it needs to be done like this:

    
<noscript> <img> </noscript>
<figcaption>
The caption
</figcaption>

    2) The second issue that I found is that srcset is being added to the noscript. This is not necessary. The src is only necessary. Adding the srcset to the noscript will just increase the size of the HTML file.

    Anthony Acker

    (@anthonyacker)

    5 years, 4 months ago

    Is there any update to the change to the noscript inside of figcaption as well as content overflow?

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    5 years, 4 months ago

    Yes, we will include further patches in upcoming releases.

    Thread Starter alfrex92

    (@alfrex92)

    5 years, 4 months ago

    Thank you for your reply.

    Is the content reflow issue also in your backlog?

    Thank you for your time.

    Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    5 years, 4 months ago

    Hey @alfrex92

    We are currently working on this ticket, but we are unable to reproduce the issue related to the caption. We’ve added image with caption, but the figcaption tag is right after the noscript tag. Is there a way to provide more detailed instructions how we can reproduce it? Or maybe url to your site.

    Thanks,
    Stanimir

    Sean

    (@sean-h)

    5 years, 3 months ago

    I am wondering if the lazy load seo problem has been fixed.

    It was around end December 2018 that I think I turned it on, and about the same time all of our image rankings dropped significantly.

    To be honest, I’m still not entirely sure it was lazy loading that caused this, Hristo knows about my other theories, such as force https not working and compressing existing images, but I am leaning towards lazy load.

    Here is a screenshot of our Search Console:

    https://www.dropbox.com/s/bhm1qcdnrpyck6d/Screen%20Shot%202019-01-17%20at%2012.16.14.png?dl=0

    • This reply was modified 5 years, 3 months ago by Sean.
    • This reply was modified 5 years, 3 months ago by Sean.
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘SG-Optimizer lazy loading images is not SEO friendly’ is closed to new replies.