Images

The Images report groups crawled image sources and shows where each image is used. Use it to distinguish one broken asset from a template-wide implementation problem and to connect accessibility, delivery, and search findings to the pages visitors actually see.

Select the right image inventory

All Images contains every discovered source. All Issues combines missing alt text, missing dimensions, unsuccessful responses, and missing responsive source sets. A row can represent many uses, so the issue count is an investigation queue rather than a list of files to edit independently.

The table can include preview, source URL, page URL, alt text, dimensions, response status, response time, loading behavior, source type, and responsive signals. Use Source Pages to find the CMS field, component, stylesheet, or template that produced each use.

Analyze one image correctly

1. Open the image URL and confirm the response and content type.
2. Open representative source pages and determine the image's purpose.
3. Inspect rendered alt, width, height, src, srcset, sizes, and loading behavior.
4. Group findings by component, template, CDN path, and file type.
5. Compare repeated uses because one shared source can require different page-level text.
6. Prioritize by accessibility, visible breakage, traffic, layout impact, and affected-template size.

Choose an investigation path

Prioritize image work

Fix images that fail visibly or remove essential accessible meaning first. Then address shared components missing dimensions or responsive delivery, followed by format and source improvements supported by measured performance. A decorative image with alt="", an intentional SVG icon, or an image served from a reliable CDN can be correct.

Google recommends standard HTML image elements, crawlable sources, descriptive alt text, and responsive images with a fallback src. See Google Image SEO best practices.

Verify the result

Publish the component or content change, inspect representative pages at several viewport sizes, test image URLs, and run another crawl. Confirm both the asset and each relevant page use are correct. Use accessibility testing, PageSpeed Insights, Search Console, or browser network tools when they answer a question the crawl cannot.

A practical image audit workflow

Start with All Issues, then separate availability, accessibility, layout, and delivery concerns. A broken hero image is usually more urgent than a missing srcset on a small icon. An image used on hundreds of pages points to a template-level fix; a one-off editorial image can be handled on its source page.

Review each image at three levels:

1. File: response status, format, dimensions, and transfer behavior.
2. Markup: alt, width, height, srcset, and sizes.
3. Page context: purpose, placement, visibility, and contribution to the user's task.

The same file can be used correctly on one page and incorrectly on another. Source-page context is therefore essential.

How results should move after optimization

After repairing failed files, expect Broken, 4xx, or 5xx counts to fall and Success (2xx) to rise. Adding dimensions should reduce Missing Dimensions without changing the number of image files. Responsive markup may increase Has Srcset while total images stay stable.

A lower issue count is not enough on its own. Confirm that images still render, the selected resource is appropriate at common viewport sizes, and meaningful images retain useful alternative text. A large count change can also result from a redesigned template or reduced crawl scope.

Prioritization questions

• Is the image visible and important above the fold?
• Does it communicate information unavailable in nearby text?
• How many source pages use it?
• Is the defect caused by a shared component?
• Could the fix change layout, accessibility, or visual quality?

Google's image SEO best practices and the W3C alt decision tree are useful references alongside Screpy's crawl evidence.