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.66MB] [CPU: ▼23.43ms] Passed 4 tests
An overview of server-side resources used by Cyberus Key
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 37.01 ▼3.24 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 42.77 ▼15.83 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 48.26 ▼3.33 |
| Add New Post /wp-admin/post-new.php | 3.21 ▼2.68 | 37.18 ▼71.33 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 32.64 ▼0.25 |
| Cyberus key settings /wp-admin/admin.php?page=cyberkey_settings | 3.22 | 30.69 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Cyberus Key
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,813 ▲67 | 13.26 ▼1.12 | 1.76 ▲0.16 | 44.07 ▲2.58 |
| Dashboard /wp-admin | 2,200 ▲12 | 5.80 ▲0.91 | 102.61 ▼12.22 | 43.98 ▼0.92 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.03 | 39.10 ▼3.17 | 35.89 ▼1.25 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲5 | 23.23 ▲4.77 | 664.45 ▲52.20 | 68.31 ▲16.24 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.14 ▼0.12 | 94.61 ▼3.11 | 41.73 ▼4.26 |
| Cyberus key settings /wp-admin/admin.php?page=cyberkey_settings | 825 | 2.06 | 22.55 | 25.92 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 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/cyberus-key/inc/cyberkey-class.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/cyberus-key/inc/cyberkey-login.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/cyberus-key/inc/cyberkey-scripts.php:43
- > PHP Fatal error
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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 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
Attributes that need to be fixed:
- Screenshots: A description for screenshot #3 is missing in cyberus-key/assets to your readme.txt
cyberus-key/cyberus-main.php 92% from 13 tests
The main file in "Cyberus Key" v. 1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("cyberus-key.php" instead of "cyberus-main.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin630 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 135 | 181 | 567 |
| JavaScript | 2 | 6 | 1 | 49 |
| CSS | 1 | 6 | 8 | 14 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 21.67 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 4.26 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 21.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 19 | |
| ▷ Static methods | 10 | 52.63% |
| ▷ Public methods | 16 | 84.21% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 15.79% |
| Functions | 9 | |
| ▷ Named functions | 8 | 88.89% |
| ▷ Anonymous functions | 1 | 11.11% |
| 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin