Benchmarks
Plugin footprint 48% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼2.35ms] Passed 4 tests
An overview of server-side resources used by Inspect HTTP Requests
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.58 ▲0.12 | 39.12 ▼0.11 |
Dashboard /wp-admin | 3.42 ▲0.12 | 44.40 ▼4.12 |
Posts /wp-admin/edit.php | 3.54 ▲0.18 | 48.77 ▼4.13 |
Add New Post /wp-admin/post-new.php | 6.02 ▲0.13 | 94.49 ▼1.03 |
Media Library /wp-admin/upload.php | 3.35 ▲0.11 | 37.42 ▲1.40 |
Inspect HTTP Request /wp-admin/tools.php?page=inspect-http-requests | 3.32 | 33.08 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 26 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_ets_wp_outbound_http_requests |
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Inspect HTTP Requests
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,811 ▲76 | 13.35 ▼0.85 | 1.78 ▲0.06 | 51.02 ▲9.80 |
Dashboard /wp-admin | 2,217 ▲29 | 5.85 ▲0.99 | 106.85 ▲4.58 | 45.06 ▼2.41 |
Posts /wp-admin/edit.php | 2,100 ▲11 | 2.04 ▲0.03 | 38.80 ▼4.10 | 34.47 ▼3.89 |
Add New Post /wp-admin/post-new.php | 1,524 ▼9 | 22.94 ▼0.55 | 644.52 ▼37.27 | 48.44 ▼5.14 |
Media Library /wp-admin/upload.php | 1,402 ▲14 | 4.20 ▼0.02 | 96.25 ▼4.36 | 43.35 ▼4.52 |
Inspect HTTP Request /wp-admin/tools.php?page=inspect-http-requests | 905 | 2.08 | 28.15 | 34.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- Uninstall procedure validation failed for this plugin
- > Notice in wp-content/plugins/inspect-http-requests/uninstall.php+13
Undefined index: plugin
- The uninstall procedure failed, leaving 1 table in the database
- wp_ets_wp_outbound_http_requests
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/inspect-http-requests/public/partials/inspect-http-requests-public-display.php
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/inspect-http-requests/admin/partials/inspect-http-requests-admin-display.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== inspect-http-requests ===
)
inspect-http-requests/inspect-http-requests.php Passed 13 tests
"Inspect HTTP Requests" version 1.0.5's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
139 characters long description:
Monitor all the HTTP Request being made via WP HTTP Methods i.e. wp_remote_get, wp_remote_post Block any request by just a click of button.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected800 lines of code in 19 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 15 | 171 | 524 | 563 |
JavaScript | 2 | 14 | 55 | 125 |
CSS | 2 | 12 | 9 | 112 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 4.75 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 25.00 |
Average method complexity | 1.83 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 36 | |
▷ Static methods | 5 | 13.89% |
▷ Public methods | 31 | 86.11% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 13.89% |
Functions | 10 | |
▷ Named functions | 10 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.27MB with 0.16MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
admin/images/ravisoni.png | 278.09KB | 110.22KB | ▼ 60.36% |