Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼29.60ms] Passed 4 tests
A check of server-side resources used by WP fail2ban Blocklist
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.03 | 45.39 ▲3.54 |
| Dashboard /wp-admin | 3.34 ▼0.00 | 49.96 ▼18.34 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.21 ▼5.62 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 87.35 ▼94.30 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 39.38 ▼0.15 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 37 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by WP fail2ban Blocklist
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲54 | 13.22 ▼1.15 | 4.82 ▲2.87 | 43.08 ▼1.27 |
| Dashboard /wp-admin | 2,221 ▲18 | 5.83 ▲0.94 | 104.35 ▼13.91 | 40.54 ▼7.99 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.00 ▼0.05 | 34.56 ▼2.86 | 33.29 ▼2.13 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲13 | 23.19 ▲2.31 | 693.38 ▼173.43 | 68.61 ▼2.75 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.26 ▲0.05 | 112.68 ▲0.51 | 43.14 ▼12.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
Please take a closer look at the following
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'com\\wp_fail2ban\\addons\\Blocklist\\Coder' not found in wp-content/plugins/wpf2b-addon-blocklist/classes/Encoder.php:12
- > PHP Fatal error
Uncaught Error: Class 'com\\wp_fail2ban\\addons\\Blocklist\\Coder' not found in wp-content/plugins/wpf2b-addon-blocklist/classes/Decoder.php:15
- > 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 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: fail2ban, blocklist, security
wpf2b-addon-blocklist/addon.php 92% from 13 tests
The main PHP file in "WP fail2ban Blocklist" ver. 2.2.1 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wpf2b-addon-blocklist.php" instead of "addon.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin1,907 lines of code in 33 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 30 | 386 | 1,359 | 1,865 |
| JSON | 1 | 0 | 0 | 21 |
| JavaScript | 1 | 0 | 0 | 20 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 10.12 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 31.00 |
| Average method complexity | 3.47 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 6 | |
| Interfaces | 0 | |
| Traits | 4 | |
| Classes | 12 | |
| ▷ Abstract classes | 5 | 41.67% |
| ▷ Concrete classes | 7 | 58.33% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 61 | |
| ▷ Static methods | 43 | 70.49% |
| ▷ Public methods | 33 | 54.10% |
| ▷ Protected methods | 28 | 45.90% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 48 | |
| ▷ Named functions | 38 | 79.17% |
| ▷ Anonymous functions | 10 | 20.83% |
| Constants | 20 | |
| ▷ Global constants | 12 | 60.00% |
| ▷ Class constants | 8 | 40.00% |
| ▷ Public constants | 8 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon.png | 15.24KB | 9.61KB | ▼ 36.93% |