When a page is heavy and a plugin is suspected, the usual responses are: a waterfall tool, a generic optimizer plugin, or a manual code audit. Here's the honest breakdown against all three.
Waterfall tools — browser devtools, GTmetrix-style speed testers — measure everything that travels over the wire, beautifully, for one URL at a time. They show you the requests; they can't tell you which plugin owns each file, and they end at diagnosis. Generic optimizer plugins minify, combine and defer — useful, but they load everything anyway; 40 unused kilobytes minified into 28 unused kilobytes is still waste on every visit. Manual code audits answer everything, at consultancy prices, and are out of date by the third plugin update. WP Asset Radar (this site) does the one thing none of them do: it attributes every CSS and JS file to the plugin or theme that loaded it, page by page, flags the files that are likely unused with the reason for each flag, and — on Pro — turns the flags into per-page dequeue rules with a preview, a dependency guard and one-click undo, plus a branded report with the savings on paper.
| Feature | WP Asset Radar | Waterfall tools | Optimizer plugins | Manual code audit |
|---|---|---|---|---|
| Names the plugin behind each file | ✓ Attribution built in | ✗ URLs, not owners | ✗ Not its question | ✓ Eventually, by hand |
| Covers the whole site | ✓ Page-by-page scan | ✗ One URL per run | ◐ Applies everywhere, measures nothing | ◐ Whatever the budget covers |
| Flags likely-unused assets, with the reason | ✓ Per page, reason attached | ◐ Coverage data, unattributed | ✗ Loads everything anyway | ✓ That's the job |
| Stops unused files loading | ✓ Per-page rules (Pro) | ✗ Diagnosis only | ✗ Shrinks them, still loads them | ◐ If you implement the findings |
| Safe to try, easy to undo | ✓ Preview + guard + one-click undo | ✓ Changes nothing | ◐ Site-wide toggles, famous for breakage | ✗ Code changes to revert |
| Trend across scans | ✓ Built in | ✗ One-off snapshots | ✗ None | ✗ Point in time |
| Client-ready evidence | ✓ Branded report + PDF (Pro) | ✗ Screenshots | ✗ Nothing on paper | ✓ A (very expensive) document |
| Time to the answer | ✓ Minutes — one scan | ◐ Fast, wrong question | ✗ Never answers it | ✗ Days to weeks |
| Measures network transfer | ◐ Enqueued files; CDN listed unweighed | ✓ Everything over the wire | ✗ Doesn't measure | ◐ If asked |
| Cost | From $49/yr · $599 lifetime | Free | Free to ~$60/yr | Hundreds to thousands |
Your problem is images, fonts or a slow server — that's waterfall-tool territory, and Asset Radar won't pretend otherwise. Keep your optimizer plugin too: minifying and deferring what does belong on the page is real work, and the two stack. And if a client needs a full architectural review before a replatform, that's a human audit — bring the Asset Radar scan along as its first exhibit.
You look after WordPress sites where “why is it slow?” keeps arriving by email, and you want every CSS and JS file attributed to the plugin that loaded it, weighed page by page, with the likely-unused files flagged, dequeued and undone in one click — and, on Pro, a branded report that turns the answer into a performance retainer. That's us.
One honest line: the weights are the files WordPress enqueues — assets a plugin pulls from an external CDN are listed with their owner but not weighed — and “likely unused” flags are heuristics to verify in the preview, not certainties. Evidence and control, not a magic speed-up button.