Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼147.37ms] Passed 4 tests
Server-side resources used by Verifyne
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.94 ▲0.22 | 38.11 ▲14.77 |
| Dashboard /wp-admin | 3.17 ▲0.11 | 50.67 ▲0.67 |
| Posts /wp-admin/edit.php | 3.28 ▲0.17 | 53.36 ▲3.33 |
| Add New Post /wp-admin/post-new.php | 5.52 ▲0.09 | 96.27 ▼594.51 |
| Media Library /wp-admin/upload.php | 3.11 ▲0.11 | 38.79 ▲1.02 |
| Verifyne /wp-admin/options-general.php?page=verifyne | 3.08 | 31.37 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 10 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Verifyne
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,690 ▲94 | 15.77 ▲0.38 | 9.26 ▼1.55 | 50.25 ▼2.94 |
| Dashboard /wp-admin | 2,978 ▲47 | 5.94 ▼0.21 | 145.26 ▼13.54 | 120.74 ▲3.28 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.72 ▲0.00 | 69.11 ▼3.74 | 91.77 ▼9.74 |
| Add New Post /wp-admin/post-new.php | 1,686 ▲71 | 18.80 ▼2.74 | 388.24 ▲86.42 | 117.70 ▲1.58 |
| Media Library /wp-admin/upload.php | 1,812 ▲5 | 5.03 ▼0.09 | 173.58 ▲16.14 | 130.47 ▲5.44 |
| Verifyne /wp-admin/options-general.php?page=verifyne | 1,087 | 2.22 | 59.04 | 78.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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
The following issues need your attention
- 6× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/verifyne/vf_register_page.php
- > /wp-content/plugins/verifyne/wp-verifyne.php
- > /wp-content/plugins/verifyne/vf_verifyne_api.php
- > /wp-content/plugins/verifyne/vf_admin_settings.php
- > /wp-content/plugins/verifyne/vf_user_profile.php
- > /wp-content/plugins/verifyne/vf_login_page.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: security, password, login
verifyne/wp-verifyne.php 92% from 13 tests
"Verifyne" version 0.3.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("verifyne.php" instead of "wp-verifyne.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
There were no executable files found in this plugin565 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 211 | 216 | 483 |
| CSS | 1 | 5 | 0 | 43 |
| JavaScript | 1 | 4 | 10 | 39 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 14.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 3.61 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 6 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 31 | |
| ▷ Static methods | 5 | 16.13% |
| ▷ Public methods | 31 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 2 | 100.00% |
| ▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
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 |
| vf_button_login.png | 14.05KB | 6.71KB | ▼ 52.22% |