Wordpress LScache Plugin: Lazy load, placeholders, ToC and Gutenberg problem
Last Updated on: Wed, 15 Apr 2026 00:00:02 I have a problem with lazy load, image placeholders, Gutenberg WP Editor, and anchors to the post sections (Table of Content). In all posts, I have a Table of Content that links to the headers and sections of my post (h1, h2). But if I turn on lazy load, the links not working correctly and they scrolled to the random position of my post. Smooth scroll in CSS doesnt help. All because of the images that have not yet been loaded. The solution to the problem should be image placeholders that have height just like images in my posts, but Gutenberg in Image block doesnt add width and height parameter to . Even if I choose image dimensions in WordPress editor, the image is responsive (have scrset). Thats OK, but I think because of that, the lazy load cant generate a placeholder. So, links in my ToC linked to a random place of my post. How to solve this problem? Force Gutenberg somehow to auto add width/height to all images code? Or do something in lazy load code? I hope for your help. PS. I think thats can be a reason for my other problem (LQIP doesnt generate) ? https://wordpress.org/support/topic/responsive-placeholder-and-lqip-doesnt-work/ Hi, Could you please try only enable lazy load , and disable all other features , and see how it goes ? for placer holder , there is also an feature for responsive placeholder , you could give it a try . Best regards, @CacheCrawler I have a responsive placeholder turn on but its not work. This is my problem. And I think LQIP doesnt generate because the same reason (no height and width in HTML for images placed by Gutenberg) Hi, Yes, responsive placeholder and LQIP requires height/width in order to work. Best regards, @CacheCrawler ? So currently placeholder and LQIP dont work on all entries on all websites that use Gutenberg (95% of all WP users?). Is there a plan to do something about this in future releases? Or some trick to make it work for me? Hi, I have talked with dev about this , we will make some improvement for it. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference