Performance & Tech tool

Favicon & PWA Checker

Verify favicon setup across required sizes, check for a web app manifest, inspect PWA icons (192px, 512px), theme-color, maskable icons, and service worker signals.

Typical check: 3sNo paid API requiredCore Web Vitals contextEdge and protocol signalsPayload-level clues

Test performance Browse Performance & Tech

Typical time

Access

Open

Processing

Live

Intent

Performance & Tech

What it checks

Favicon & PWA Checker coverage

Favicon & PWA Checker

Check favicons, web app manifest, and PWA readiness.

Delivery layer

Inspect protocol, CDN, compression, and response signals where available.

Resource footprint

Surface page weight, resource count, app shell clues, or installability signals.

Optimization next steps

Prioritize fixes that reduce latency, transfer size, or rendering friction.

Methodology

How the result is produced

1Finds favicon, apple-touch-icon, manifest, theme-color, and service worker signals in the live HTML.
2Checks whether required icon sizes are present for browser tabs, mobile shortcuts, and install prompts.
3Highlights missing manifest fields that reduce PWA quality and brand consistency in search surfaces.

Next steps

How to act on the result

Add a root favicon plus 180px, 192px, and 512px icons for broad browser and device support.
Publish a valid web app manifest with name, short_name, icons, start_url, display, and theme_color.
Use maskable icons when you want polished Android install surfaces.

Interpretation

Read the result without guessing

What the result means

Performance findings are strongest when checked on representative page types, not only the homepage.
Separate server response, transfer size, resource count, compression, and frontend rendering clues.
A stack clue is useful only when it points to a practical optimization path.

Evidence to keep

URL, response time, protocol, compression, page weight, and major resource groups.
The page type tested and whether it is cached, logged-out, or region-specific.
Any recent release, plugin, app, CDN, or theme change that may explain a regression.

Best next fix

Reduce server and CDN latency before chasing small frontend details.
Cut heavy scripts, oversized images, and uncompressed assets.
Retest the same page type after deployment and compare the exact metrics.

Use cases

When to use the Favicon & PWA Checker

Core Web Vitals triage

Find infrastructure or payload issues that can affect LCP, CLS, and INP.

Stack research

Understand how a site is built, delivered, and optimized at the edge.

Performance regression checks

Retest after releases to catch heavier pages, slower responses, or missing compression.

Popular checks

Try PWA on common domains

PWA for vercel.com PWA for cloudflare.com PWA for shopify.com PWA for github.com PWA for stripe.com PWA for openai.com

Next paths

Continue with the right follow-up

Use these pages when the result points to a broader check, a fix workflow, or a related technical question.

Meta Tags Checker Open Graph Preview Page Weight Analyzer

Frequently asked questions

Favicon & PWA Checker common questions

Do I need an account to use the Favicon & PWA Checker?+

No. Enter a URL or domain and run the check in your browser. Some results can be partial if the target site blocks requests or hides the data being checked.

How accurate is the Favicon & PWA Checker?+

The Favicon & PWA Checker runs live checks against the target website. Results reflect what was reachable at the time of the test, so retest after changing DNS, redirects, headers, or page content.

What favicon sizes are required?+

At minimum: 16x16 and 32x32 for browsers, 180x180 for Apple Touch Icon, 192x192 and 512x512 for Android/PWA. A /favicon.ico fallback is also recommended.

What makes a site PWA-ready?+

A Progressive Web App needs: a web app manifest (manifest.json), a service worker, HTTPS, icons in 192px and 512px sizes, and a theme-color meta tag.

Loading CheckWebs…

Performance & Tech tool

Favicon & PWA Checker

Verify favicon setup across required sizes, check for a web app manifest, inspect PWA icons (192px, 512px), theme-color, maskable icons, and service worker signals.

Typical check: 3sNo paid API requiredCore Web Vitals contextEdge and protocol signalsPayload-level clues

Test performance Browse Performance & Tech

Typical time

Access

Open

Processing

Live

Intent

Performance & Tech

What it checks

Favicon & PWA Checker coverage

Favicon & PWA Checker

Check favicons, web app manifest, and PWA readiness.

Delivery layer

Inspect protocol, CDN, compression, and response signals where available.

Resource footprint

Surface page weight, resource count, app shell clues, or installability signals.

Optimization next steps

Prioritize fixes that reduce latency, transfer size, or rendering friction.

Methodology

How the result is produced

1Finds favicon, apple-touch-icon, manifest, theme-color, and service worker signals in the live HTML.
2Checks whether required icon sizes are present for browser tabs, mobile shortcuts, and install prompts.
3Highlights missing manifest fields that reduce PWA quality and brand consistency in search surfaces.

Next steps

How to act on the result

Add a root favicon plus 180px, 192px, and 512px icons for broad browser and device support.
Publish a valid web app manifest with name, short_name, icons, start_url, display, and theme_color.
Use maskable icons when you want polished Android install surfaces.

Interpretation

Read the result without guessing

What the result means

Performance findings are strongest when checked on representative page types, not only the homepage.
Separate server response, transfer size, resource count, compression, and frontend rendering clues.
A stack clue is useful only when it points to a practical optimization path.

Evidence to keep

URL, response time, protocol, compression, page weight, and major resource groups.
The page type tested and whether it is cached, logged-out, or region-specific.
Any recent release, plugin, app, CDN, or theme change that may explain a regression.

Best next fix

Reduce server and CDN latency before chasing small frontend details.
Cut heavy scripts, oversized images, and uncompressed assets.
Retest the same page type after deployment and compare the exact metrics.

Use cases

When to use the Favicon & PWA Checker

Core Web Vitals triage

Find infrastructure or payload issues that can affect LCP, CLS, and INP.

Stack research

Understand how a site is built, delivered, and optimized at the edge.

Performance regression checks

Retest after releases to catch heavier pages, slower responses, or missing compression.

Popular checks

Try PWA on common domains

PWA for vercel.com PWA for cloudflare.com PWA for shopify.com PWA for github.com PWA for stripe.com PWA for openai.com

Next paths

Continue with the right follow-up

Use these pages when the result points to a broader check, a fix workflow, or a related technical question.

Meta Tags Checker Open Graph Preview Page Weight Analyzer

Frequently asked questions

Favicon & PWA Checker common questions

Do I need an account to use the Favicon & PWA Checker?+

No. Enter a URL or domain and run the check in your browser. Some results can be partial if the target site blocks requests or hides the data being checked.

How accurate is the Favicon & PWA Checker?+

The Favicon & PWA Checker runs live checks against the target website. Results reflect what was reachable at the time of the test, so retest after changing DNS, redirects, headers, or page content.

What favicon sizes are required?+

At minimum: 16x16 and 32x32 for browsers, 180x180 for Apple Touch Icon, 192x192 and 512x512 for Android/PWA. A /favicon.ico fallback is also recommended.

What makes a site PWA-ready?+

A Progressive Web App needs: a web app manifest (manifest.json), a service worker, HTTPS, icons in 192px and 512px sizes, and a theme-color meta tag.