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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.27MB] [CPU: ▼1.26ms] Passed 4 tests
This is a short check of server-side resources used by Anti-Brute Force, Login Fraud Detector Wordpress plugin
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.72 ▲0.26 | 39.03 ▼8.28 |
| Dashboard /wp-admin | 3.57 ▲0.27 | 50.83 ▼2.75 |
| Posts /wp-admin/edit.php | 3.68 ▲0.33 | 54.28 ▲2.17 |
| Add New Post /wp-admin/post-new.php | 6.17 ▲0.28 | 98.20 ▲3.84 |
| Media Library /wp-admin/upload.php | 3.49 ▲0.27 | 41.95 ▲4.32 |
Server storage [IO: ▲0.89MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 21 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_criminalip |
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Anti-Brute Force, Login Fraud Detector Wordpress plugin
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,819 ▲58 | 13.74 ▼0.97 | 1.91 ▲0.22 | 39.33 ▼6.34 |
| Dashboard /wp-admin | 2,213 ▲36 | 5.76 ▲0.15 | 94.17 ▼1.43 | 76.11 ▲33.28 |
| Posts /wp-admin/edit.php | 2,130 ▲27 | 2.73 ▲0.78 | 43.79 ▲3.95 | 36.08 ▼0.54 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲26 | 23.54 ▲0.53 | 627.45 ▼53.81 | 33.24 ▼21.49 |
| Media Library /wp-admin/upload.php | 1,421 ▲24 | 5.26 ▲1.06 | 108.33 ▼0.66 | 88.35 ▲42.27 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 4× PHP files trigger server errors when accessed directly:
- > PHP Warning
require_once(ABSPATHwp-admin/includes/screen.php): failed to open stream: No such file or directory in wp-content/plugins/anti-brute-force-login-fraud-detector/admin/partials/wp-list-table.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/anti-brute-force-login-fraud-detector/index.php:47
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/anti-brute-force-login-fraud-detector/admin/partials/wp-list-table.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/screen.php' (include_path='.:/usr/share/php') in wp-content/plugins/anti-brute-force-login-fraud-detector/admin/partials/wp-list-table.php on line 3
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% 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
7 plugin tags: brute force protection, login security, anti-brute force, limit login, security...
anti-brute-force-login-fraud-detector/index.php 85% from 13 tests
Analyzing the main PHP file in "Anti-Brute Force, Login Fraud Detector Wordpress plugin" version 1.0.3
You should first fix the following items:
- Description: The description should be shorter than 140 characters (currently 446 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("anti-brute-force-login-fraud-detector.php" instead of "index.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,580 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 167 | 18 | 1,031 |
| PO File | 3 | 191 | 306 | 541 |
| JavaScript | 3 | 0 | 29 | 5 |
| SVG | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 9.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 21.00 |
| Average method complexity | 2.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 12 | |
| ▷ Static methods | 3 | 25.00% |
| ▷ Public methods | 12 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 24 | |
| ▷ Named functions | 24 | 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
4 PNG files occupy 0.20MB with 0.11MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon.png | 8.66KB | 4.28KB | ▼ 50.56% |
| images/logout.png | 1.95KB | 0.94KB | ▼ 52.02% |
| images/banner.png | 185.32KB | 63.38KB | ▼ 65.80% |
| images/logo.png | 5.94KB | 2.95KB | ▼ 50.41% |