Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.17ms] Passed 4 tests
An overview of server-side resources used by BugPlug by OMATUM
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.62 ▲0.34 |
Dashboard /wp-admin | 3.32 ▼0.02 | 46.44 ▼9.63 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 44.05 ▼3.87 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 79.09 ▼19.53 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.43 ▲0.96 |
Server storage [IO: ▲0.01MB] [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: 4 new files
Database: no new tables, 11 new options
New WordPress options |
---|
bugplug_board |
widget_recent-comments |
bugplug_switch |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
bugplug_color |
bugplug_api_key |
bugplug_vars |
theysaidso_admin_options |
... |
Browser metrics Passed 4 tests
This is an overview of browser requirements for BugPlug by OMATUM
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,811 ▲65 | 13.24 ▼1.13 | 1.76 ▼0.03 | 43.65 ▲1.43 |
Dashboard /wp-admin | 2,220 ▲29 | 5.84 ▲0.92 | 113.07 ▲10.83 | 77.14 ▲36.59 |
Posts /wp-admin/edit.php | 2,097 ▲8 | 2.01 ▲0.02 | 41.56 ▲4.35 | 37.23 ▲5.18 |
Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 22.98 ▼0.26 | 746.89 ▲71.70 | 56.64 ▼4.70 |
Media Library /wp-admin/upload.php | 1,399 ▲11 | 4.14 ▼0.07 | 116.30 ▲20.60 | 48.27 ▲1.60 |
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
These items require your attention
- This plugin does not fully uninstall, leaving 11 options in the database
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- bugplug_vars
- bugplug_api_key
- bugplug_switch
- widget_theysaidso_widget
- bugplug_color
- ...
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
Even though everything seems fine, this is not an exhaustive test
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
Please fix the following items
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/bugplug-by-omatum/admin.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/bugplug-by-omatum/plugin.php:25
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Screenshots: No descriptions were found for these screenshots #1, #2, #3, #4 in bugplug-by-omatum/assets to your readme.txt
bugplug-by-omatum/plugin.php 92% from 13 tests
The primary PHP file in "BugPlug by OMATUM" version 1.0.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("bugplug-by-omatum.php" instead of "plugin.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 plugin102 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 9 | 9 | 81 |
Markdown | 1 | 5 | 0 | 21 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.16 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 4 | 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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/icon.png | 1.34KB | 0.81KB | ▼ 39.62% |