Assets
Images and files the pages load.
A document asset is unusually large
Section titled “A document asset is unusually large”asset.document.heavy · Review signal (Needs review) · Severity: Medium
Why it matters. Large documents take longer to download and can consume substantial bandwidth, especially on mobile connections.
How to fix. Compress the document or move the large download behind a clear user action.
An asset has a generic file name
Section titled “An asset has a generic file name”asset.filename.generic · Review signal (Needs review) · Severity: Low
Why it matters. Generic names make assets harder to find, maintain and verify across pages and content collections.
How to fix. Rename the asset with a descriptive, stable name before client handoff.
An image could use a modern format
Section titled “An image could use a modern format”asset.image.avif_candidate · Review signal (Needs review) · Severity: Low
Why it matters. A lighter image can reduce transfer time and improve loading performance, but conversion must preserve visual quality and transparency.
How to fix. Review whether the image can use a modern format without unacceptable quality loss.
An image asset is large
Section titled “An image asset is large”asset.image.large · Review signal (Needs review) · Severity: Medium
Why it matters. Large images increase transfer and decode work and can delay the point at which visitors see useful content.
How to fix. Compress the image, use WebP/AVIF where appropriate and match delivered dimensions to its display size.
An image uses a legacy format
Section titled “An image uses a legacy format”asset.image.legacy_format · Review signal (Needs review) · Severity: Low
Why it matters. Legacy image formats can transfer more bytes than necessary and slow visual loading.
How to fix. Convert suitable images to WebP or AVIF, keep an appropriate fallback, and verify quality and loading behavior.
An image element is missing its source
Section titled “An image element is missing its source”asset.image.source_missing · Issue · Severity: High
Why it matters. An image without a source cannot render its intended content and can leave a visible gap or broken control in the page layout.
How to fix. Set a valid image source or remove the empty image element, then verify the rendered page at every affected URL.
An asset may be unused
Section titled “An asset may be unused”asset.unused.conservative · Review signal (Needs review) · Severity: Set per finding
Why it matters. Apparently unused assets increase project clutter and storage, but sampled evidence cannot prove they are safe to remove without review.
How to fix. Treat the asset as a cleanup candidate only after manually confirming that it is safe to remove.
An asset URL is unreachable
Section titled “An asset URL is unreachable”asset.url.unreachable · Issue · Severity: Medium
Why it matters. A broken image, font or downloadable asset can leave pages incomplete and degrade trust or task completion.
How to fix. Replace or republish the asset, then verify every page and CMS item that references it.