I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound.
First off, I'm a non-developer, so please tell me if you think I got any of this wrong...
I'd argue that lazy loading is a performance strategy that tries to anticipate user behavior. From Mozilla:
Lazy loading is a strategy to identify resources as non-blocking (non-critical) and load these only when needed. It's a way to shorten the length of the critical rendering path, which translates into reduced page load times
Lazy loading can occur on different moments in the application, but it typically happens on some user interactions such as scrolling and navigation.
If you think about lazy loading in the context of "scrolling", the site anticipates that a user is going to land on the page and see the assets that are at the top of the page and so it loads these first, only after scrolling down does the site load these other assets.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
First off, I'm a non-developer, so please tell me if you think I got any of this wrong...
I'd argue that lazy loading is a performance strategy that tries to anticipate user behavior. From Mozilla:
If you think about lazy loading in the context of "scrolling", the site anticipates that a user is going to land on the page and see the assets that are at the top of the page and so it loads these first, only after scrolling down does the site load these other assets.