How to use it
- 1
Paste a public HTML page URL.
- 2
WebDiag discovers stylesheet links and inline style blocks, then fetches a bounded CSS sample.
- 3
Review duplicate links, @import chains, decoded bytes, MIME, compression, and failed stylesheets.
What the tool can do
- Same-host/cross-host inventory and media/alternate/disabled signals.
- Counts inline bytes, sampled decoded bytes, @import, and @font-face.
- Checks response status, text/css MIME, Content-Encoding, Cache-Control, and redirects.
Common use cases
- Find duplicate stylesheet requests and MIME errors.
- Check for @import discovery chains.
- Review the bounded decoded CSS surface after a release.
How it works inside
Every CSS URL is revalidated by the public-target policy and bounded decoded-body limit.
The sampled size is not a browser transfer waterfall or an unused-CSS measurement.
Questions and answers
Does the tool identify render-blocking CSS?
It shows default-media candidates and loading attributes but does not claim runtime blocking without a browser trace.
Why is @import treated as a review signal?
It can create an additional discovery chain. The actual impact depends on order, cache, and browser runtime.
