JarCastingLazyLoad is a lightweight (2.4 kB) and flexible script that speeds up your web application by deferring the loading of your below-the-fold images, videos and iframes to when they will enter the viewport. It's written in plain "vanilla" JavaScript, it leverages the IntersectionObserver API, it supports responsive images, it optimizes your website for slower connections, and can enable native lazy loading. See notable features for more.
Love this project?
👨💻
Getting started - HTML
In order to make your content be loaded by LazyLoad, you must use some data- attributes instead of the actual attributes. Examples below.
Lazy image:
<img alt="A lazy image" class="lazy" data-src="lazy.jpg" />
Lazy image with low quality placeholder:
<img alt="A lazy image" class="lazy" src="lazy-lowQuality.jpg" data-src="lazy.jpg" />
Lazy responsive image with srcset and sizes:
<img
alt="A lazy image"
class="lazy"
data-src="lazy.jpg"
data-srcset="lazy_400.jpg 400w,
lazy_800.jpg 800w"
data-sizes="100w"
/>
To have a low quality placeholder, add the src attribute pointing to a very small version of the image. E.g. src="lazy_10.jpg".
Lazy responsive image with hi-dpi support using the picture tag:
<picture>
<source media="(min-width: 1200px)" data-srcset="lazy_1200.jpg 1x, lazy_2400.jpg 2x" />
<source media="(min-width: 800px)" data-srcset="lazy_800.jpg 1x, lazy_1600.jpg 2x" />
<img alt="A lazy image" class="lazy" data-src="lazy.jpg" />
</picture>
To have a low quality placeholder, add the src attribute pointing to a very small version of the image to the img tag. E.g. src="lazy_10.jpg".
Lazy responsive image with automatic WebP format selection, using the picture tag:
<picture>
<source
type="image/webp"
data-srcset="lazy_400.webp 400w,
lazy_800.webp 800w"
data-sizes="100w"
/>
<img
alt="A lazy image"
class="lazy"
data-src="lazy.jpg"
data-srcset="lazy_400.jpg 400w,
lazy_800.jpg 800w"
data-sizes="100w"
/>
</picture>
To have a low quality placeholder, add the src attribute pointing to a very small version of the image to the img tag. E.g. src="lazy_10.jpg".
Lazy background image
img tag. This would benefit the SEO and the accessibility of your website. To understand if your images are content or background, ask yourself: "would my website user like to see those images when printing out the page?". If the answer is "yes", then your images are content images and you should avoid using background images to display them.
Single background image:
<div class="lazy" data-bg="lazy.jpg"></div>
Single background, with HiDPI screen support:
<div class="lazy" data-bg="lazy.jpg" data-bg-hidpi="[email protected]"></div>
Multiple backgrounds:
<div
class="lazy"
data-bg-multi="url(lazy-head.jpg),
url(lazy-body.jpg),
linear-gradient(#fff, #ccc)"
>
...
</div>
url() to wrap the URLs in your data-bg-multi attributes.
Multiple backgrounds, HiDPI screen support:
<div
class="lazy"
data-bg-multi="url(lazy-head.jpg),
url(lazy-body.jpg),
linear-gradient(#fff, #ccc)"
data-bg-multi-hidpi="url([email protected]),
url([email protected]),
linear-gradient(#fff, #ccc)"
>
...
</div>
url() to wrap the URLs in your data-bg-multi-hidpi attributes.
Lazy video
<video class="lazy" controls width="620" data-src="lazy.mp4" data-poster="lazy.jpg">
<source type="video/mp4" data-src="lazy.mp4" />
<source type="video/ogg" data-src="lazy.ogg" />
<source type="video/avi" data-src="lazy.avi" />
</video>
Please note that the video poster can be lazily loaded too.
Lazy iframe
<iframe class="lazy" data-src="lazyFrame.html"> </iframe>
Love this project?
👩💻
Getting started - Script
The latest, recommended version of LazyLoad is 17.3.1.
Quickly understand how to upgrade from a previous version reading the practical upgrade guide.
To polyfill or not to polyfill IntersectionObserver?
On browser NOT supporting IntersectionObserver such as Internet explorer and older versions of Safari you can choose whether or not to add a javascript polyfill for it.
If you don't use a polyfill, LazyLoad will load all the images as soon as it's downloaded and executed. The number of impacted users would be relatively small, so this is a completely acceptable choice.
If you prefer to load a polyfill, the regular LazyLoad behaviour is granted.
The simple, easiest way
The easiest way to use LazyLoad is to include the script from a CDN:
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/lazyload.min.js"></script>
Or, with the IntersectionObserver polyfill:
<script src="https://cdn.jsdelivr.net/npm/[email protected]/intersection-observer.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/lazyload.min.js"></script>
Then, in your javascript code:
var lazyLoadInstance = new LazyLoad({
// Your custom settings go here
});
To be sure that DOM for your lazy content is ready when you instantiate LazyLoad, place the script tag right before the closing </body> tag. If more DOM arrives later, e.g. via an AJAX call, you'll need to call lazyLoadInstance.update(); to make LazyLoad check the DOM again.
lazyLoadInstance.update();
Include via RequireJS
You can use RequireJS to dynamically and asynchronously load modules in your website.
You can also find the original W3C'S IntersectionObserver Polyfill packed in AMD so you can require it conditionally, along with LazyLoad.
Include RequireJS:
<script src="https://cdn.jsdelivr.net/npm/[email protected]/bin/r.min.js"></script>
Then require the AMD version of LazyLoad, like this:
var lazyLoadAmdUrl = "https://cdn.jsdelivr.net/npm/[email protected]/dist/lazyload.amd.min.js";
var polyfillAmdUrl = "https://cdn.jsdelivr.net/npm/[email protected]/intersection-observer-amd.js";
/// Dynamically define the dependencies
var dependencies = [
"IntersectionObserver" in window
? null // <- Doesn't require the polyfill
: polyfillAmdUrl,
lazyLoadAmdUrl
];
// Initialize LazyLoad inside the callback
require(dependencies, function(_, LazyLoad) {
var lazyLoadInstance = new LazyLoad({
// Your custom settings go here
});
}
Using an async script
If you prefer, it's possible to include LazyLoad's script using async script and initialize it as soon as it's loaded.
To do so, you must define the options before including the script. You can pass:
{}an object to get a single instance of LazyLoad[{}, {}]an array of objects to get multiple instances of LazyLoad, each one with different options.
<script>
// Set the options globally
// to make LazyLoad self-initialize
window.lazyLoadOptions = {
// Your custom settings go here
};
</script>
Then include the script.
<script
async
src="https://cdn.jsdelivr.net/npm/[email protected]/dist/lazyload.min.js"
></script>
Possibly place the script tag right before the closing </body> tag. If you can't do that, LazyLoad could be executed before the browser has loaded all the DOM, and you'll need to call its update() method to make it check the DOM again.
Using an async script + getting the instance reference
Same as above, but you must put the addEventListener code shown below before including the async script.
<script>
// Set the options globally
// to make LazyLoad self-initialize
window.lazyLoadOptions = {
// Your custom settings go here
};
// Listen to the initialization event
// and get the instance of LazyLoad
window.addEventListener(
"LazyLoad::Initialized",
function (event) {
window.lazyLoadInstance = event.detail.instance;
},
false
);
</script>
Then include the script.
<script
async
src="https://cdn.jsdelivr.net/npm/[email protected]/dist/lazyload.min.js"
></script>
Now you'll be able to call its methods, like:
lazyLoadInstance.update();
Note about Internet Explorer: because this technique uses a CustomEvent to trigger the LazyLoad::Initialized event, you might want to add this polyfill to make it work on Internet Explorer.
DEMO - SOURCE ← for a single LazyLoad instance
DEMO - SOURCE ← for multiple LazyLoad instances
Local install
If you prefer to install LazyLoad locally in your project, you can!
Using npm
npm install vanilla-lazyload
Using bower
bower install vanilla-lazyload
Manual download
Download one the latest releases. The files you need are inside the dist folder. If you don't know which one to pick, use lazyload.min.js, or read about bundles.
Local usage
Should you install LazyLoad locally, you can import it as ES module like the following:
import LazyLoad from "vanilla-lazyload";
It's also possible (but unadvised) to use the require commonJS syntax.
More information about bundling LazyLoad with WebPack are available on this specific repo.
Usage with React
Take a look at this example of usage of React with LazyLoad on Sandbox.
This implementation takes the same props that you would normally pass to the img tag, but it renders a lazy image. Feel free to fork and improve it!
Bundles
Inside the dist folder you will find different bundles.
| Filename | Module Type | Advantages |
|---|---|---|
lazyload.min.js |
UMD (Universal Module Definition) | Works pretty much everywhere, even in common-js contexts |
lazyload.iife.min.js |
IIFE (Immediately Invoked Function Expression) | Works as in-page <script src="...">, ~0.5kb smaller than UMD version |
lazyload.amd.min.js |
AMD (Asynchronous Module Definition) | Works with RequireJS module loader, ~0.5kb smaller than UMD version |
lazyload.esm.js |
ES Module | Exports LazyLoad so you can import it in your project both using <script type="module" src="..."> and a bundler like WebPack or Rollup |
Love this project?
🥧
Recipes
This is the section where you can find ready to copy & paste code for your convenience.
Hide alt text and empty image
💡 Use case: when your lazily loaded images show theiralttext and the empty image icon before loading.
CSS
img:not([src]):not([srcset]) {
visibility: hidden;
}
Just that, really.
Dynamic content
💡 Use case: when you want to lazily load images, but the number of images change in the scrolling area changes, maybe because they are added asynchronously.
HTML
The HTML to use depends on your case, see other recipes' HTML
Javascript
var myLazyLoad = new LazyLoad();
// After your content has changed...
myLazyLoad.update();
Mixed native and JS-based lazy loading
💡 Use case: you want to use theuse_nativeoption to delegate the loading of images to the browsers engine where supported, but you also want to lazily load backgroud images or videos.
HTML
<img class="lazy" alt="A lazy image" data-src="lazy.jpg" />
<iframe class="lazy" data-src="lazyFrame.html"></iframe>
<video class="lazy" controls data-src="lazy.mp4" data-poster="lazy.jpg">...</video>
<div class="lazy" data-bg="lazy.jpg"></div>
Javascript
// Instance using native lazy loading
const lazyContent = new LazyLoad({
use_native: true // <-- there you go
});
// Instance without native lazy loading
const lazyBackground = new LazyLoad({
// DON'T PASS use_native: true HERE
});
Scrolling panel(s)
💡 Use case: when your scrolling container is not the main browser window, but a scrolling container.
HTML
<div class="scrollingPanel">
<!-- Set of images -->
</div>
Javascript
var myLazyLoad = new LazyLoad({
container: document.querySelector(".scrollingPanel")
});
If you have multiple scrolling panels, you can use the following markup and code.
HTML
<div id="scrollingPanel1" class="scrollingPanel">
<!-- Set of images -->
</div>
<div id="scrollingPanel2" class="scrollingPanel">
<!-- Set of images -->
</div>
Javascript
var myLazyLoad1 = new LazyLoad({
container: document.getElementById("scrollingPanel1")
});
var myLazyLoad2 = new LazyLoad({
container: document.getElementById("scrollingPanel2")
});
Lazy functions
💡 Use case: when you want to execute arbitrary scripts or functions when given elements enter the viewport
HTML
<div class="lazy" data-lazy-function="foo">...</div>
<div class="lazy" data-lazy-function="bar">...</div>
<div class="lazy" data-lazy-function="buzz">...</div>
<div class="lazy" data-lazy-function="booya">...</div>
JS
// It's a best practice to scope the function names inside a namespace like `lazyFunctions`.
window.lazyFunctions = {
foo: function (element) {
element.style.color = "red";
console.log("foo");
},
bar: function (element) {
element.remove(element);
console.log("bar");
},
buzz: function (element) {
var span = document.createElement("span");
span.innerText = " - buzz!";
element.appendChild(span);
console.log("buzz");
},
booya: function (element) {
element.classList.add("boo");
console.log("booya");
}
};
function executeLazyFunction(element) {
var lazyFunctionName = element.getAttribute("data-lazy-function");
var lazyFunction = window.lazyFunctions[lazyFunctionName];
if (!lazyFunction) return;
lazyFunction(element);
}
var ll = new LazyLoad({
unobserve_entered: true, // <- Avoid executing the function multiple times
callback_enter: executeLazyFunction // Assigning the function defined above
});
Use unobserve_entered to avoid executing the function multiple times.
That's it. Whenever an element with the data-lazy-function attribute enters the viewport, LazyLoad calls the executeLazyScript function, which gets the function name from the data-lazy-function attribute itself and executes it.
Lazy initialization of multiple LazyLoad instances
💡 Use case: when you have a lot of horizontally scrolling containers and you want to instantiate a LazyLoad instance on them, but only when they entered the viewport.
HTML
<div class="horizContainer">
<img
src=""
alt="Row 01, col 01"
data-src="https://placeholdit.imgix.net/~text?txtsize=19&txt=row_01_col_01&w=200&h=200"
/>
<img
src=""
alt="Row 01, col 02"
data-src="https://placeholdit.imgix.net/~text?txtsize=19&txt=row_01_col_02&w=200&h=200"
/>
<!-- ... -->
</div>
<div class="horizContainer">
<img
src=""
alt="Row 02, col 01"
data-src="https://placeholdit.imgix.net/~text?txtsize=19&txt=row_02_col_01&w=200&h=200"
/>
<img
src=""
alt="Row 02, col 02"
data-src="https://placeholdit.imgix.net/~text?txtsize=19&txt=row_02_col_02&w=200&h=200"
/>
<!-- ... -->
</div>
Javascript
var lazyLoadInstances = [];
var initOneLazyLoad = function (horizContainerElement) {
// When the .horizContainer element enters the viewport,
// instantiate a new LazyLoad on the horizContainerElement
var oneLL = new LazyLoad({
container: horizContainerElement
});
// Optionally push it in the lazyLoadInstances
// array to keep track of the instances
lazyLoadInstances.push(oneLL);
};
// The "lazyLazy" instance of lazyload is used to check
// when the .horizContainer divs enter the viewport
var lazyLazy = new LazyLoad({
elements_selector: ".horizContainer",
callback_enter: initOneLazyLoad,
unobserve_entered: true // Stop observing .horizContainer(s) after they entered
});
That's it. Whenever a .horizContainer element enters the viewport, LazyLoad calls the initOneLazyLoad function, which creates a new instance of LazyLoad on the .horizContainer element.
Love this project?
📺
Demos
Didn't find the recipe that exactly matches your case? We have demos!
The demos folder contains 30+ use cases of vanilla-lazyload. You might find there what you're looking for.
| Type | Title | Code | Demo |
|---|---|---|---|
| Content | Simple lazy loaded images, not using any placeholder | Code | Live |
| Content | Lazy images that use an inline SVG as a placeholder | Code | Live |
| Content | Lazy images that use an external SVG file as a placeholder | Code | Live |
| Content | Lazy responsive images with srcset |
Code | Live |
| Content | Lazy responsive images with the <picture> tag and the media attribute (art direction) |
Code | Live |
| Content | Lazy responsive images with srcset and sizes (using data-sizes) |
Code | Live |
| Content | Lazy responsive images with srcset and sizes (using plain sizes) |
Code | Live |
| Content | Lazy video with multiple <source> tags |
Code | Live |
| Content | Lazy loading background images | Code | Live |
| Content | Lazy loading multiple background images | Code | Live |
| Content | Lazy WebP images with the <picture> tag and the type attribute for WebP |
Code | Live |
| Loading | Asynchronous loading LazyLoad with requireJS | Code | Live |
| Loading | Asynchronous loading LazyLoad + InterserctionObserver with requireJS | Code | Live |
| Loading | Asynchronous loading LazyLoad with <script async> |
Code | Live |
| Loading | Asynchronous loading multiple LazyLoad instances with <script async> |
Code | Live |
| Technique | Fade in images as they load | Code | Live |
| Technique | Lazily create lazyload instances | Code | Live |
| Technique | Lazily execute functions as specific elements enter the viewport | Code | Live |
| Technique | How to manage the print of a page with lazy images | Code | Live |
| Technique | A popup layer containing lazy images in a scrolling container | Code | Live |
| Settings | Multiple scrolling containers | Code | Live |
| Settings | Single scrolling container | Code | Live |
| Methods | How to destroy() LazyLoad |
Code | Live |
| Methods | Adding dynamic content, then update() LazyLoad |
Code | Live |
| Methods | Adding dynamic content, then update() LazyLoad passing a NodeSet of elements |
Code | Live |
| Methods | Load punctual images using the load() method |
Code | Live |
| Methods | Load all images at once using loadAll() |
Code | Live |
| Test | Test for multiple thresholds | Code | Live |
| Test | Test behaviour with hidden images | Code | Live |
| Test | Test performance, lazy loading of hundreds of images | Code | Live |
| Native | Test the native lazy loading of images WITHOUT any line of javascript, not even this script | Code | Live |
| Native | Test the native lazy loading of images conditionally using the use_native option (see API) |
Code | Live |
Love this project?
😋
Tips & tricks
Occupy space and avoid content reflow
It's a good idea to make sure that your lazy images occupy some space even before they are loaded, otherwise the img elements will be shrinked to zero-height, causing your layout to reflow and making lazyload inefficient.
There are many ways to avoid content reflow. I've tested three of them and found that the fastest is to avoid using a placeholder at all, and use the vertical padding trick.
Vertical padding trick
<div class="image-wrapper">
<img class="lazy image" alt="An image" data-src="lazy.jpg" />
</div>
.image-wrapper {
width: 100%;
height: 0;
padding-bottom: 150%;
/* 👆 image height / width * 100% */
position: relative;
}
.image {
width: 100%;
height: auto;
position: absolute;
}
More info in Sizing Fluid Image Containers with a Little CSS Padding Hack by Andy Shora. Find also a useful SASS mixin to maintain aspect ratio on CSS tricks.
Inline SVG
If you can't use the vertical padding trick for some reason, the best option is to use an SVG placeholder of the same ratio of the lazy images.
<img
src="data:image/svg+xml,%3Csvg
xmlns='http://www.w3.org/2000/svg'
viewBox='0 0 3 2'%3E%3C/svg%3E"
data-src="//picsum.photos/900/600"
alt="Lazy loading test image"
/>
Alternatively (but less efficiently) you can use a tiny, scaled-down version of your images as a placeholder, stretching them to the final size of the images, and obtain a blur-up effect when the full images load.
Using a placeholder image will also make sure that browsers don't show your alt content instead of the images before the lazy-loading starts.
Love this project?
🔌
API
Constructor arguments
The new LazyLoad() instruction you execute on your page can take two parameters:
| Parameter | What to pass | Required | Default value | Type |
|---|---|---|---|---|
| Options | The option object for this instance of LazyLoad | No | {} |
Plain Object |
| Nodeset | A NodeSet of elements to execute LazyLoad on | No | null |
NodeSet |
The most common usage of LazyLoad constructor is to pass only the options object (see "options" in the next section). For example:
var aLazyLoad = new LazyLoad({
/* options here */
});
In the unusual cases when you can't select the elements using elements_selector, you could pass the elements set as a second parameter. It can be either a NodeSet or an array of DOM elements.
var elementsToLazyLoad = getElementSetFromSomewhere();
var aLazyLoad = new LazyLoad(
{
/* options here */
},
elementsToLazyLoad
);
Options
For every instance of LazyLoad you can pass in some options, to alter its default behaviour. Here's the list of the options.
| Name | Meaning | Default value | Example value |
|---|---|---|---|
container |
The scrolling container of the elements in the elements_selector option. |
document |
document.querySelector('.scrollPanel') |
elements_selector |
The CSS selector of the elements to load lazily, which will be selected as descendants of the container object. |
".lazy" |
".lazyload" |
threshold |
A number of pixels representing the outer distance off the scrolling area from which to start loading the elements. | 300 |
0 |
thresholds |
Similar to threshold, but accepting multiple values and both px and % units. It maps directly to the rootMargin property of IntersectionObserver (read more), so it must be a string with a syntax similar to the CSS margin property. You can use it when you need to have different thresholds for the scrolling area. It overrides threshold when passed. |
null |
"500px 10%" |
data_src |
The name of the data attribute containing the element URL to load, excluding the "data-" part. E.g. if your data attribute is named "data-src", just pass "src" |
"src" |
"lazy-src" |
data_srcset |
The name of the data attribute containing the image URL set to load, in either img and source tags, excluding the "data-" part. E.g. if your data attribute is named "data-srcset", just pass "srcset" |
"srcset" |
"lazy-srcset" |
data_sizes |
The name of the data attribute containing the sizes attribute to use, excluding the "data-" part. E.g. if your data attribute is named "data-sizes", just pass "sizes" |
"sizes" |
"lazy-sizes" |
data_bg |
The name of the data attribute containing the URL of background-image to load lazily, excluding the "data-" part. E.g. if your data attribute is named "data-bg", just pass "bg". The attribute value must be a valid value for background-image, including the url() part of the CSS instruction. |
"bg" |
"lazy-bg" |
data_bg_hidpi |
The name of the data attribute containing the URL of background-image to load lazily on HiDPI screens, excluding the "data-" part. E.g. if your data attribute is named "data-bg-hidpi", just pass "bg-hidpi". The attribute value must be a valid value for background-image, including the url() part of the CSS instruction. |
"bg-hidpi" |
"lazy-bg-hidpi" |
data_bg_multi |
The name of the data attribute containing the value of multiple background-image to load lazily, excluding the "data-" part. E.g. if your data attribute is named "data-bg-multi", just pass "bg-multi". The attribute value must be a valid value for background-image, including the url() part of the CSS instruction. |
"bg-multi" |
"lazy-bg-multi" |
data_bg_multi_hidpi |
The name of the data attribute containing the value of multiple background-image to load lazily on HiDPI screens, excluding the "data-" part. E.g. if your data attribute is named "data-bg-multi-hidpi", just pass "bg-multi-hidpi". The attribute value must be a valid value for background-image, including the url() part of the CSS instruction. |
"bg-multi-hidpi" |
"lazy-bg-multi-hidpi" |
data_poster |
The name of the data attribute containing the value of poster to load lazily, excluding the "data-" part. E.g. if your data attribute is named "data-poster", just pass "poster". |
"poster" |
"lazy-poster" |
class_applied |
The class applied to the multiple background elements after the multiple background was applied | "applied" |
"lazy-applied" |
class_loading |
The class applied to the elements while the loading is in progress. | "loading" |
"lazy-loading" |
class_loaded |
The class applied to the elements when the loading is complete. | "loaded" |
"lazy-loaded" |
class_error |
The class applied to the elements when the element causes an error. | "error" |
"lazy-error" |
class_entered |
The class applied to the elements after they entered the viewport. | "entered" |
"lazy-entered" |
class_exited |
The class applied to the elements after they exited the viewport. This class is removed if an element enters the viewport again. The unobserve_entered option can affect the appliance of this class, e.g. when loading images that complete loading before exiting. |
"exited" |
"lazy-exited" |
cancel_on_exit |
A boolean that defines whether or not to cancel the download of the images that exit the viewport while they are still loading, eventually restoring the original attributes. It applies only to images so to the img (and picture) tags, so it doesn't apply to background images, iframes nor videos. |
true |
false |
unobserve_entered |
A boolean that defines whether or not to automatically unobserve elements once they entered the viewport | false |
true |
unobserve_completed |
A boolean that defines whether or not to automatically unobserve elements once they've loaded or throwed an error | true |
false |
callback_enter |
A callback function which is called whenever an element enters the viewport. Arguments: DOM element, intersection observer entry, lazyload instance. | null |
(el)=>{console.log("Entered", el)} |
callback_exit |
A callback function which is called whenever an element exits the viewport. Arguments: DOM element, intersection observer entry, lazyload instance. | null |
(el)=>{console.log("Exited", el)} |
callback_loading |
A callback function which is called whenever an element starts loading. Arguments: DOM element, lazyload instance. | null |
(el)=>{console.log("Loading", el)} |
callback_cancel |
A callback function which is called whenever an element loading is canceled while loading, as for cancel_on_exit: true. |
null |
(el)=>{console.log("Cancelled", el)} |
callback_loaded |
A callback function which is called whenever an element finishes loading. Note that, in version older than 11.0.0, this option went under the name callback_load. Arguments: DOM element, lazyload instance. |
null |
(el)=>{console.log("Loaded", el)} |
callback_error |
A callback function which is called whenever an element triggers an error. Arguments: DOM element, lazyload instance. | null |
(el)=>{console.log("Error", el)} |
callback_applied |
A callback function which is called whenever a multiple background element starts loading. Arguments: DOM element, lazyload instance. | null |
(el)=>{console.log("Applied", el)} |
callback_finish |
A callback function which is called when there are no more elements to load and all elements have been downloaded. Arguments: lazyload instance. | null |
()=>{console.log("Finish")} |
use_native |
This boolean sets whether or not to use native lazy loading to do hybrid lazy loading. On browsers that support it, LazyLoad will set the loading="lazy" attribute on images and iframes, and delegate their loading to the browser. |
false |
true |
Methods
Instance methods
You can call the following methods on any instance of LazyLoad.
| Method name | Effect | Use case |
|---|---|---|
update() |
Make LazyLoad to re-check the DOM for elements_selector elements inside its container. |
Update LazyLoad after you added or removed DOM elements to the page. |
loadAll() |
Loads all the lazy elements right away and stop observing them, no matter if they are inside or outside the viewport, no matter if they are hidden or visible. | To load all the remaining elements in advance |
destroy() |
Destroys the instance, unsetting instance variables and removing listeners. | Free up some memory. Especially useful for Single Page Applications. |
Static methods
You can call the following static methods on the LazyLoad class itself (e.g. LazyLoad.load(element, settings)).
| Method name | Effect | Use case |
|---|---|---|
load(element, settings) |
Immediately loads the lazy element. You can pass your custom options in the settings parameter. Note that the elements_selector option has no effect, since you are passing the element as a parameter. Also note that this method has effect only once on a specific element. |
To load an element at mouseover or at any other event different than "entering the viewport" |
resetStatus(element) |
Resets the internal status of the given element. |
To tell LazyLoad to consider this element again, for example if you changed the data-src attribute after the previous data-src was loaded, call this method, then call update(). |
Properties
You can use the following properties on any instance of LazyLoad.
| Property name | Value |
|---|---|
loadingCount |
The number of elements that are currently downloading from the network (limitedly to the ones managed by the instance of LazyLoad). This is particularly useful to understand whether or not is safe to destroy this instance of LazyLoad. |
toLoadCount |
The number of elements that haven't been lazyloaded yet (limitedly to the ones managed by the instance of LazyLoad) |
Love this project?
😯
Notable features
It works with your favourite library or framework
As LazyLoad doesn't rely on jQuery, you can use it in web applications using Angular, React or Vue.js without the need to include jQuery.
Intersection Observer API for optimized CPU usage
Instead of listening to the scroll and resize events, LazyLoad uses the Intersection Observer API which is a new, blazing fast method to detect if an element is inside the browser viewport. Your users will see the difference in slow and even in fast devices or computers.
SEO friendly
LazyLoad doesn't hide your images from search engines, even if you don't specify any initial src for your image.
Flaky connections supported
If your users lose the internet connection causing errors on images loading, this script tries and loads those images again when the connection is restored.
Optimize for slow connections
LazyLoad optimizes for slow connections by cancelling the download of images when they exit the viewport.
Support for responsive images
LazyLoad supports responsive images, both via the srcset & sizes attributes and via the picture tag.
Support for single and background images, and HiDPI displays
LazyLoad supports single and multiple lazy background images, with standard resolution or HiDPI (retina) displays.
Tested on real browsers
Legacy browsers support is from IE 9 up. This script is tested in every browser before every release using BrowserStack live, thanks to the BrowserStack Open Source initiative.
Love this project?