No supported homepage icon declaration or conventional favicon was found
The homepage did not declare a supported icon link, and ShipReady's conditional request to /favicon.ico did not return HTTP 200.
Why it matters
A browser-tab icon helps users recognise a site in tabs, bookmarks, and shortcuts. Its absence is a presentation issue worth resolving before launch.
How ShipReady detects it
What it inspects
ShipReady inspects the fetched homepage markup for a link relation containing icon, apple-touch-icon, or mask-icon.
Only when no supported icon declaration appears, ShipReady requests the conventional same-origin /favicon.ico path and follows redirects.
What triggers a finding
The rule triggers when no supported homepage icon declaration is found and the /favicon.ico response is not HTTP 200.
What the evidence shows
The inspected homepage lacked ShipReady's supported icon-link signal, and the conventional favicon path did not return HTTP 200 during this probe.
Limits of this check
ShipReady does not validate every icon format, image dimensions, manifest entry, browser cache, or every route. It does not make the favicon request when a supported homepage declaration is present. Failed, rate-limited, or unavailable origin probes produce no finding.
How to fix it
Publish and declare the intended site icon
Use your framework's icon convention or publish a supported icon declaration. If relying on the conventional fallback, make sure /favicon.ico is served successfully.
How to verify the change
Verify the deployed icon path or declaration
Inspect the deployed homepage markup and request the declared icon or /favicon.ico directly. Use a fresh browser context when checking visual updates because icons can be cached.
Expected: The deployed homepage declares the intended icon or the conventional favicon path returns HTTP 200.