Need improve lazy loader

  • As you can see in the picture, it does not comply with w3c standards. It should be replaced with a real url instead of base64 or kept temporarily in data-src. Actually I don’t know your code. So I just wanted to report it here.

    https://prnt.sc/1Mt8bSQQlvrA

    Additionally, you should not detect the images that are on the opening of the page and add lazy load.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author adeelkhan

    (@adeelkhan)

    The Lazy-Load for images in Breeze using the WordPress ecosystem.

    The images are replaced by a dummy transparent image as placeholder and when it reaches the screen, the original image is loaded.

    The code recognizes the data-sizes and data-srcset attributes used for displaying the correct image size based on the resolution.

    The following attributes replace the original attributes:

    • data-breeze = src
    • data-brsrcset = data-srcset
    • data-brsizes = data- sizes

    The code will present two options for the users.

    1. The first option is the default Lazy-Load JavaScript based library, which will add an extra JS library to be loaded in the front-end.
    1. Native Lazy load option which does not used JavaScript, but it’s based on the browser engine. This functionality is recognized by around 70% of the browsers right now
    Thread Starter BeycanPress LLC

    (@beycanpress)

    Yes, the Native one can be used. However, because it causes late loading in the images at the beginning of the page, google drops a lot of points in the speed test.

    Plugin Author adeelkhan

    (@adeelkhan)

    Please share google points.

    • This reply was modified 1 year, 4 months ago by adeelkhan.
    Thread Starter BeycanPress LLC

    (@beycanpress)

    ? fixed everything about of speed in my site. Only this problem showing in W3C checker. Also, if i use native lazy loader “The loading of the large-scale image at the top of the page should not be delayed. He gives a warning in the style of spoiling large paint.” giving like that warning.

    Plugin Author adeelkhan

    (@adeelkhan)

    Great. Is there any point of conflict which you want to investigate by Breeze team?

    Thread Starter BeycanPress LLC

    (@beycanpress)

    As I said, if “breeze lazy loader” is selected, it will give a warning in accordance with W3C standards. I conveyed this in the picture.

    If “native lazy loader” is selected, Google will give a warning because it adds tags to the images while the page is loading at the very beginning of the screen.

    I think both cases need to be investigated and resolved.

    In case 1, the relevant data should be corrected using this site https://validator.w3.org/.

    In the 2nd case, the relevant warning should be resolved by using this site https://pagespeed.web.dev/

    Plugin Author adeelkhan

    (@adeelkhan)

    As we investigated but not able to replicate it. For further investigation ?it would be great if you contact our support and?create ticket?. We will investigate the point of conflict and also share to our users.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Need improve lazy loader’ is closed to new replies.