Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.74ms] Passed 4 tests
Server-side resources used by WP fail2ban Add-on for Contact Form 7
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 36.26 ▼4.29 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 45.47 ▼2.75 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.94 ▲0.11 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.91 ▼6.38 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.43 ▼1.55 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
WP fail2ban Add-on for Contact Form 7: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.30 ▼1.10 | 1.65 ▼0.22 | 41.09 ▼4.46 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.81 ▲0.00 | 107.90 ▼7.22 | 39.71 ▼3.07 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.18 ▲0.19 | 39.56 ▲1.10 | 36.24 ▲1.22 |
| Add New Post /wp-admin/post-new.php | 1,517 ▼18 | 17.92 ▼5.24 | 617.67 ▼63.19 | 50.50 ▼7.12 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.19 ▼0.06 | 99.04 ▼1.86 | 41.13 ▼4.40 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: contact form 7, fail2ban, security, classicpress, spam
wp-fail2ban-addon-contact-form-7/addon.php 85% from 13 tests
The entry point to "WP fail2ban Add-on for Contact Form 7" version 2.0.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-fail2ban-addon-contact-form-7.php" instead of "addon.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin335 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 71 | 243 | 314 |
| JSON | 1 | 0 | 0 | 21 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.61 |
| Average class complexity | 4.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 4.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 3 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 1 | 33.33% |
| ▷ Concrete classes | 2 | 66.67% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 3 | |
| ▷ Static methods | 3 | 100.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 12 | |
| ▷ Named functions | 10 | 83.33% |
| ▷ Anonymous functions | 2 | 16.67% |
| Constants | 8 | |
| ▷ Global constants | 8 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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 | 13.19KB | 6.99KB | ▼ 47.04% |