Enter a URL and the audit reads your pages the way a search engine crawler does, downloads every image it finds to measure its real size, format and dimensions, and lists each problem with the HTML that caused it, why it matters and how to fix it.
Public websites only. The scanner identifies itself as “ImageMagixImageAudit”, follows robots.txt, and downloads each image to measure it.
Images are usually the heaviest part of a web page, and they are often where accessibility and SEO problems hide: alt text that is missing or just a file name, broken image URLs, photos several times larger than the space they fill, or a hero image that is lazy-loaded and delays Largest Contentful Paint.
Most of these problems are invisible when you look at the page, so they are easy to miss. This audit checks every image on up to 50 pages and shows you the evidence for each issue, so you can fix the ones that matter most first.

Missing alt, file names or generic words used as alt, very long or repeated alt text, image links and buttons with no accessible name, and SVGs with role="img" but no title.
File size against role-based budgets, images larger than their display size, missing srcset/sizes, legacy formats with an estimated WebP saving, lazy-loading and fetchpriority on the likely LCP image, missing width/height, cache headers and SVG compression.
Missing, relative or small og:image, structured data without an image, and non-descriptive file names such as IMG_1234.jpg.
Broken images (4xx/5xx), URLs that don’t return an image, unreachable hosts, redirect chains, mixed content on HTTPS pages and formats most browsers can’t display.
Paste a page or your home page. You can leave out https://.
Scan just that page, or up to 10, 25 or 50 pages found through your sitemap and internal links.
Pages and images are checked in parallel and issues appear as they are found. You can cancel at any time and keep what has been scanned.
Review issues by type, by page or image by image, then export a CSV, JSON or PDF report.
| Image role | How the audit decides | Budget | High severity above |
|---|---|---|---|
| Icon or logo | A favicon, or an image 96 px or smaller | 20 KB | 50 KB |
| Thumbnail | At most 480 px wide, or displayed at 300 px or less | 100 KB | 250 KB |
| Content image | Any other image in the page content | 250 KB | 625 KB |
| Hero (likely LCP) image | The large image near the top that is probably the LCP element | 400 KB | 1000 KB |
| Background image | Set with an inline CSS background-image | 400 KB | 1000 KB |
| Social / metadata image | og:image, twitter:image or a structured-data image | 600 KB | 1.46 MB |
A website image audit is a check of every image on your site for the three things images most often get wrong: page speed (files that are too heavy or too large for where they are shown), image SEO (missing alt text, unhelpful file names, missing social preview images) and accessibility (images and image links that screen reader users can’t understand). It also catches outright errors such as broken image links and images loaded over insecure HTTP.
General SEO audit tools and website speed tests usually report images as a single line item, such as “properly size images” for one page. An image-focused audit goes further: it lists each image once (even if it appears on 50 pages), shows the exact HTML that caused each problem, and gives you a fix you can hand to a developer or content editor.
Google’s Core Web Vitals measure loading (Largest Contentful Paint, LCP), visual stability (Cumulative Layout Shift, CLS) and responsiveness (Interaction to Next Paint). Google recommends an LCP of 2.5 seconds or less and a CLS of 0.1 or less for at least 75% of page visits. Images play a direct part in the first two.
On many pages the LCP element is an image: a hero banner, a product photo or a featured blog image. Anything that delays that one image delays LCP. The most common causes are a file that is far heavier than it needs to be, an image that is lazy-loaded even though it is at the top of the page, and an image that the browser discovers late or downloads at low priority.
Layout shift happens when an image loads and pushes the content below it down the page. The fix is simple: give every image width and height attributes (or a CSS aspect-ratio) so the browser reserves the right amount of space before the file arrives.
Large images are the most common reason a website feels slow on mobile data. There are two different problems, and they need different fixes. The first is a heavy file: a photo saved at maximum quality or in an old format. The second is an oversized image: a 4000-pixel-wide photo displayed in a 600-pixel-wide column, so most of the downloaded pixels are thrown away.
The audit measures the real byte size of every image from its server and compares it with a budget for how the image is used (the table above), so a 150 KB hero photo passes while a 150 KB icon is flagged. It also reads each file’s real pixel dimensions and compares them with the display width given in the HTML (the width attribute, srcset and sizes). When an image is more than 1.5 times wider than it needs to be even for a high-density (2×) screen, it is reported with an estimated saving.
To fix heavy files, compress them with the Image Compressor or target an exact size, for example with compress image to 100KB. To fix oversized images, resize them to about twice their display width with the Image Resizer.
Image optimization is a short list of habits that, together, usually remove most of a page’s image weight without any visible loss in quality:
srcset with a matching sizes attribute so phones download a small file and desktops a larger one.loading="lazy" for images further down, never for the main image at the top.Cache-Control max-age and change the file name when the image changes.Search engines understand images mainly from the text around them. Google’s image SEO guidance highlights descriptive alt text, descriptive file names, the page content near the image, and making sure images are crawlable. Good image SEO helps your pages appear in Google Images and in image-rich search results, which can be a meaningful source of organic traffic for ecommerce, recipe, travel and how-to sites.
Good alt text describes what the image shows in the context of the page, in plain language, without stuffing keywords. “Red trail running shoe, side view” helps both screen reader users and search engines; “shoe running shoes best running shoes buy” helps no one and can look like spam. File names work the same way: red-trail-running-shoe.webp is a small, useful signal, while IMG_2041.jpg is not.
Social previews matter too. When someone shares your page on Facebook, LinkedIn, X or WhatsApp, the preview image comes from the og:image tag. Pages without one, or with a relative URL or a tiny image, get a poor preview or none at all.
Every image needs an alt attribute, but not every image needs alt text. The W3C’s guidance comes down to one question: what would you say about this image if you were reading the page aloud?
alt="" so screen readers skip them. The audit treats this as correct.WCAG success criterion 1.1.1 (Non-text Content) requires a text alternative for images that convey information, and image links and buttons need an accessible name so that people using screen readers know where they lead. Missing alt text and unlabeled icon links are among the most common problems found in web accessibility audits.
This audit checks the image-related parts of accessibility that can be detected reliably from HTML: missing alt attributes, unhelpful alt text, links and buttons whose only content is an unlabeled image or SVG, and SVGs marked role="img" without a title or label. It is not a full accessibility or ADA/WCAG compliance audit: colour contrast, keyboard navigation and whether alt text is actually accurate still need a human review.
A broken image shows visitors an empty box or a broken-image icon, and it wastes search engine crawl time. Images break when files are deleted or renamed, when a site moves to a new domain or CDN, or when a URL in a CMS is mistyped. The audit requests every image and reports any 4xx or 5xx response as broken, along with the pages that use it.
It also reports URLs that answer successfully but don’t return an image (often an HTML error page), image hosts that can’t be reached, redirect chains, insecure http:// images on https:// pages (mixed content) and formats most browsers can’t show, such as HEIC and TIFF. When an image server rate-limits or blocks the scanner, those images are listed as “couldn’t be checked”, never as broken, so you don’t chase problems that visitors don’t have.
WordPress generates several sizes of every upload and adds srcset automatically, but themes often output the wrong sizes value, page builders add large background images, and the media library fills up with full-resolution camera photos. Image optimization plugins help, but it is still worth checking what visitors actually download.
Shopify and other ecommerce platforms usually serve images through a CDN with automatic resizing, so the common problems are elsewhere: product photos with missing or repeated alt text (often the product name on every gallery image), lazy-loaded hero images on collection pages, and very large source uploads. Product images also drive traffic from Google Images and Shopping, which makes image SEO more valuable for online stores than for most sites.
Next.js and other React sites often use an image component that handles formats and srcset, but the image that becomes LCP still needs priority / fetchpriority="high", and images added purely on the client after load can’t be seen by crawlers that don’t run JavaScript.
PageSpeed Insights and Lighthouse load one page in a real browser and measure what actually happened: the real LCP element, real layout shifts and real download timings. That makes them the best tool for confirming a performance problem on a single page. Their image advice is grouped into a few performance audits for that one URL.
This audit works differently. It reads the HTML of up to 50 pages, measures every image file, and checks performance, SEO, accessibility and errors together, listing each image once across the whole site. It does not run JavaScript or render the page, so layout-based checks (the likely LCP image, images below the fold) are clearly marked as heuristics. Use both: this audit to find every image problem across the site, and PageSpeed Insights to confirm the impact on your most important pages.
Start with critical and high issues: broken images, lazy-loaded LCP images, missing alt text and image links with no name. Then work through medium performance issues on your highest-traffic pages, where saved kilobytes matter most. Low issues (cache headers, file names, format suggestions) are worth fixing in bulk when you next update your images or your server configuration.
The “By page” view is useful for content editors, who usually fix one page at a time. The “By issue” view suits developers, because one template or server change often fixes the same issue on every page. Export the issues CSV to share the work, and re-scan afterwards to confirm the fixes.
Add an image section to a technical SEO audit: every missing alt, broken image and missing og:image across the site, exported as a CSV with the fix for each row.
Find heavy product photos that slow down category pages, and gallery images with missing or repeated alt text that miss out on Google Images traffic.
Check srcset/sizes, lazy loading, width/height and cache headers before a launch, and confirm that the hero image isn’t lazy-loaded.
See which uploads are still served at full camera resolution and whether your theme’s responsive images actually work.
Make sure every blog post has a social preview image and descriptive alt text before it is promoted.
Get a quick list of image-related WCAG problems (missing alt, unlabeled icon links and SVGs) to fix before a full manual review.
<img> and <picture> elements (including srcset), inline CSS background images, inline SVGs, og:image and twitter:image tags, favicons and images in JSON-LD structured data. Each image is downloaded from its server to measure its real size, format, dimensions, HTTP status and caching headers, and then checked for accessibility, performance, SEO and error issues.Fix broken images and missing alt text first, then the critical and high performance issues on your most visited pages. When you are ready to optimise files, the Bulk Image Converter turns JPEG and PNG into WebP or AVIF, and the Image Resizer cuts oversized photos down to the size they are displayed at.
Convert JPEG and PNG files flagged by the audit to WebP or AVIF in one go.
Shrink images that are larger than the space they are displayed in.
Bring heavy files under their size budget without visible quality loss.
Check and strip camera and GPS metadata before you publish photos.