WordPress plugin comparison
Force non-SSL vs HTTPS for WordPress
At a glance
- HTTPS for WordPress has more active installs: 30+, against 20+ for Force non-SSL.
- On a typical day, HTTPS for WordPress is downloaded about 6 times, Force non-SSL about 2.
- HTTPS for WordPress has no reviews yet.
- Force non-SSL was updated more recently: Dec 5, 2013, against Jun 3, 2008 for HTTPS for WordPress.
- Force non-SSL is tested with a newer WordPress: 3.7.41, against 2.5 for HTTPS for WordPress.
- HTTPS for WordPress has been around longer: since 2008, against 2010 for Force non-SSL.
Line by line
HTTPS for WordPress leads on 3 of 5 comparable lines.
| Metric | ||
|---|---|---|
| Popular rank | #25,466 | #23,713 |
| Active installs | 20+ | 30+ |
| Downloads, last 30 days | 54 | 129 |
| Rating | 5.0(1) | No ratings |
| Support threads resolved | – | – |
| Tested up to | 3.7.41 | 2.5 |
| Search multiplier | ×0.00 | ×0.00 |
| Last release | 13 years ago | 18 years ago |
| Requires PHP | – | – |
From WordPress.org's public data, refreshed every night. Downloads are WordPress.org's official daily figures for the last 30 days.
Tags they share
More comparisons
- Force non-SSL vs Easy HTTPS Redirection (SSL)
- Force non-SSL vs SSL Insecure Content Fixer
- Force non-SSL vs WP Force SSL & HTTPS SSL Redirect
- Force non-SSL vs WP Encryption
- HTTPS for WordPress vs Easy HTTPS Redirection (SSL)
- HTTPS for WordPress vs SSL Insecure Content Fixer
- HTTPS for WordPress vs WP Force SSL & HTTPS SSL Redirect
- HTTPS for WordPress vs WP Encryption
Is one of these yours?
Track your plugin against its rivals every day: rank, installs, downloads, ratings and their releases, with alerts when anything moves.
Start free