Lazy Load Question & Answer

Hello @mentikyusmantara

Thank you for your inquiry and I am happy to answer this:

1. <noscript> increase the number of DOM nodes and negatively affect page speed score. Also, page size increased what affects network transferring time. At the same time, Google says it works well with intersection observer lazyloading implementation we use
https://developers.google.com/search/docs/guides/lazy-loading so we don’t generate them.
2. Not sure what you mean by that. Can you please clarify?
3. YOu can set image placeholders via hooks. SVG is what w3tc places by default.
4. It gives CSS class to all images it modifies, so you may set some background to that class.
I hope this helps!

Thanks your answer help all my question

1. I am not sure all bot can crawl the image, because its use Javascript. As i found, googlebot from now support Javascript. But i don’t know about another search engine.

And a notherhand There called dynamic rendering, i don’t much understand. But maybe can be considering about noscript tag.
https://developers.google.com/search/docs/guides/dynamic-rendering

2. Sorry for ambiguous question, i mean lazy threshold?

Thanks ??

Hello @mentikyusmantara

1. All modern bots parse it well, if you do care about something legacy – it can be implemented via user agent groups and hook to disable LL within that group. It would mean to increase page size for everyone just to make some single bot happy, and there is no reason for that.
As for the Lazy treshhold, thank you for the idea. I’ve opened an issue in our GitHub public repository on your behalf regarding this. Please make sure to check the progress of the issue on a regular basis.
Thank you!

@vmarko thanks, you recommendations about dynamic rendering is really helpful

Really want to know the progress of lazy threshold

Best Support ??