Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.55MB] [CPU: ▲1.22ms] Passed 4 tests
A check of server-side resources used by Banhammer – Monitor Site Traffic, Block Bad Users and Bots
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.64 ▲0.17 | 37.94 ▼1.71 |
Dashboard /wp-admin | 4.02 ▲0.72 | 49.83 ▲3.09 |
Posts /wp-admin/edit.php | 4.07 ▲0.72 | 49.08 ▲6.13 |
Add New Post /wp-admin/post-new.php | 6.54 ▲0.65 | 83.22 ▼1.87 |
Media Library /wp-admin/upload.php | 3.88 ▲0.65 | 37.76 ▲5.35 |
Armory /wp-admin/admin.php?page=banhammer-armory | 3.87 | 36.08 |
Tower /wp-admin/admin.php?page=banhammer-tower | 3.86 | 35.98 |
Settings /wp-admin/admin.php?page=banhammer | 3.87 | 36.28 |
Server storage [IO: ▲4.69MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 315 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_banhammer |
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Banhammer – Monitor Site Traffic, Block Bad Users and Bots
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,822 ▲61 | 14.27 ▼0.09 | 1.84 ▲0.22 | 43.41 ▲4.22 |
Dashboard /wp-admin | 2,231 ▲51 | 5.63 ▼0.05 | 80.92 ▼9.39 | 38.88 ▼2.20 |
Posts /wp-admin/edit.php | 2,130 ▲30 | 2.00 ▼0.03 | 33.24 ▼2.76 | 34.93 ▼0.56 |
Add New Post /wp-admin/post-new.php | 1,567 ▲39 | 22.75 ▼0.32 | 653.59 ▼13.83 | 49.30 ▼10.53 |
Media Library /wp-admin/upload.php | 1,430 ▲30 | 4.28 ▼0.05 | 99.58 ▼13.55 | 43.40 ▼4.36 |
Armory /wp-admin/admin.php?page=banhammer-armory | 1,974 | 2.54 | 50.26 | 34.40 |
Tower /wp-admin/admin.php?page=banhammer-tower | 1,952 | 2.54 | 45.39 | 27.46 |
Settings /wp-admin/admin.php?page=banhammer | 1,505 | 1.98 | 29.26 | 57.02 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
Smoke tests Passed 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 Passed 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 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
6 plugin tags: bots, ban, banhammer, security, block...
banhammer/banhammer.php Passed 13 tests
The main PHP script in "Banhammer – Monitor Site Traffic, Block Bad Users and Bots" version 3.4.1 is automatically included on every request by WordPress
42 characters long description:
Monitor traffic and ban unwanted visitors.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected25,073 lines of code in 278 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 252 | 0 | 1 | 20,289 |
PHP | 15 | 1,620 | 134 | 2,556 |
PO File | 1 | 420 | 431 | 1,261 |
JavaScript | 4 | 59 | 13 | 623 |
CSS | 6 | 63 | 22 | 344 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 35.00 |
▷ Minimum class complexity | 35.00 |
▷ Maximum class complexity | 35.00 |
Average method complexity | 3.12 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 16 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 16 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 125 | |
▷ Named functions | 125 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 11 | |
▷ Global constants | 11 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
12 PNG files occupy 0.11MB with 0.06MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/banhammer-bg-ban.png | 1.62KB | 0.42KB | ▼ 73.99% |
img/banhammer-loading.png | 5.81KB | 3.23KB | ▼ 44.37% |
img/banhammer-bg-fade.png | 0.93KB | 0.21KB | ▼ 77.26% |
img/banhammer-bg-warn.png | 1.57KB | 0.42KB | ▼ 73.07% |
img/banhammer-header.png | 54.31KB | 54.31KB | 0.01% |