Which of your site icons actually exist?
Paste a URL. Favitest reads every icon declaration in the page’s HTML, fetches each file and the two implicit fallbacks, then reports which are present, which are missing, and which are served in the wrong format.
How it works
- Paste any public URL into the checker.
- Favitest fetches the page and reads every icon declaration:
<link rel="icon">,apple-touch-icon,msapplication-TileImage, and more. - It fetches each icon file plus the two implicit fallbacks (
/favicon.icoand/apple-touch-icon.png) and parses their binary headers. - You see a table of every icon, its pixel dimensions, format, HTTP status, and a verdict per context — browser tab, search result, iOS homescreen.
Three contexts, one table
An icon that works in your browser tab may be invisible to an iOS homescreen bookmark or missing from a Google search result. Favitest reports what each context would actually receive.
Browser tab
The icon users see in their tab, bookmarks, and history. Usually
<link rel="icon"> or the root /favicon.ico fallback.iOS homescreen
The icon shown when someone saves your site to their home screen. Requires
<link rel="apple-touch-icon"> at 180×180 or the implicit /apple-touch-icon.png.Search result
Google and other search engines use icon declarations from the page HTML. A missing or misconfigured icon means your site appears without a brand mark in search results.
Why not just clear the cache?
Because a missing file is not a caching problem. If /apple-touch-icon.png returns 404 and you never declared one, clearing the cache changes nothing. Favitest tells you which file is absent, so you know what to fix rather than guessing what to clear.