No favicon
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
No favicon file or link tag was found; the browser tab will show a generic icon.
Why it matters
Without a favicon, browser tabs, bookmarks, and history entries show a generic placeholder icon, which makes your app harder to spot among open tabs and reads as unfinished. Browsers also request /favicon.ico on their own, so its absence adds a recurring 404 to your logs. It is a small polish item that users notice more than developers expect.
How to fix it
Add an icon file and reference it from the <head>. The simplest modern approach is a single SVG: create icon.svg and add <link rel="icon" type="image/svg+xml" href="/icon.svg">, plus a fallback favicon.ico at the web root for older browsers. Next.js and similar frameworks pick up app/icon.svg or a favicon.ico in the public directory automatically. Generate a PNG/ICO set from your logo with a tool like RealFaviconGenerator if you need broad coverage.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo