Speed is the one feature nobody asks for and everybody notices. A page that paints in half a second feels like a product that has its house in order; a page that takes four seconds feels like a company that will be slow to answer your support email too. The frustrating part is that most sites are not slow because of anything clever. They are slow because of a handful of ordinary decisions, each defensible on its own.
Most of the weight is images
On a typical marketing page, images account for more transferred bytes than everything else put together. They are also the easiest thing to fix, because the fixes are mechanical rather than architectural: serve modern formats, size the file to the space it actually occupies, and let the browser skip anything below the fold until it is needed.
A hero photograph exported at 3000 pixels wide and displayed at 800 is not a small mistake. It is usually the single largest line item on the page.
Fonts block the first paint
Web fonts are the other common culprit, and they hurt in a sneakier way: the browser often has the text ready and simply refuses to show it until the font arrives. Every additional weight and style is another file. Two weights of one family, self-hosted and preloaded, will beat five weights fetched from a third party every time.
The checklist that covers most of it
Before reaching for anything exotic, work through the unglamorous list:
- Compress and resize every image to the largest size it is actually displayed at.
- Lazy-load anything below the fold, and only that — lazy-loading the hero makes things worse.
- Cut the font families and weights to what the design genuinely uses, then self-host them.
- Defer scripts that are not needed for the first screen, which is nearly all of them.
- Reserve space for images and embeds so the layout does not jump as they arrive.
Measure on the device people actually use
The most common self-deception in performance work is testing on a fast laptop over office wifi. Throttle the connection, throttle the processor, and look at the numbers again. A site that feels instant on a development machine and takes six seconds on a mid-range phone is not a fast site — it is a site that has only ever been measured somewhere flattering.
Performance is not a feature you add at the end. It is a budget you either keep or spend, one decision at a time.
Set the budget early — a page weight you will not exceed, a font count you will not pass — and most of these decisions make themselves.