An image SEO audit for every picture on the page.

Images go wrong in three ways: search engines and screen readers can't tell what they show, they're heavier than they need to be, or they push the layout around as they load. Each image gets pills for what's wrong, and you can filter the list by issue.

1. 1Alt text

   Missing, empty, over 125 characters, or just a file name like IMG_0042.jpg.

2. 2Width and height

   Without them the browser can't reserve space, and the page jumps (layout shift).

3. 3Lazy loading

   Lazy on the first images slows the page's main paint; eager on everything below wastes bandwidth.

4. 4File size

   Anything over 200 KB is worth a look. We read the real size from the server.

5. 5Format

   JPG, PNG and GIF where WebP or AVIF would be much smaller, unless a <picture> already offers one.

6. 6Oversized and vague files

   Files far bigger than they're displayed, and camera or hash filenames that say nothing.

Use an image pipeline. An image CDN, or a framework component like Next.js <Image>, converts to WebP or AVIF, resizes for each screen and adds width and height for you. That fixes four of the checks above at once.

Write alt text when you upload. It's easiest at the moment you choose the picture, and most CMSs have a field for it. Describe the image as you would to someone on the phone. Rename the file at the same time.

Treat the hero differently. The first big image is often the page's Largest Contentful Paint. Load it eagerly, give it fetchpriority="high", and keep it light. The Page Speed Checker shows whether it's the bottleneck.

Most AI crawlers read HTML, not pixels. To them, an image without alt text is a blank, and a chart or diagram with a good description is a fact they can use. Descriptive alt text and filenames also help Google Images, which is still a real source of traffic for products, recipes and places. For the rest of the page, run the On-Page SEO Checker.