Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.10MB] [CPU: ▼151.25ms] Passed 4 tests
An overview of server-side resources used by Infisecure
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.91 ▲0.07 | 35.01 ▼5.08 |
| Dashboard /wp-admin | 3.17 ▲0.11 | 47.80 ▼13.82 |
| Posts /wp-admin/edit.php | 3.28 ▲0.17 | 41.85 ▼6.70 |
| Add New Post /wp-admin/post-new.php | 5.52 ▲0.09 | 91.51 ▼579.38 |
| Media Library /wp-admin/upload.php | 3.11 ▲0.11 | 36.36 ▲2.21 |
| InfiSecure Setting /wp-admin/options-general.php?page=infisecure_option | 3.06 | 28.18 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
These are issues you should consider
- The plugin illegally modified 1 file (0.00KB) outside of "wp-content/plugins/infisecure/" and "wp-content/uploads/"
- (new file) infisecure_ns_cache
Filesystem: 7 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Infisecure
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,712 ▲140 | 15.89 ▲0.20 | 10.65 ▲0.65 | 44.36 ▼8.03 |
| Dashboard /wp-admin | 2,972 ▲38 | 5.96 ▼0.02 | 148.11 ▲0.23 | 110.50 ▼5.80 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.72 ▲0.02 | 61.15 ▼10.48 | 87.93 ▲2.53 |
| Add New Post /wp-admin/post-new.php | 1,607 ▼2,036 | 18.80 ▼1.89 | 409.06 ▼88.87 | 107.17 ▼3.60 |
| Media Library /wp-admin/upload.php | 1,815 ▲8 | 5.03 ▼0.01 | 144.35 ▼11.72 | 114.02 ▲4.26 |
| InfiSecure Setting /wp-admin/options-general.php?page=infisecure_option | 1,217 | 2.10 | 59.59 | 70.02 |
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
Please fix the following items
- This plugin did not uninstall without warnings or errors
- > Warning in wp-includes/class-wp-hook.php+303
call_user_func_array() expects parameter 1 to be a valid callback, class 'InfiSecure' does not have a method 'plugin_deactivation'
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Almost there, just fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=infisecure_option
- > Notice in wp-content/plugins/infisecure/includes/setting.php+129
Trying to access array offset on value of type bool
SRP 50% from 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
The following issues need your attention
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/infisecure/includes/setting.php:33
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/infisecure/includes/frontend-scripts.php:19
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/infisecure/infisecure.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
7 plugin tags: bot, explore frauds, detection, real time protection, real time traffic...
infisecure/infisecure.php 92% from 13 tests
The entry point to "Infisecure" version 1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Description: The description should be shorter than 140 characters (currently 154 characters long)
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
Success! There were no dangerous files found in this plugin626 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 77 | 103 | 626 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 7.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 3.74 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 19.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 | 19 | |
| ▷ Static methods | 3 | 15.79% |
| ▷ Public methods | 17 | 89.47% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 10.53% |
| Functions | 7 | |
| ▷ Named functions | 7 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
No PNG images were found in this plugin