Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼138.26ms] Passed 4 tests
Server-side resources used by Widgets Control
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.92 ▲0.08 | 36.35 ▲4.08 |
| Dashboard /wp-admin | 3.12 ▲0.06 | 44.58 ▼0.90 |
| Posts /wp-admin/edit.php | 3.21 ▲0.10 | 43.33 ▲2.04 |
| Add New Post /wp-admin/post-new.php | 5.48 ▲0.05 | 99.22 ▼547.43 |
| Media Library /wp-admin/upload.php | 3.06 ▲0.05 | 35.03 ▼6.74 |
| Widgets Control /wp-admin/plugins.php?page=widgets-plugin | 3.03 | 29.29 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 31 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| widget_widgets_control_content_block |
Browser metrics Passed 4 tests
Checking browser requirements for Widgets Control
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,723 ▲127 | 15.89 ▲0.28 | 8.28 ▼0.34 | 48.18 ▲1.47 |
| Dashboard /wp-admin | 3,007 ▲76 | 5.93 ▼0.11 | 141.43 ▲7.47 | 114.44 ▼1.85 |
| Posts /wp-admin/edit.php | 2,779 ▲40 | 2.68 ▼0.01 | 66.40 ▼2.23 | 94.21 ▲1.97 |
| Add New Post /wp-admin/post-new.php | 1,742 ▲72 | 18.94 ▲1.53 | 381.59 ▲19.99 | 111.04 ▲2.06 |
| Media Library /wp-admin/upload.php | 1,847 ▲40 | 5.01 ▼0.01 | 152.79 ▼4.52 | 123.50 ▼1.29 |
| Widgets Control /wp-admin/plugins.php?page=widgets-plugin | 1,087 | 2.05 | 57.83 | 67.74 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options detected upon uninstall: 1 option
- widget_widgets_control_content_block
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Looking good! No server-side errors or output on direct access of PHP files
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 93% from 29 tests
readme.txt 88% 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
Attributes that need to be fixed:
- Screenshots: These screenshots lack descriptions #10, #11, #12, #13, #14, #6, #7, #8, #9 in widgets-control/assets to your readme.txt
- Tags: Too many tags (19 tag instead of maximum 10); only the first 5 tags are used in your directory listing
widgets-control/widgets-control.php Passed 13 tests
Analyzing the main PHP file in "Widgets Control" version 2.5.0
119 characters long description:
A Widget toolbox that adds visibility management and helps to control where widgets and sidebars are shown efficiently.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin2,368 lines of code in 23 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 19 | 249 | 1,002 | 1,995 |
| PO File | 1 | 76 | 103 | 236 |
| JavaScript | 1 | 4 | 23 | 94 |
| CSS | 2 | 4 | 0 | 43 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 27.67 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 66.00 |
| Average method complexity | 5.55 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 40.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 15 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 15 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 88 | |
| ▷ Static methods | 82 | 93.18% |
| ▷ Public methods | 80 | 90.91% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 8 | 9.09% |
| Functions | 8 | |
| ▷ Named functions | 8 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 28 | |
| ▷ Global constants | 18 | 64.29% |
| ▷ Class constants | 10 | 35.71% |
| ▷ Public constants | 10 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/wctrl_gear-20x20.png | 1.58KB | 0.64KB | ▼ 59.39% |
| images/wctrl_gear.png | 5.41KB | 2.59KB | ▼ 52.14% |