Security News
UK Officials Consider Banning Ransomware Payments from Public Entities
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
vanilla-lazyload
Advanced tools
A fast, lightweight script to load images as they enter the viewport. SEO friendly, it supports responsive images (both srcset + sizes and picture) and progressive JPEG
LazyLoad is a fast, lightweight and flexible script that speeds up your web application by loading your content images, video, iframes as they enter the viewport. It's written in plain "vanilla" JavaScript, it uses the IntersectionObserver API, and it supports responsive images. It's also SEO-friendly and it has some other notable features.
ā”ļø Jump to: šØāš» Getting started - š„§ Recipes - šŗ Demos - š Tips & tricks - š API - šÆ Notable features
In order to make your content be loaded by LazyLoad, you must use some data-
attributes instead of the actual attributes. Examples below.
<img alt="A lazy image" data-src="sloth.jpg">
srcset
and sizes
:<img alt="A lazy image" class="lazy"
data-src="sloth.jpg"
data-srcset="sloth_400.jpg 400w, sloth_800.jpg 800w"
data-sizes="100w">
picture
tag:<picture>
<source
media="(min-width: 1200px)"
data-srcset="sloth_1200.jpg 1x, sloth_2400.jpg 2x">
<source
media="(min-width: 800px)"
data-srcset="sloth_800.jpg 1x, sloth_1600.jpg 2x">
<img alt="A lazy image" class="lazy"
data-src="sloth.jpg">
</picture>
picture
tag:<picture>
<source type="image/webp"
data-srcset="sloth_400.jpg 400w, sloth_800.jpg 800w"
data-sizes="100w">
<img alt="A lazy image" class="lazy"
data-src="sloth.jpg"
data-srcset="sloth_400.jpg 400w, sloth_800.jpg 800w"
data-sizes="100w">
</picture>
<div class="lazy" data-bg="url(sloth.jpg)"></div>
Note that to load images you to use url()
in the value of your data-bg
attribute.
<div class="lazy"
data-bg="url(sloth-head.jpg), url(sloth-body.jpg), linear-gradient(#fff, #ccc)">
...
</div>
<video class="lazy" controls width="620"
data-src="sloth.mp4" poster="sloth.jpg">
<source type="video/mp4" data-src="sloth.mp4">
<source type="video/ogg" data-src="sloth.ogg">
<source type="video/avi" data-src="sloth.avi">
</video>
<iframe class="lazy" data-src="slothFrame.html" poster="sloth.jpg"></iframe>
The latest version of LazyLoad is 11.0.2.
ā Read the note about versions and behaviour
The easiest way to use LazyLoad is to include the script from a CDN:
<script src="https://cdn.jsdelivr.net/npm/vanilla-lazyload@11.0.2/dist/lazyload.min.js"></script>
Then, in your javascript code:
var lazyLoadInstance = new LazyLoad({
elements_selector: ".lazy"
// ... more custom settings?
});
Be sure that DOM for your lazy content is ready when you instantiate LazyLoad. If you can't be sure, or other content may arrive in a later time via AJAX, you'll need to call lazyLoadInstance.update();
to make LazyLoad check the DOM again.
async
scriptIf you prefer, it's possible to include LazyLoad's script using async
script and initialize it as soon as it's loaded.
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 to make LazyLoad self-initialize
window.lazyLoadOptions = {
elements_selector: ".lazy",
// ... more custom settings?
};
// 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/vanilla-lazyload@11.0.2/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 lazyLoadInstance.update();
to make LazyLoad check the DOM again.
if (lazyLoadInstance) {
lazyLoadInstance.update();
}
Note about Internet Explorer
If you want to use asynchronous loading and need to store the instance in a variable, you need to include the following "polyfill" code to enable support for Internet Explorer.
This is because LazyLoad uses CustomEvent
(learn more) to trigger the LazyLoad::Initialized
event, but this is not natively supported by Internet Explorer.
(function () {
if (typeof window.CustomEvent === "function") {
return false;
}
function CustomEvent(event, params) {
params = params || {bubbles: false, cancelable: false, detail: undefined};
var evt = document.createEvent("CustomEvent");
evt.initCustomEvent (event, params.bubbles, params.cancelable, params.detail);
return evt;
}
CustomEvent.prototype = window.Event.prototype;
window.CustomEvent = CustomEvent;
})();
If you use RequireJS to dynamically load modules in your website, you can take advantage of it.
define("vanilla-lazyLoad", ["https://cdn.jsdelivr.net/npm/vanilla-lazyload@11.0.2/dist/lazyload.amd.min.js"], function (LazyLoad) {
return LazyLoad;
});
If you prefer to install LazyLoad locally in your project, you can!
npm install vanilla-lazyload
bower install vanilla-lazyload
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.
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.
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!
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 |
The latest, recommended version of LazyLoad is 11.0.2
.
IntersectionObserver
API, it will load your images as they enter the viewport.IntersectionObserver
, it will load all your lazy content immediately, unless you load an IntersectionObserver
polyfill like this one in your page (before LazyLoad). Using Polyfill.io is a way to do that.Legacy browsers support is from IE 9 up.
Version 8.x of LazyLoad still works and exists on npm, cdnjs and jsdelivr, and you still can load it conditionally (if you do that, like in this demo, you may use versions 8.17.0
/10.20.1
which have similar API), but doing so is being deprecated. The reason of is:
IntersectionObserver
support is very wide now, coming to Safari in the very next few days;scroll
event, while version 10.x uses IntersectionObserver
, so they behave differently (e.g. with sliders, or with different scrolling containers).The official w3c polyfill could be loaded conditionally on less recent versions of Safari and Internet Explorer, using Polyfill.io.
This is the section where you can find copy & paste code for your convenience.
š” 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.getElementById('scrollingPanel')
});
š” Use case: when your scrolling container is not the main browser window, and you have multiple scrolling containers.
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')
});
š” Use case: you want the images to stay inside the viewport for some time before to start loading them, e.g. to skip loading some images them if the user scrolled fast after them.
HTML
<img class="lazy" alt="A lazy image"
data-src="sloth.jpg"
width="220" height="280">
Javascript
var myLazyLoad = new LazyLoad({
elements_selector: ".lazy",
load_delay: 300 //adjust according to use case
});
š” 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();
š” Use case: when you have a lot of scrolling containers in the page and you want to instantiate a LazyLoad only on the ones that are in the viewport.
HTML
<div class="horzContainer">
<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="horzContainer">
<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 = [];
// The "lazyLazy" instance of lazyload is used (kinda improperly)
// to check when the .horzContainer divs enter the viewport
var lazyLazy = new LazyLoad({
elements_selector: ".horzContainer",
// When the .horzContainer div enters the viewport...
callback_set: function(el) {
// ...instantiate a new LazyLoad on it
var oneLL = new LazyLoad({
container: el
});
// Optionally push it in the lazyLoadInstances
// array to keep track of the instances
lazyLoadInstances.push(oneLL);
}
});
That's it. Whenever a .horzContainer
element enters the viewport, LazyLoad calls the callback_set
function, which creates a new instance of LazyLoad on the .horzContainer
element.
Didn't find the recipe that exactly matches your case? We have demos!
The demos folder contains 15 use cases of LazyLoad. You might find there what you're looking for.
You need to be sure that the containers of the images that are going to be lazy loaded occupy some vertical space. This because if the images have an initial height of 0
, all of them will probably be inside the viewport before time, so they will be loaded all at once.
In an elastic layout where images width change, you want to keep vertical space maintaining the images height, using a width/height ratio calculation.
.image-wrapper {
width: 100%;
height: 0;
padding-bottom: 66.67%; /* You define this doing 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.
There's also a useful SASS mixin to maintain aspect ratio on CSS tricks.
@mixin aspect-ratio($width, $height) {
position: relative;
&:before {
display: block;
content: "";
width: 100%;
padding-top: ($height / $width) * 100%;
}
> .content {
position: absolute;
top: 0;
left: 0;
right: 0;
bottom: 0;
}
}
Images should be shown while they load, and not after, to give your users the best perceived performance. This is especially true if you use a progressive loading format like Progressive JPEG.
In order to make your images visible as soon as LazyLoad sets the src
/srcset
attribute to it, you can either:
Do it like that via CSS:
/* Prevents img without src to appear */
img:not([src]) {
visibility: hidden;
}
Or instead of the above :not()
selector do it using the CSS classes of class_loading
and class_loaded
set by LazyLoad when loading starts or is completed - see API.
We do not recommend to use a placeholder image (like a transparent pixel GIF) in your HTML.
src
and srcset
attributes blank. Doing so, the image will be shown as soon as LazyLoad starts loading the image. See this video or this pen to test the difference (remember to disable the cache and to set a slower connection speed if you have a very fast one).It's safe not to put any value in the src
nor srcset
attributes, even if your HTML won't validate by a static code analyzer. The reason is that once JavaScript is executed, those values will be set by LazyLoad. For SEO, if the client is a crawler like Googlebot, it will be detected by LazyLoad which will fix the HTML.
According to what reported in #152, for Microsoft Edge to fire the IntersectionObserver for an img
element, it must have a size. Since img
s are displayed inline-block
as standard, MS Edge (version not specified) doesn't read them correctly.
By setting the following, edge is able to see the images and they get loaded.
img[data-src],
img[data-srcset] {
display: block;
min-height: 1px;
}
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 rare cases where you can't or don't want to select the elements using elements_selector
and you have a reference variable to your elements set (can be a NodeSet or an array of elements), you can pass the elements set as second parameter.
var elementsToLazyLoad = getElementSetFromSomewhere();
var aLazyLoad = new LazyLoad({
/* options here */
}, elementsToLazyLoad);
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 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. | "img" | ".images img.lazy" |
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 original image source, excluding the "data-" part. E.g. if your data attribute is named "data-src" , just pass "src" | "src" | "original" |
data_srcset | The name of the data attribute containing the original image source set in either img and source tags, excluding the "data-" part. E.g. if your data attribute is named "data-srcset" , just pass "srcset" | "srcset" | "original-set" |
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" | null |
data_bg | The name of the data attribute containing the value 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" | "url(img1.jpg), url(img2.jpg)" |
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" |
load_delay | The time (in milliseconds) each image needs to stay inside the viewport before its loading begins. | 0 | 300 |
auto_unobserve | A boolean that defines whether or not to automatically unobserve elements that was already revealed | true | false |
callback_enter | A callback function which is called when an element enters the viewport. | null | (el)=>{console.log("Entered", el)} |
callback_exit | A callback function which is called when an element exits the viewport. | null | (el)=>{console.log("Exited", el)} |
callback_reveal | A callback function which is called when an element is activated (usually when it starts loading). | null | (el)=>{console.log("Loading", el)} |
callback_loaded | A callback function which is called when an element was loaded. | null | (el)=>{console.log("Loaded", el)} |
callback_error | A callback function which is called when an element triggered an error. | null | (el)=>{console.log("Error", el)} |
callback_finish | A callback function which is called when there are no more elements to load and all elements have been downloaded. | null | ()=>{console.log("Finish")} |
You can call the following public methods on any instance of LazyLoad.
Method name | Effect |
---|---|
update() | Make LazyLoad to check for new lazy images in the container, using the elements_selector option. |
loadAll() | Loads all the lazy images right away, no matter if they are inside or outside the viewport. |
load(element, force) | Immediately loads any lazy element , even if it isn't selectable by the elements_selector option. Note that this method works only once on a specific element , unless you force it passing true as second parameter. |
destroy() | Destroys the instance, unsetting instance variables and removing listeners. |
LazyLoad doesn't hide your images from search engines, even if you don't specify any initial src
for your image.
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.
LazyLoad supports responsive images, both via the srcset
& sizes
attributes and via the picture
tag.
Progressive JPEG is an image format which is very good for perceived performance because it's rendered sooner, and refined in progressive passes. LazyLoad
shows your images while they load, letting progressive JPEG do its magic.
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.
This script is comparable to the notorious jQuery_lazyload, but LazyLoad is 10x faster, because LazyLoad uses only optimized, native javascript functions and methods, instead of jQuery.
This script is tested before every release using BrowserStack live, thanks to the BrowserStack Open Source initiative.
11.0.2
Applied a patch to resolve #293 a Chromium bug already fixed in Chrome 72. Thanks to @dverbovyi for the analysis and the report.
FAQs
LazyLoad 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 leve
The npm package vanilla-lazyload receives a total of 32,495 weekly downloads. As such, vanilla-lazyload popularity was classified as popular.
We found that vanilla-lazyload demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Ā It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.