vanilla-lazyload VS stitchcounter

Vanilla-lazyload :

Hi all, I'm using verlok/vanilla-lazyload to make an image-based reader with thresholds: "200% 0px". The problem I'm facing is that it waits till the user scroll to load the following image and becomes slow to load images when fast scrolling. What I want to do is when the first image is loaded all the following images should load in order without relying on the user's scroll but if the reader jumps to the middle of the page then it should prioritize loading images around the reader's location. How can I achieve this? Or is there a better way to approach this issue?

Google recommends using a lazy loading library such vanilla-lazyload, or you can write your own JavaScript code.

If you want to guarantee lazy-load across all (JavaScript-capable) browsers and not just images, I've used Vanilla Lazyload a couple years ago with success, but as this relies on using a data-src attribute, you will get W3C validation errors unless you also set a src attribute. But you don't want to set the src to a real image, because this will nullify the whole point of using the plugin, so set it to a 1x1 pixel "image" that will immediately get replaced by the data-src once the image scrolls into view.

There are a lot of snippets and scripts like vanilla-lazyload out there that enable lazy-loading via javascript. In almost all cases a data attribute is used to prevent upfront image loading.

Right, time to put the base64 images to use. What you want to do is to use these as placeholders while the full image is loading. I usually use vanilla-lazyload for this. It is a simple and tiny project that gets the job done. Do mind that if you use Turbolinks you have to make sure that vanilla-lazyload does its thing after Turbolinks is done. If you use Webpacker it will look something like this in your application.js file:

I got a 500 error when I checked your site but for deployment tips... Running python manage.py check —deploy (or in some cases it’s python3... instead if python...) shows the deployment checklist of Django. You should also minimize and remove unused css and js. Try to research on purgecss and other similar web techs. Optimizing images is also important. I also saw that you are serving a lot of images from your readme in github so maybe you should consider lazyload.

There is a decent library to do the work for you. Only add some classes to your images and boom, they're already using the library. https://github.com/verlok/vanilla-lazyload

Try lazy loading, either using a js class (like https://github.com/verlok/vanilla-lazyload) or use the html lazy loading attribute (https://addyosmani.com/blog/lazy-loading/)

Fully open source at https://github.com/isaec/stitchcounter, and I don't stand to profit from its use in any way, so I hope it doesn't violate rule #2. I don't knit myself, so like I said, any feedback or feature requests would be great.