How To Load Images Like A Pro
Vložit
- čas přidán 21. 07. 2024
- Lazy Load Images Article: blog.webdevsimplified.com/202...
Images are the largest asset for most sites and the biggest cause for unresponsive, laggy sites. In this video I will show you how to use lazy loading to not only drastically speed up your applications, but to also increase the polish and quality of your site.
📚 Materials/References:
Lazy Load Images Article: blog.webdevsimplified.com/202...
Responsive Images Video: • Make Your Site Lightni...
Responsive Images Article: blog.webdevsimplified.com/202...
🌎 Find Me Here:
My Blog: blog.webdevsimplified.com
My Courses: courses.webdevsimplified.com
Patreon: / webdevsimplified
Twitter: / devsimplified
Discord: / discord
GitHub: github.com/WebDevSimplified
CodePen: codepen.io/WebDevSimplified
⏱️ Timestamps:
00:00 - Introduction
00:35 - What Is The Problem
02:17 - Lazy Loading Basics
05:15 - Advanced Blurry Loading
#LazyLoading #WDS #HTML
one of the things i like about you, is that you rarely use any framework/library for your videos and just focused on the fundamentals...! Keep it up.!
He does talk a lot about react tbf, but decent amount of vanilla videos.
He is the framework
I agree, prefer not to be bogged down with a framework, for what I do they're overkill.
yup, it helps to have more better understand, and get used to the logics
Hi Kail, thanks, good idea with pulse. And you can write in the keyframes 0%, 100% ... and 50%, instead repeat the same code.
I'm not that into front end side,
But video making of yours is brilliant!
I've even checked if I increased playback speed, but no, it was you talking at a good amount of speed, talking only about important stuff.
Visual demonstrations are on point also.
Thank you, good work.
Edit: 11:36 that is the fastest bug fixing I've ever seen haha
1. I'd add an additional blur filter to the low res images, either in the browser or when generating them. Just upscaling them kinda makes them look crappy as you get lots of "square gradients" (for a lack of a better word) interpolating between the pixels instead of a nice smooth blurry version.
2. As other have said, this effect is mostly already implemented into browsers/images. If you'd save the images as progressive, they'd automatically get sharper and sharper while they load, which requires less code and doesn't even need the download of the small image versions. However you could implement an additional blur effect on top of that while they're loading for a better effect, similar to what you've done in the video.
3. The solution you've given in the video is bad as someone with scripts disabled won't see the high-res versions at all. I'd add the CSS class that hides them until they're loaded also within JS.
Did not know about the loading attribute. It was very helpful for a website I develop. Thank you!
8:12 in addition to online tools most image asset CDN's have parameters , or a path, to serve specific image sizes.
Great easy to follow vid. The blur background idea is gold.
I love how this is detailed!!!
Been in web dev for 25 years, been a few since I was doing front end stuff. TIL some new to me properties, thanks!
Excellent video! Incredibly well explained, exceptionally well prepared! Thank you very much!
The process of generating and storing the blue placeholder js cumbersome - cloudinary really makes the whole thing a lot more cleaner.
Hi Kail, thanks, good idea with pulse.
Dude you're a blessing, thank you!
I love that the way you add lazy loading is how non-programmers think writing code is like.
"If you want lazy loading, type "loading = lazy". If you want a visitor to buy things, just add a button and write "action = complete transaction with credit card or payment service.""
That's the Declarative Paradigm of programming for you. It's all about letting you describe WHAT you want (leaving the HOW to the engine).
That is, you provide descriptions of what you want, piece by piece.
On the other hand, what people casually mean by "programming" tends to be the Imperative Paradigm. This is all about letting you describe HOW you want things done.
That is, you provide instructions, step by step.
Thanks this is so useful, I have started a e-commerce site and I will use this method for the product images
this method is more suite for showcase , img attribute srcset is better enough for your ecom site
Awesome tutorial, thanks Kyle.
This is an awesome way to load images. Great video!
It's better to use library for that
You're awesome, this was incredibly helpful.
Just what i was looking for, awesome
Amazing as always thank you so much man
exactly what I needed thank you
I was looking for EXACTLY this for my project.
Great video!
Thanks for this Video!
Great stuff thanks for sharing.
Great content! Thank you!
Thankyou much for sharing this awesome technique. ))))
Super cool, thank you
This is nice. Thank you dude.
I heard about it, but actually never used it ... But this actually seems pretty helpful. Keep it up. 😉🔥
Whose gonna do it? so much typing of extra code 😁 so much work. Just basic lazy loading is enough.
@@harris.sensorsoffline6419 I see you don't care about UX at all
@@Peshyy It won't be ideal, to work on a ldiotic Blur Image Lazy Load when native lazy load is faster & better.
@@harris.sensorsoffline6419 native lazy loading is still being used. the difference is that with one, you get images pop out of nowhere on slow networks; with the other - the images are placed where they should be, the user is visually aware there's an image there and how it should look like, and gets nice visual feedback that the image is being loaded.
calling it "idiotic blur image lazy load" shows a lot about you
@@Peshyy If you are working on a Gov Project that requires support for Slower Network & Older Browsers. You can't even support native lazy loading better luck with Tables to align those IMGs 😁.
Just kiddin, like you can convert all your images to webp with extreme compression & native lazy loading. Enough, to work good on all 4G Connections that most World runs on.
Very usefull video ! Thank you !
Nice, thank you!
Considering that jpeg encodes in 8x8 blocks, maybe 16x16 or 24x24 pixels would work better?
Web development wouldn't be where it's at without CZcams. Great video!
nah, without content creators
@@calimio6 nah, without internet
Did you ever hear about books? Or sites like MSDN?
@@merlinwarage Congrats on being a dick under a positive comment.
Also, dev books are 80% fluff, 20% content and MSDN is for boomers.
Thanks!
Amazing content!
Great video. Thanks.
Great video as usual. What do you think of the use of 'skeletons' while loading stuff. Is it any better than having to have multiples files of the same image but sized down?
Grest tutorial. Thank you
very helpfull content thankyou for sharing this.
I was waiting for this video.
Simply amazing explanation
That's awesome!
Ow man! You are awesome!
Great advice :)
you are such a genius!!
thank you
This guy is awesome!
The issue with this puts more load on the user and the server. You're loading multiple images at the end of the day. I would love to see if there could be a version where it automatically downscales itself, and builds upon itself. Great video!
The "load" of a
If you already know the image dimensions before loading it, then you should add the width and height attributes to you img. This avoids the annoying effect of seeing the content moving around during image loading
also known as CLS, which is Cumulative Layout Shift, which will impact the page SEO ranking
@@YuriG03042 What do you mean ? using width and height impact SEO ranking negatively?
@@thalisonamaral1642 It is the other way around. Not using width/height affects the SEO ranking negatively and increases the cumulative layout shift score. Google for "cumulative layout shift"
@@thalisonamaral1642 After 20 years fuckig around with Google bullshit I can tell you without a shadow of doubt that most all of these SEO tips are an utter waste of time and effort. If you ever look at some of the top ranking sites in highly saturated market you will see most of them are trash, a million console errors, dozens of tracking cookies, elements jumping around, interstitials and popups, bad semantics, too much advertising blocks, shallow content, meaningless content, duplicated content, I mean the list goes on.
@@rproctor83 no, it's just that being the thing people want is always most important.
But layout shift is still annoying for users period.
In the 90s with JPEG they would load exactly like you describe and they can because the the way jpegs are constructed using frequency data so you can load lower frequency components first making up a blurry pixelated image like you have slowly transitioning into the actual image as finally received and loaded
What you're describing is called Progressive JPEG, normal JPEG stores image block by block and cannot be rendered Progressively, but Progressive JPEG stores data from lower frequencies to higher ones, so it can load in an un-bluring manner
Yes, it's called jpeg 2000. Unlike regular jpeg, where they use Fourier transform, jpeg 2000 uses wavelet transform, which allows for better perceived image quality with smaller file size. Windows does not support it, but on a macOS you can save an image in jpeg 2000 format.
That was amazing
Very useful. King.
what a coincidence got this issue in my job task xD thanks a lot!
Welcome back
It was great and useful, thank you. How can I load the photos myself? For example, load photo number 3 first and then photo number 8?
nice tricks to load images thanks for sharing.
nice video! one thing I'd have done differently is, if you're using javascript anyways, I'd have set the small image style in the script itself too, to have the DOM be less cluttered
Also to make the no-scripts users see the actual picture eventually...
Cool!
I personally prefer not having extra markup. You can have the background image directly on the img tag. You wouldn't have the exact fade in animation you achieved but if you save your images with "progressive" turned on, they load in waves of less quality to more quality instead of top to bottom.
Also, I think that hiding images by default isn't very progressively enhanced. You could instead add a class when JS starts running to hide them, or the classic remove the .no-js class on the body.
Also, wouldn't it be more performant to do the pulse animation with opacity rather than changing the background color value? I think this can be done without extra markup as well (there's no need even for a pseudo element)
One more thing. In your example it doesn't really matter, but for regular block images (not on a grid like yours) lazy loading can cause layout shift.
To prevent this, you should specify each image width and height attributes.
What's more, if you have those values and you are dealing with responsive images, you could also set a style with --_img-width and --_img-height custom properties. This should be the pixel value without unit.
Then, in your CSS
img[loading="lazy"]{
max-width:100%;
height:auto;
aspect-ratio: var(--_img-width) / var(--_img-height);
}
while trying this out i ran into said issues and after struggling for 20 minutes I arrived at almost the same solution you gave except for the progressive part. Have no idea what that means. Can you please explain?
@@aniketpandey2524 Progressive images, supported since ages from jpg format include the small image Kyle generates inside the image itself. Also, the top-to-bottom loading is different on this kind of images - the same effect we're trying to have in the video, except that it is browser native, rather than using JS. I personally create the progressive images with the "export for web(legacy)" using the "progressive" option in Photoshop, but pretty sure you can find a free tool for that.
@@PhoenixXxXx91 oh! Now I got it. I thought he's talking about some new option in img tag of html.. 😅
@@aniketpandey2524 JPGs can be saved as "progressive" from photoshop. I'm sure there are other ways, but that's how I do it.
If you are going full on optimization you may also consider a tag with the image inside as a WEBP or any other modern web format; with the JPG fallback.
I don't know if WEBP has this "progressive" option.
I would also add a blur filter to smooth out those low res jpeg artifacts.
Thank god programming is like an open-book exam, you just need to know that it can be done and you will have Kyle here to help you do it
Your are the life saver....the (img.complete) one
What happened to progressive jpg anyway? That was a really cool feature built into the image...
It should still works, and it is much simpler than this.
That would still start the resource download on page load even if the image is 200 viewport a down.
You can lazy load progressive jpeg as well, and this way you're not wasting user's bandwidth for blurred images, image actually loads progressively and you won't have to manage two sets of assets
I was looking for this comment
Thank you for this very informative video .. pls do make a video for video loading time will be very helpful :)
At my job they really want us to improve the ligthouse scores. Have you done any tests to see what maximizes the lighthouse score (things like first/largest contentful paint)? I know you may even have to do strange stuff like not use external css files if your site has a really big one. I think it would be great if you could do a showcase of all the different ways to lazy load & optimize images and then show what kind of lighthouse scores they get (specifically on mobile, that's the killer). Thank you for this vid!
What is the right way to ensure that the placeholder div is the same size the image will be, once loaded, to avoid jerky reflow issues.
Thanks again man! can you made also one video about file types? webp and avif versus jpeg also svg can be nice
Thank you
😍 nice sir
❤❤❤thank you
question, does this have to do with downloading the image or rendering? Because wouldn’t it look better if it just shows an icon that its loading and then renders it instantly on the screen once it fetched it from the database (or wherever it came from)?
love the content
good video thanks
Web Dev is the best👍
thats what i want thanks very much i had same porblem in my real portfolio
Love this man, awesome video! Can you please do a vid on requestAnimationFrame()?
1. Would ".blur-load:not(.loaded)::before" work?
2. What do you think about "animation-direction: alternate"?
3. Setting the bg color to white and play with the opacity in the animation is another way to do it.
ok
very nice 🙂
Cool! 👍
I am curious to know, if we set content to none. But left animation there. Will it take any computation load as animations are cpu intensive.
Or browser intelligently will remove the animation property if no content is there
You are a savior :D
amazing
1. You can set background on an img itself. But I think it'll be impossible to add pulse over it.
2. Seems like progressive jpeg (especially with http2) could've solve the problem too?
3. 08:48 I like this more than blurry until load.
4. 10:30 It would be better to specify { once: true } so that it usubscribes after event occures.
Is this how you'd do this in React too? Or would you do it a different way?
So impressed with your skills, every single piece of content you produce. Just a heads up, that addEventListener will leak memory. Simplest fix would be to add an option argument with once:true.
Is that the third argument?
@@cookieman.19 Yes, add { once: true } for the third argument 👍
Does anyone know if it is possible to use lazy loading in addition to resolution switching? If so, is it considered good practice, or is it an unnecessary overkill?
Thanks, ill just use progressive jpegs.
Thank you next/image for not making having to write all of this :). Great video btw.
What if you are querying the images from a database, how would you implement the blur in case it takes time to load
awesome. so this means one can replace IntersectionObserver to lazy load images that come into view with this simple loading="lazy" trick?
Hey Kyle. The component in Next.js take care of this problem?
How to do it dynamically fetching from backend
Is there a reason to use ffmpeg over imagemagick? I was under the impression that ffmpeg is tailored for videos, and imagemagick for pictures.
No, he says as much (something like "there are tons of ways, use what ever you want")
I'm guessing he just had a good workflow set up for ffmpeg that he was familiar with, so he threw the images at it because he could :P
Please make a video about next image too? My problem is how to set height on dynamic images in next js without them losing the aspect ratio and keeping the responsiveness
This video is 🔥
Hey Kyle I've a question
According to you, what are the fundamental concepts of Computer science a web developer ( let's say full stack developer) should know ?
Thanks
Is it possible to lazy load in a sharp pixelated style. Because pixel-art aesthetic is really hip these days.
Yes
Yes you can
Well done guys, one more happy comentator that got his question answered
@@sanzharsuleimenov379 thank you
You can create a smaller pixelated version of your image and use that as the bg of the div.
Is there anyway to trigger Horizontal Intersection using the intersection Observer?
how would you be handling if the height is not fixed size of Img?
You could also throw a filter blur on it to make that pixilated small file look a little nicer
Actually, you are right, but when we use the 'Filter blur' effect on the mobile version, it feels laggy.
@@gowthammurugan6392 Interesting. Which part feels laggy?