Lazy loading, explained without the jargon

It comes up on almost every project, usually later than it should. Here is lazy loading without the vocabulary that usually surrounds it.

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. If two people in the business would answer this differently, that gap is the actual problem.

The short version

Only load what is about to be seen. This is the sort of thing that compounds, quietly, in both directions. Doing this properly once is usually cheaper than doing it approximately three times.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. None of that requires a large budget, only a decision and someone to own it.

Never lazy-load the main hero image. In practice this is a scheduling problem more than a technical one. Doing this properly once is usually cheaper than doing it approximately three times.

Where to go from here

Always reserve the space so nothing jumps. None of that requires a large budget, only a decision and someone to own it. Budget a little time for it every quarter and it never becomes a project of its own.

What this looks like day to day

Speed is a feature people notice only in its absence, and then they leave rather than complain. Three things worth confirming about lazy loading before you move on:

• Someone can say what the current setup is without going to look
• Only load what is about to be seen — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.