Inspect HTTP Requests

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

1. ★★★★★ Farzad

   1.0y ago

   The plugin is so useful and i loved it. But there is some bugs and I think it’s okay for the first versions.#1: It shows no response for any request. all empty.#2: There is no “Clear log” button to empty log. I have to do it from DB.#3: Requests are not sortable by time or id, By default, They are sorted by Alphabets + Endpoint url. So i need a lot of scrolls to jump off 127.0.0.1 requests!Thank you very much! Hope my comment can help you for future updates.

   Read on wp.org ↗
2. ★★★★★ jubilo

   3.7y ago

   <p>The first version had bugs, but the developer fixed them and now it works excellent.<br />It is the most complete plugin to analyze outgoing traffic.</p> This topic was modified 3 years, 7 months ago by jubilo. This topic was modified 3 years, 6 months ago by jubilo.

   Read on wp.org ↗

Automated install-time checks, tested on PHP 8.1.12 · WP 6.8.1

Translated into 2 languages, 1 at 90% or more

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2024-03-14 90+ → 100+ up after 22 days in tier
2. 2024-02-21 80+ → 90+ up after 22 days in tier
3. 2024-01-30 70+ → 80+ up after 3 days in tier
4. 2024-01-27 80+ → 70+ down after 2 days in tier
5. 2024-01-25 70+ → 80+ up after 16 days in tier
6. 2024-01-09 80+ → 70+ down after 1 days in tier
7. 2024-01-08 60+ → 80+ up after 1 days in tier
8. 2024-01-07 70+ → 60+ down after 2 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• L Log HTTP Requests 2K+ installs · 4.5★ · 5 shared tags B
• HTTP Requests Manager 1K+ installs · 4.3★ · 2 shared tags A
• WP Consent API 200K+ installs · 4.1★ · 1 shared tag B
• Check & Log Email – Easy Email Testing & Mail logging 100K+ installs · 4.8★ · 1 shared tag A
• Disable REST API 80K+ installs · 4.6★ · 1 shared tag D
• Make Connector 80K+ installs · 3.1★ · 1 shared tag B

Embed this report card

Drop a live Pulse card for Inspect HTTP Requests into a readme, a review or a deck. It updates itself.

Inspect HTTP Requests: 100+ active installs, 5.0★ (2 reviews). Plugin Pulse (WP Mayor), as of 2026-08-31. https://plugins.wpmayor.com/plugin/inspect-http-requests