The Broken images signal shows image assets from this scan that failed or returned an invalid response.
This is a scan-level signal. It answers: “Did this snapshot find image assets anywhere in the scanned site that need attention?”
What this signal means
A broken image is an image reference that Siteimp could not load as a valid image asset.
This can happen when:
- the image URL returns an HTTP error
- the image request fails
- the server returns the wrong content type
- the image is present in markup or CSS but the asset is missing
- the image redirects to something unexpected
Signal vs issue
This page is the signal view. It summarizes broken image findings across the scan.
A page issue is the same kind of finding, but scoped to one page. For example, if the scan finds broken images across several pages, that appears as a signal. If a specific page uses broken images, that page can show a Broken images issue.
Why it matters
Broken images can make a page look unfinished, confuse readers, and weaken calls to action. They can also point to deeper problems such as moved assets, bad build output, CDN trouble, or incorrect image paths.
What to check next
Open the asset URL directly.
Check whether the image exists at that location.
Check the page template, markdown, CMS entry, or CSS rule that references the image.
If the content type is wrong, check the server or CDN configuration.
If the image loads in your browser but failed in Siteimp, rerun the scan to rule out a temporary network or server issue.
Why this signal may be empty
If the page says no broken images were found, Siteimp did not find failing image assets in this scan.
That does not mean the site has no images. It means the image assets Siteimp checked did not produce broken image findings for this snapshot.