Head.WP vs Async JS and CSS

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

Health D41

Health D46

Active-install trajectory

Async JS and CSS moved down one install band, 800+ to 700+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	Head.WP	Async JS and CSS
Active installs Modeled from the public "N+" band and recent downloads.	10–20	700–800 ✓
Install trend Change in active installs across the charted window.	0% ✓	-13%
Overall health	—	D · 46 ✓
Maintenance How recently the plugin was updated.	3/100	3/100
Rating quality Volume-adjusted review quality.	—	78/100 ✓
Support Share of forum threads marked resolved.	—	70/100 ✓
Rating (weighted for review count)	—	4.1★ ✓
Reviews	0	51 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	35/100	43/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	High	High
Last updated	12.7y ago	8.9y ago ✓
Downloads · 30d	32	182 ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	0.3%	0.6% ✓
Category	Uncategorized	Uncategorized

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

Release activity

Head.WPAsync JS and CSS

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.