Think Build Implement Repeat
Web Development

Images Are Still the Biggest Cause of Slow Sites

Last updated:

Still the number one cause

Despite everything, oversized images remain the most common reason business sites are slow. A photograph straight from a camera is several megabytes and displays at 800 pixels wide.

The fix is unglamorous and reliable: resize, compress, use a modern format, and tell the browser the dimensions.

The four rules

  1. Resize to the display size, with a version for large screens and one for phones.
  2. Use modern formats — WebP or AVIF with a fallback. Typically half the size of a JPEG at the same quality.
  3. Set width and height in the markup, so the browser reserves space and the page does not jump as images load.
  4. Lazy-load below the fold, so the first screen does not wait for images nobody has scrolled to.
The width-and-height rule is the one people skip and the one that causes the most irritation. Layout that jumps while loading is what makes people tap the wrong thing.

The hero image deserves special treatment

The largest image on the first screen usually determines when the page feels loaded. It should be the priority download, correctly sized, and never lazy-loaded.

If it is a background image applied by CSS, the browser discovers it late. Preloading it, or using a real image element, measurably improves perceived speed.

Video, handled sensibly

  • Never autoplay with sound — it is universally disliked
  • Do not load a video player script until someone clicks play
  • Use a poster image so the space is filled immediately
  • Host on a video service rather than serving large files yourself
  • Consider whether the video earns its weight at all on a landing page

Give your team a workflow

Most image problems are introduced after launch by whoever uploads content. Either process images automatically on upload, or give the team a simple, documented routine with the target dimensions.

Automatic processing is better, because a routine that depends on discipline decays within a few months.

Frequently asked questions

Do we need a CDN for images?

For international audiences or image-heavy sites, yes, and many are inexpensive. For a local business with modest traffic, correct sizing matters far more.

What about retina displays?

Serve a higher-resolution version for high-density screens through responsive image markup. This is standard and handled automatically by most modern platforms.

Should we compress aggressively?

Compress until quality visibly suffers, then step back once. For photographs, substantial compression is usually invisible; for product images where detail matters, be more careful.

How much difference does this make?

On sites that have never addressed it, image work alone frequently halves page weight. It is the highest-return performance work available on most business sites.

Keep reading

Site slow and nobody sure why?

It is usually images. Send us the URL and we will tell you the page weight and where it is going.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Web DevelopmentCustom Software Development