You run your website through PageSpeed Insights. The score is bad, and the diagnosis keeps pointing at the same thing: “Properly size images.” “Serve images in modern formats.” “Efficiently encode images.”

Three separate warnings, one root cause. Your photos are too big.

Not big in the way you’d notice — they look fine on screen. Big in the way a browser experiences them: files that weigh several megabytes each, delivered to a phone on mobile data, for a spot on the page that’s 400 pixels wide.

Images are the heaviest part of most small business websites. Fix them and the page gets faster than any other single change. Here’s what’s actually wrong, and what to do about each piece.

Problem 1: The photo is bigger than the space it fills

Your designer (or you, or your nephew) exported photos straight from the camera or stock site. A modern phone takes photos that are 4000+ pixels wide. The header image on your homepage displays at maybe 1900 pixels wide on a laptop, 400 on a phone.

So the browser downloads 4000 pixels of image, then throws away 90% of it to fit the screen. Every visitor pays that cost. Multiply by a homepage with five images.

How to check: open your homepage, right-click an image, and open it in a new tab. Look at the width of what loads versus the space it occupies on the page. If a header image loads at 4000px wide, it’s oversized.

The fix: resize images to the largest size they’ll actually display, then stop. A hero image rarely needs to be wider than 1920 pixels. A photo inside your text column? 800–1200 pixels is plenty. This one change can cut an image’s file size dramatically — often by more than half — with zero visible difference.

If you don’t have image editing software, free tools like Squoosh (squoosh.app) let you drag a photo in, set the width, and download the smaller version. No account, nothing to install. If you’re saving from Squoosh or any modern tool, WebP is usually one of the export options.

Problem 2: The format is wrong

There are three image formats that matter in 2026:

The common small-business mistake: photos saved as PNG because “it’s higher quality.” PNG is not better quality for photos — it’s a different tool for a different job, and for photos it produces files several times larger for no visible gain.

The fix: photos go WebP (or JPG at worst). Logos and screenshots with sharp lines can stay PNG. If you’re saving from Squoosh or any modern tool, WebP is usually one of the export options.

One exception worth knowing: your logo. If it’s a simple mark with few colors, SVG (a vector format) is even better — it stays sharp at every size and typically weighs a few kilobytes.

Problem 3: Everything loads at once

A visitor lands on your homepage. The browser starts downloading everything — including the photo of your team that’s three screens down, which the visitor may never scroll to.

That’s the default behavior. It’s also wasteful: the images below the visible area compete for bandwidth with the header image, the thing the visitor is actually looking at right now.

The fix is lazy loading, and it’s built into HTML now. Any image with loading="lazy" in its tag won’t download until the visitor scrolls near it. The header image loads instantly; the team photo loads when it’s about to matter.

You don’t need to hand-edit HTML for this — most modern website builders and templates add it automatically. (Every LiteInk template ships with lazy loading on below-the-fold images by default, precisely because it’s free speed.) But if your site is older or hand-built, it’s worth checking: view your page source, search for loading="lazy". If it’s not there on below-the-fold images, that’s a fix your developer can apply in minutes.

A note on “above the fold”

The first screen a visitor sees — your header, your headline, maybe a hero photo — should be the opposite of lazy. That image is the first impression, and you want it loading immediately. The standard advice: lazy-load everything below the fold, and make sure the top-of-page image is optimized so it loads fast eagerly.

This distinction matters because a common over-correction is to lazy-load everything, including the hero image. That makes your first paint slower, not faster.

The 20-minute checklist

If you do nothing else from this article, do this:

  1. Find your three heaviest images. Run your site through PageSpeed Insights and look at the Opportunities section — it lists images by estimated savings.
  2. Resize them to display size. Hero images max 1920px wide, content images 800–1200px.
  3. Convert photos to WebP. Squoosh handles this in two clicks per image.
  4. Check for lazy loading on everything below the first screen.
  5. Re-run PageSpeed. Compare before and after. The number will move.

None of this requires redesigning anything. The page looks identical — it just arrives faster.

Does this actually matter for a small business site?

Speed isn’t a vanity metric. It compounds with everything else:

If you want the full picture of what “fast enough” means, we’ve written about what a good load time actually is and how fast your site should load elsewhere.

But if you only fix one thing this month, fix your images. It’s the cheapest speed you’ll ever buy.