Enter a site address to review its favicon: declared files, sizes, web manifest, with real previews and the fixes to apply.
The tool fetches the home page HTML, reads every icon tag it declares, then requests each declared file to confirm it really exists and has the right dimensions. It also tests for a favicon.ico at the root, validates its multi-size header, and downloads the web manifest to check its name, its colors and its icons.
A favicon works on launch day and then disappears months later, usually without anyone noticing. The causes are always the same: a path change after a redesign, a file left out of the build output, an overly aggressive cache rule, or a web manifest pointing at icons that were deleted. None of it triggers a visible error on the site.
Google shows the favicon next to the title in mobile results. To be picked up, the icon must be crawlable, served with a correct MIME type, square, and declared on the domain's home page. A file blocked by robots.txt or returning an error leaves a generic globe instead, which costs you clicks.
Each warning names the file involved and the expected fix. When several pieces are missing, the fastest route is to regenerate the whole package from your current logo: you get a consistent set with the right sizes and the code to paste. The checker can then be run again to confirm everything is in place.
The other LFFavicon tools, and the guides that answer the questions people ask most.