Declare icons explicitly
A root favicon fallback is useful, but explicit icon declarations make browser behavior easier to review across page templates and deployments.
Favicon · app icon and source evidence
Check favicon and app icon setup
Inspect source-declared favicon links, the conventional /favicon.ico fallback, manifest declarations, icon target responses, content types, redirects, HTTPS state, cache policy, and cross-origin icon usage from bounded public evidence.
PAGE SOURCE2 MiBICON TARGETS20 MAXPIXELSNOT FETCHED
◆
Ready for a public HTML page.
No sample favicon result, browser-tab preview, app-install verdict, pixel-dimension claim, brand-trust score, ranking claim, or manufactured icon warning appears before a live bounded request.
Small asset, real trust signal
Make the site recognizable in browsers, bookmarks, tabs, and shared workspaces
Serve icons cleanly
Use HTTPS, stable content types, short redirects, and reasonable cache policy for icon files that rarely change.
Connect app context
A web app manifest can provide richer app names, theme colors, and icons when the site is intended to behave like an installable or saved app.