Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼4.53ms] Passed 4 tests
Analyzing server-side resources used by MainWP Key Maker
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 36.02 ▼4.15 |
Dashboard /wp-admin | 3.30 ▼0.04 | 59.33 ▼13.50 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 60.18 ▲9.51 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 93.54 ▼9.97 |
Media Library /wp-admin/upload.php | 3.23 ▼0.00 | 48.04 ▲11.09 |
Server storage [IO: ▲0.08MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for MainWP Key Maker
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,934 ▲188 | 13.41 ▼1.01 | 1.87 ▼0.14 | 40.57 ▼2.82 |
Dashboard /wp-admin | 2,315 ▲115 | 4.93 ▲0.03 | 110.17 ▲6.39 | 75.90 ▲34.74 |
Posts /wp-admin/edit.php | 2,200 ▲97 | 2.16 ▲0.15 | 41.15 ▲3.18 | 35.62 ▲0.45 |
Add New Post /wp-admin/post-new.php | 1,618 ▲72 | 25.13 ▲2.06 | 599.30 ▼53.97 | 30.47 ▼21.96 |
Media Library /wp-admin/upload.php | 1,534 ▲134 | 4.37 ▲0.20 | 115.66 ▲7.36 | 67.78 ▲17.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
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 no errors were found, 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
Almost there! Just fix the following items
- 1× 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/mainwp-key-maker/mainwp-key-maker.php:264
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Tags: Too many tags (11 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: Screenshot #1 (The MainWP Key Maker form copy fields) image not found
- Donate link: Invalid url: ""
mainwp-key-maker/mainwp-key-maker.php Passed 13 tests
The principal PHP file in "MainWP Key Maker" v. 1.2 is loaded by WordPress automatically on each request
89 characters long description:
Easily convert a form into a "key" to use with the MainWP Bulk Settings Manager Extension
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
Everything looks great! No dangerous files found in this plugin470 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 99 | 161 | 419 |
CSS | 1 | 5 | 16 | 49 |
JavaScript | 2 | 0 | 11 | 2 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.40 |
Average class complexity | 41.00 |
▷ Minimum class complexity | 41.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 6.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.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
PNG files should be compressed to save space and minimize bandwidth usage
5 PNG files occupy 0.02MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/logo.png | 21.88KB | 3.59KB | ▼ 83.60% |
css/images/controls.png | 1.23KB | 1.28KB | 0.00% |
css/images/overlay.png | 0.11KB | 0.15KB | 0.00% |
css/images/loading_background.png | 0.13KB | 0.15KB | 0.00% |
css/images/border.png | 0.07KB | 0.10KB | 0.00% |