Scorecard
WordPress Plugin Bloat Scorecard
Score the six places plugin-heavy WordPress sites usually slow down: plugin count, frontend requests, JS/CSS weight, database overhead, page-builder usage, and Core Web Vitals risk.
Six-factor scoring matrix
| Factor | 0 points | 1 point | 2 points |
|---|---|---|---|
| Plugin count | 0 to 10 active plugins, all tied to visible business requirements. | 11 to 20 active plugins, with a few legacy or convenience plugins. | More than 20 active plugins, or plugins nobody can explain. |
| Frontend requests | Fewer than 35 JS/CSS/font requests on a representative landing page. | 35 to 60 frontend requests after caching and CDN setup. | More than 60 frontend requests, or plugin assets loading on pages that do not use them. |
| JS/CSS weight | Under 300KB transferred JS/CSS on mobile for the tested template. | 300KB to 750KB transferred JS/CSS, with some render-blocking files. | More than 750KB JS/CSS, heavy unused CSS, or main-thread blocking from plugin scripts. |
| Database overhead | Under 50 database queries and stable TTFB on logged-out page loads. | 50 to 100 queries, slow admin screens, or inconsistent cache misses. | More than 100 queries, slow uncached TTFB, or plugins writing bloated options/postmeta. |
| Page-builder usage | No page builder on priority templates, or only static block-editor content. | Page builder used on secondary pages but not main conversion pages. | Elementor, Divi, WPBakery, or similar builder controls key landing pages. |
| Core Web Vitals risk | Mobile LCP, INP, and CLS pass in field data or reliable RUM. | One CWV metric needs improvement, or only lab data exists. | LCP, INP, or CLS fails on priority pages after basic optimization. |
Score interpretation
0 to 3 points
Cleanup path
Remove unused plugins, clean duplicate tags, optimize images, check caching coverage, and rerun the speed test.
4 to 7 points
Audit path
Measure plugin PHP cost, frontend assets, DOM size, Core Web Vitals, and Search Console impact before buying more optimization work.
8 to 12 points
Rebuild threshold
Do not jump straight to a rebuild, but treat repeated plugin cleanup as suspect until URL, redirect, canonical, and tracking risk are mapped.
Measurement workflow
Turn the score into evidence
The score is a triage layer. The real decision comes from before/after measurements on the same template.
- 1Run the WordPress Speed Test on the priority URL.
- 2Open Chrome DevTools Network and count JS, CSS, font, and third-party requests.
- 3Use Query Monitor on the same template to record query count, PHP time, scripts, and styles.
- 4Run document.querySelectorAll('*').length in DevTools to check DOM size.
- 5Score each row 0, 1, or 2, then write down the three highest-cost factors.
- 6Retest after removing obvious offenders so the score becomes a before/after artifact.
Use the score with the speed test
The plugin score explains the internal drag. The speed test checks the public mobile result. If both are bad, the audit maps the fix order before anyone prices a rebuild.