Efficiently implement lazy loading of web page images: taking into account both responsiveness and performance
Have you ever considered lazy loading of images to optimize web page performance? Lazy loading technology can effectively reduce the load weight of the initial page and improve the loading speed of the web page. This article will explore an efficient image lazy loading method, while taking into account responsive images and the best user experience.
Lazy loading is not a browser native function, and it currently needs to be implemented with the help of JavaScript. Although Chrome 75 and subsequent versions plan to natively support lazy loading of images and iframes, we still need to use JavaScript solutions in order to be compatible with other browsers. Many static website generators, libraries, and frameworks provide lazy loading capabilities out of the box, but introducing a full library or framework just to implement this functionality can cause performance overhead. Therefore, we chose to implement lazy loading by ourselves.
Core mechanism:
Most lazy loading methods follow the following pattern:
HTML tags: Use
<img src="/static/imghw/default1.png" data-src="https://img.php.cn/upload/article/000/000/000/174502705448368.jpg" class="lazy" alt="Tips for rolling your own lazy loading">
Loading time: Use
Intersection Observer
API to detect whether the image enters the viewport.Intersection Observer
provides efficient element visibility detection, avoiding frequentscroll
andresize
event listening.
// Create Intersection Observer const observer = new IntersectionObserver(lazyLoad, { rootMargin: '100px', threshold: 1.0 }); function lazyLoad(elements) { elements.forEach(image => { if (image.intersectionRatio > 0) { image.src = image.dataset.src; observer.unobserve(image); } }); } // Observe all img elements with "lazy" class const lazyImages = document.querySelectorAll('img.lazy'); lazyImages.forEach(img => { observer.observe(img); });
Improvement and optimization:
There are some shortcomings in the above basic methods:
- JavaScript dependency: The image cannot be displayed until JavaScript is loaded and executed.
- Visual beating: The page is blank before the picture is loaded, which may cause visual dissatisfaction.
In response to the above issues, we have made the following improvements:
- Native lazy load detection: Use feature detection to determine whether the browser supports the native
loading="lazy"
attribute. If supported, use it directly without JavaScript intervention.
if ('loading' in HTMLImageElement.prototype) { document.querySelectorAll('img.lazy').forEach(img => img.src = img.dataset.src); } else { // Use Intersection Observer to implement lazy loading}
- Placeholder map and CSS transition: Use a small-size placeholder map as the initial state, and use CSS to scale and blur, remove the blur effect after the image is loaded to achieve a smooth transition.
<picture> <img src="/static/imghw/default1.png" data-src="https://img.php.cn/upload/article/000/000/000/174502705554652.jpg" class="lazy" alt="Tips for rolling your own lazy loading"> </picture>
picture { width: 100%; overflow: hidden; } picture img { width: 100%; transition: filter 0.5s; } picture.lazy img { filter: blur(20px); }
- Responsive picture: Use
<picture></picture>
Elements and<source></source>
Elements implement responsive pictures, loading pictures of different sizes according to different viewport sizes.
Auxiliary tools:
To simplify the development process, we can use the following auxiliary tools:
HTML generator: custom function or template engine assisted in generation
<picture></picture>
HTML code for the element.Image batch processing: Use tools such as
gulp-image-resize
to batch generate pictures of different sizes, or use cloud services (such as Netlify and Cloudinary) to convert pictures on demand.
Summarize:
This article introduces an efficient image lazy loading implementation method. By combining native lazy loading feature detection, placeholder map, CSS transition, responsive pictures and auxiliary tools, it can improve the user experience while ensuring performance. Choosing the right image processing method (build or on-demand conversion) depends on the project size and requirements. This method can significantly improve web page loading speed and provide smoother visual effects.
The above is the detailed content of Tips for rolling your own lazy loading. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
