WP Deferred JavaScripts vs AMP

Head-to-head on the signals that matter, from the public WordPress.org data.

Health F39

Health C57

Active-install trajectory

WP Deferred JavaScripts moved down one install band, 900+ to 800+; AMP moved down one install band, 400K+ to 300K+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	WP Deferred JavaScripts	AMP
Active installs Modeled from the public "N+" band and recent downloads.	800–900	300K–400K ✓
Install trend Change in active installs across the charted window.	-11% ✓	-25%
Overall health	F · 39	C · 57 ✓
Maintenance How recently the plugin was updated.	3/100	38/100 ✓
Rating quality Volume-adjusted review quality.	59/100	70/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	3.4★	3.8★ ✓
Reviews	35	367 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	42/100	78/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	High	Low ✓
Last updated	10.2y ago	1.6y ago ✓
Downloads · 30d	179	51K ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	0.5%	1.8% ✓
Category	Performance	Performance

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

WP Deferred JavaScriptsAMP

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.