Force gzip vs WP HTTP Compression

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

Health D44

Health F38

Active-install trajectory

WP HTTP Compression moved down one install band, 500+ to 400+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	Force gzip	WP HTTP Compression
Active installs Modeled from the public "N+" band and recent downloads.	200–300	400–500 ✓
Install trend Change in active installs across the charted window.	0% ✓	-20%
Overall health	D · 44 ✓	F · 38
Maintenance How recently the plugin was updated.	3/100	3/100
Rating quality Volume-adjusted review quality.	72/100 ✓	56/100
Support Share of forum threads marked resolved.	70/100	70/100
Rating (adjusted)	3.91★ ✓	3.24★
Reviews	1	8 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	32/100	37/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	High	High
Last updated	16.3y ago	14.3y ago ✓
Downloads · 30d	94	133 ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	0.7% ✓	0.6%
Category	Uncategorized	Performance

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

Release activity

Force gzipWP HTTP Compression

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.