WP Asset Radar attributes every CSS and JS file to the plugin or theme that loaded it, weighs them page by page, and flags the files loaded where they're likely unused — with the reason for each flag. Then, on Pro, dequeues them with one-click undo.
FROM $49/YEAR · LIFETIME OPTION · 14-DAY GUARANTEE
“The client's forwarded a PageSpeed screenshot with one line: why is our site so slow? The homepage weighs 4 MB — and nobody in the room can say which plugin the weight came from.”— Monday morning, in every agency inbox
The waterfall tools show the requests. WP Asset Radar names the owners — which plugin loaded which file, on which page, and what each one weighs.
One scan walks the site page by page, captures every enqueued CSS and JS file, and hands each one back to the plugin or theme that loaded it. The 4 MB question gets an itemised answer in minutes.
Each CSS and JS file is traced back to the plugin or theme that enqueued it — from the directory it actually lives in, not guessed from the URL. The result is an owner league table per page and for the site: which plugins earn their weight, and which one is quietly shipping a megabyte to every visitor.
Real file sizes, per page — homepage, shop, contact, all of them — rolled into a weight scorecard and a trend across scans, so last month's 2.9 MB homepage reading sits next to this month's 3.9 MB one. Honest scope: totals cover the files WordPress enqueues; assets loaded from external CDNs are listed with their owner but not weighed.
Assets loaded where they probably do nothing get flagged, and every flag says why: form-plugin CSS on a page with no form, gallery JS where there's no gallery markup, a file loaded on all 24 pages and used on one. Each flag now explains what its assets are and shows what depends on them, so you judge before you act — with an extra caution on page-builder owners like Elementor whose usage isn't visible in the page content. Flags are heuristics to verify, not certainties — which is exactly why the rules preview exists.
Turn a flag into a rule in one click — correctly scoped, ready to preview. Every rule previews in your admin session first, a dependency guard blocks anything another asset relies on, and one-click undo waits behind every rule. A dated change log records every rule you add, disable or undo, so you can always see — and reverse — exactly what changed. Front-end only, fully reversible — control without the white-knuckle moment.
Measure the win, don't estimate it. One click loads the page twice — stock, then with your rules applied — and reports the exact CSS/JS requests and kilobytes removed. It runs on your server, never touches visitors, and the measured figure carries straight into the branded report and PDF.
Print-ready HTML and a real downloadable PDF in your agency's logo, name and colours: the per-page weight table, the owner league table, the flagged assets with reasons, the savings estimate and the before/after trend. This is the retainer pitch, on paper — here's the weight, here's who packed it, here's what we'd recover.
The client wants to know why the homepage is heavy. One scan later you have the itemised answer — every file, every owner, every kilobyte — instead of a shrug and a caching plugin.
The Pro report is a performance retainer pitch the client can hold: the weight, the league table of who packed it, the flagged waste and the savings estimate — your logo on top.
Weigh the site before pricing the work. The league table shows which plugins earn their weight and which should go — evidence for the scope conversation, not instinct.
Plugins gain weight quietly, update by update. The trend across scans catches the release that added 600 KB while it's still news, not archaeology.
The same scan on every client site, one licence across the fleet. The heaviest sites surface first, and every site gets the same evidence-first answer to the weight question.
Apply the rules and run the before/after speed test — it loads the page stock vs optimised and shows the exact requests and kilobytes removed, while the trend across scans tracks the drop over time. The difference between claiming the work happened and showing it.
The page total, before and after the rules — 3.9 MB down to 1.1 MB on this homepage. One line the client understands without a glossary, backed by the itemised table behind it.
Every plugin and the theme, ranked by the weight they load, with the bars doing the talking. This is the answer to “which plugin did it?” — and usually the start of the “do we still need it?” conversation.
Each likely-unused file with its weight and the reason it was flagged, in plain English. Heuristics, verified in preview — the report shows the evidence, not just the accusation.
What the rules would recover, plus what was weighed and when. Print-ready HTML and a real PDF in your agency's branding — attach it to the retainer proposal.
The usual options: a waterfall tool (browser devtools or a speed-test site), a generic optimizer plugin, or a manual code audit. Here's what changes against the tool most people reach for first.
| WP Asset Radar (us) | Waterfall tools | |
|---|---|---|
| Names the plugin behind each file | ✓ Attribution built in | ✗ URLs, not owners |
| Covers the whole site | ✓ Page-by-page scan | ✗ One URL per run |
| Flags likely-unused assets | ✓ With the reason for each | ◐ Coverage data, unattributed |
| Trend across scans | ✓ Built in | ✗ One-off snapshots |
| A fix path | ✓ Dequeue rules + undo (Pro) | ✗ Diagnosis only |
| Client-ready evidence | ✓ Branded report + PDF (Pro) | ✗ Screenshots |
| Measures network transfer | ◐ Enqueued files; CDN listed unweighed | ✓ Everything over the wire |
| Free to run | ✗ From $49/yr | ✓ Free |
Waterfall tools are good at what they measure — bytes over the wire. They just stop at the request list; the attribution and the fix are still your evening. Full comparison →
Every plan includes every Pro feature — the per-page dequeue rules with preview and undo, and the branded page-weight report with the PDF. You're only choosing how many sites.
Up to 10 sites
25 sites · for agencies
Up to 100 sites
Up to 100 sites, forever
Prices in USD. Licence keys are domain-based — no accounts, no phoning home. VAT invoices available.
Plugins and themes hand their CSS and JS to WordPress through the enqueue system, and every registered asset carries a source path. The scanner captures the full asset list for each page as WordPress assembles it, traces each file back to the plugin or theme directory it came from, and records the owner next to the file and its weight. No guessing from URLs — the attribution comes from where the file actually lives.
The CSS and JS files WordPress enqueues on each page, at their real file sizes, page by page. Assets a plugin loads from an external CDN are listed with their owner so nothing is hidden, but they aren't weighed — we won't invent a number for a file that isn't on your server. The totals are the weight your WordPress install is responsible for, which is the part you can act on.
It's a heuristic, and the report says so. Each flag carries its reason in plain English: a form plugin's stylesheet on a page with no form, a gallery plugin's lightbox script on a page with no gallery markup, an asset loaded on all 24 pages but plausibly used on one. Flags are leads to verify, not certainties — the Pro rules preview shows you the exact page without the flagged file before anything changes for visitors.
The rules are built so you find out before visitors could. Every rule previews in your admin session first — you see the page without the asset while the public site is untouched. A dependency guard blocks removing any file that another enqueued asset declares a dependency on. Rules apply to the front end only, never the admin, and every rule has a one-click undo. Fully reversible, by design.
No. Asset capture runs only on signed scan requests you trigger from the admin — visitors never start a scan, and no scanning code runs on normal page loads. The plugin adds nothing to the front end of the site except, on Pro, the dequeue rules you've chosen — which remove weight rather than add it.
No, and that's deliberate. Optimizer plugins shrink and merge the files but load them all anyway; Asset Radar tells you which files shouldn't be loading at all, and on Pro stops them per page. The two approaches stack — run Asset Radar alongside your caching or optimizer plugin and let each do its own job. This is evidence and control, not a magic speed-up button.
Turn any flag into a rule in one click, preview it in your admin session, pass the dependency guard, then apply it to the front end with one-click undo and a dated change log of every change. A before/after speed test loads the page stock vs optimised and measures the exact requests and kilobytes removed. And the branded page-weight report: print-ready HTML and a real downloadable PDF in your agency's logo and colours, with the per-page weight table, the owner league table, the flagged assets with reasons, the savings estimate and the before/after numbers. The free edition keeps the full scan, attribution, weights, flags, scorecard and trend.
Yes, per site. Scans, attribution, flags, rules and reports are all scoped to the individual site, because two sites in a network rarely load the same asset mix. Network-activate the plugin if you like; each site still gets weighed and ruled on its own.
Order through the form and your licence key and invoice arrive by email, usually within the hour. Keys are long codes starting VPC1. — paste the whole thing into the licence textarea rather than typing it. Domain-based, no account, no phoning home, no lock-in.
14-day money-back guarantee, no questions. Email us and we refund you.
Order below and your licence key and invoice arrive by email — usually within the hour. Run the first scan the same afternoon, and the next “why is it slow?” email gets an itemised reply with names in it.
14-DAY MONEY-BACK GUARANTEE · SUPPORT BY ACTUAL HUMANS