Image SEO Audit: Find Every Image Problem Before Google and Your Visitors Do
Last updated October 18, 2026 · Built and maintained by the ImageFix team · Based on Google Search Central and web.dev guidance
This image SEO audit tool checks the five things that decide whether an image helps or hurts your page: its filename, alt text, dimensions, file size and format. It also checks loading behavior, such as lazy loading and the likely Largest Contentful Paint (LCP) image. Paste an HTML snippet, upload a CSV or JSON manifest, or drop your image files, and the tool returns a scored report with a specific fix for every issue.
SEO specialists use the report to prioritize quick wins on a site audit. Developers use it to catch oversized files and missing width and height attributes before launch. Content teams use it to fix weak alt text and generic filenames. Everything runs in your browser, so your HTML and images stay private.
How to Run an Image SEO Audit
- Choose your input. Select the HTML snippet tab, the Manifest tab (CSV or JSON), or the Image files tab.
- Add your data. Paste your markup or manifest, or drop image files. Optionally attach the real image files to an HTML snippet so the tool can read exact sizes and dimensions.
- Run the audit. Click Run audit. The tool scores every image and groups the findings by filename, alt text, dimensions, size, format and loading.
- Review and filter. Filter by errors, warnings or clean images, search by filename, and read the specific fix next to every issue.
- Fix and export. Copy suggested markup for each image, or export the report as Markdown, CSV or JSON for your team.
What the Image SEO Checker Looks For
| Area | What the tool flags | Why it matters |
|---|
| Filename | Generic names (IMG_4021.jpg), uppercase letters, spaces, special characters, underscores, very long or single-word names | Descriptive filenames give search engines light clues about the subject and keep URLs clean. |
| Alt text | Missing or empty alt, very short or very long text, "image of" openings, filename-style alt, keyword stuffing, duplicates, linked images with no name | Alt text makes images accessible and helps search engines understand them. |
| Dimensions | No width/height, ratio mismatch, files much wider than their display size, images wider than 2560 px | Reserved space prevents layout shift (CLS); right-sized files save bandwidth. |
| File size | Files above 200 KB (warning) and 500 KB (error) by default | Heavy images slow LCP and waste mobile data. |
| Format | Legacy JPG/PNG/GIF without a WebP or AVIF option, BMP/TIFF/HEIC, extension and file-type mismatch | Modern formats deliver the same look in fewer bytes. |
| Loading | Lazy-loaded first image, missing loading="lazy" below the fold, missing fetchpriority, JavaScript-only data-src | Correct loading order improves LCP and keeps images discoverable. |
The size and width thresholds are adjustable defaults rather than official limits. Google does not publish a maximum image size, so set the values that fit your own performance budget.
How the Audit Score Works
Each image starts with 100 points. The tool subtracts 15 points per error, 7 per warning and 2 per informational note, then averages the results into an overall score and a grade from A to F. The category bars show where the biggest gains hide: a low "Alt text" bar points to a content fix, while a low "File size" bar points to a compression job.
Image Filename Best Practices
Google's image SEO best practices recommend descriptive filenames because they hint at what an image shows. Follow four simple rules.
- Describe the subject. Write
red-running-shoes-side-view.jpg, not IMG_4021.jpg.
- Use lowercase and hyphens. Hyphens separate words clearly and avoid case-sensitivity problems on servers.
- Keep it short. Two to five meaningful words work best.
- Avoid spaces and symbols. They turn into
%20 and other encoded characters in URLs.
Alt Text Best Practices: Do and Don't
Do
- Describe what the image shows and why it matters on the page.
- Keep alt text to one natural sentence, ideally under 125 characters.
- Use
alt="" for purely decorative images.
- For linked images, describe the link destination.
Don't
- Start with "image of" or "picture of".
- Paste the filename into the alt attribute.
- Repeat keywords: "shoes, cheap shoes, buy shoes".
- Reuse one alt text across different images.
The W3C's alt decision tree walks you through choosing the right alt text for informative, decorative, functional and complex images.
Image Format Guide: JPG, PNG, WebP, AVIF, SVG and GIF
| Format | Best for | SEO and speed notes |
|---|
| AVIF | Photos and detailed graphics | Often the smallest files; serve with a fallback in <picture>. |
| WebP | Photos, graphics and simple animation | Widely supported; Google reports lossy WebP files around 25–34% smaller than comparable JPEGs. |
| JPG | Photos (fallback format) | Universal support; larger than WebP and AVIF. |
| PNG | Flat graphics, screenshots, transparency | Lossless and heavy for photos; consider WebP for transparency too. |
| SVG | Logos, icons, illustrations | Tiny, sharp at any size; compress and sanitize the markup. |
| GIF | Legacy animations only | Very heavy; replace with MP4/WebM or animated WebP/AVIF. |
Serve modern formats with a fallback so every browser can display your image. The WebP documentation explains the format in detail.
<picture>
<source srcset="trail-runner.avif" type="image/avif">
<source srcset="trail-runner.webp" type="image/webp">
<img src="trail-runner.jpg" alt="Trail runner crossing a wooden bridge"
width="1200" height="800" loading="lazy" decoding="async">
</picture>
Dimensions, Layout Shift and Responsive Images
Always set width and height to the image's intrinsic pixel size. The browser then reserves the correct space before the file arrives, which prevents the jumps that raise your Cumulative Layout Shift score. Read web.dev's guide to Cumulative Layout Shift for the full picture.
Then deliver the right pixels to each device. Use srcset and sizes so a phone downloads a 480 px file instead of a 2400 px one. MDN's responsive images guide shows the exact syntax. If a file is more than about twice as wide as its display size, resize it with the Image Resizer.
Lazy Loading Without Hurting LCP
Lazy loading saves bandwidth for images below the fold, but it backfires on your hero image. Follow this rule: never lazy-load the likely LCP image. Give it fetchpriority="high" instead, and lazy-load everything below the fold with loading="lazy". The web.dev articles on optimizing LCP and browser-level lazy loading explain why. Prefer native lazy loading over JavaScript-only data-src patterns so crawlers can always find the image.
A Simple Image SEO Audit Workflow
- Audit: run the tool on a template, a page or a media-library export.
- Fix errors first: missing alt text, non-web formats and files above your error threshold.
- Optimize files: compress with the Image Compressor and convert with the All-in-One Image Converter.
- Rename and rewrite: apply descriptive filenames and natural alt text.
- Re-audit: run the tool again, compare scores and export the report for your team.
Common Image SEO Mistakes
- Uploading camera or phone originals at 4000 px and 5 MB straight into a CMS.
- Writing alt text for search engines instead of for people.
- Lazy-loading the hero image and wondering why LCP is slow.
- Omitting
width and height, so the page jumps while it loads.
- Serving PNG for photographs where WebP or AVIF would cut the file size sharply.
- Hiding important images in CSS backgrounds, where they carry no alt text.
Frequently Asked Questions
What is an image SEO audit?
An image SEO audit reviews every image on a page or site for the signals that affect search visibility and page speed: descriptive filenames, useful alt text, correct dimensions, sensible file sizes and modern formats such as WebP and AVIF. The audit ends with a prioritized list of fixes.
What does this image SEO audit tool check?
The tool checks six areas: filename quality, alt text quality, dimensions (including width and height attributes and oversized images), file size, format (WebP, AVIF, legacy and non-web formats) and loading behavior such as lazy loading. Every image receives a score from 0 to 100, and the whole set receives an overall grade.
How does the tool audit an HTML snippet?
The tool parses your markup with the browser's built-in HTML parser and reads every <img> tag, including its alt, width, height, srcset, loading and fetchpriority attributes. It also reads the surrounding <picture> element to see whether you already serve WebP or AVIF sources.
Can the tool read file sizes from image URLs?
No. Browsers block cross-origin requests from a web page, so the tool cannot fetch your live images. To audit file size and pixel dimensions, attach the image files in the HTML tab, upload the files in the Image files tab, or add sizes to a CSV or JSON manifest.
Which manifest formats can I use?
You can paste or upload a CSV or JSON manifest. Recognized columns include src (or url, filename), width, height, size (bytes, or text such as "245 KB"), alt and format. Columns you leave out are skipped, never counted as failures.
Does the tool upload my images or HTML?
No. The audit runs 100% in your browser. Your HTML, manifests and image files never leave your device, so you can safely audit staging sites and unreleased pages.
How large should a web image be?
Google publishes no fixed size limit. The tool uses adjustable defaults: a warning above 200 KB and an error above 500 KB, plus a warning for images wider than 2560 px. Change these thresholds in the Settings panel to match your own performance budget.
Does every image need alt text?
Every image needs an alt attribute. Informative images need a short, specific description. Purely decorative images should use an empty alt="" so screen readers skip them. Images that act as links need alt text that describes the link destination.
Are WebP and AVIF better than JPG and PNG?
In most cases, yes. Google reports that lossy WebP files run roughly 25 to 34 percent smaller than comparable JPEGs, and AVIF often compresses further. Serve them through a <picture> element with a JPG or PNG fallback so every browser can display your image.
Should I lazy-load every image?
No. Lazy-load images below the fold, but never lazy-load the image that is likely your Largest Contentful Paint (LCP) element. Lazy-loading that image delays the metric you want to improve. The tool warns you when the first image on a page uses loading="lazy".
Do image filenames affect SEO?
Google's image guidance says descriptive filenames give light clues about the subject of an image. Filenames like red-running-shoes-side-view.jpg help both search engines and people, while IMG_4021.jpg tells them nothing.
How is the audit score calculated?
Each image starts at 100 points. The tool subtracts 15 points per error, 7 per warning and 2 per informational note. The overall score is the average across all images, and the grade runs from A (90 and above) to F (below 50).
What does the tool not cover?
The tool does not see CSS background images, images injected by JavaScript after page load, image sitemaps, or the real compression quality of a file. Treat the report as a fast first pass, then verify important pages with a full crawler or Lighthouse.
Related ImageFix Tools
Sources and Further Reading
