Skip to content
install

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

diagnostic · one of 29free, no counter

Unused

What did this page download and never use?

Dead weight comes in kinds that are not equally safe to remove, and a single "unused" list flattens that distinction into something nobody dares act on. Each row here carries how confidently it can go: a downloaded font nothing uses, a custom property nothing reads, a class that appears in no markup - three different levels of certainty, marked as such.

Reach itPress +K on any tab and type unused.Ctrl+Kon Windows and Linux

What the page downloaded and never used
readsstylesheets, markup and loaded resources
writesnothing
sendsnothing
kindsa table - each row says how safely it can go
switchesapplied before the counts, never after
savingestimated, and it says estimated
planfree
Add LoupeKit- opens the list of browsers it can be installed in

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

in the panel · free, no counter

section#about

What this actually is

Before a cleanup, and during one as the check that the cleanup worked. The two narrowing switches are applied before the counts, so an eleven-row report says eleven.

section#asked

Asked about this diagnostic

Is it safe to delete everything it lists?

No, and the marks say so. A downloaded font nothing uses is safe; a class that appears in no markup may be applied by a script on another route. The tone on each row is how confidently it can go.

Why does the count change when I flip a switch?

Because the switches narrow the *reading*, not the view - they are applied first, so the strip, the chips and the saving all describe the same set. A switch that only filtered the list would leave a summary disagreeing with what is under it.

Does it find unused JavaScript?

It reports what the browser can tell it about resources that were loaded and never executed. Function-level dead code is a build-tool question rather than a page-reading one.

Why is the saving an estimate?

Because removing a rule changes what compresses against what. The figure is the transfer size of what was fetched, which is an upper bound rather than a promise.

Add LoupeKit- opens the list of browsers it can be installed in

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

63 of these · no host permissions · three free audits