Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.04MB] [CPU: ▼142.59ms] Passed 4 tests
An overview of server-side resources used by GM Variations Radio Buttons for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.88 ▲0.05 | 33.81 ▲1.34 |
Dashboard /wp-admin | 3.11 ▲0.05 | 51.94 ▲2.07 |
Posts /wp-admin/edit.php | 3.16 ▲0.05 | 56.60 ▲8.46 |
Add New Post /wp-admin/post-new.php | 5.46 ▲0.03 | 85.98 ▼577.04 |
Media Library /wp-admin/upload.php | 3.05 ▲0.05 | 35.79 ▲3.29 |
Server storage [IO: ▲0.21MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 17 new files
Database: no new tables, 4 new options
New WordPress options |
---|
gmrbw_showdesc |
gmrbw_showimg |
gmrbw_enable |
gmrbw_hide_unpurchase |
Browser metrics Passed 4 tests
Checking browser requirements for GM Variations Radio Buttons for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,757 ▲161 | 16.23 ▲0.66 | 12.71 ▲0.82 | 46.91 ▼1.37 |
Dashboard /wp-admin | 3,016 ▲85 | 6.50 ▲0.28 | 162.27 ▲10.30 | 119.89 ▲18.14 |
Posts /wp-admin/edit.php | 2,791 ▲52 | 2.77 ▲0.04 | 72.54 ▲8.17 | 106.06 ▲15.23 |
Add New Post /wp-admin/post-new.php | 1,704 ▲21 | 18.96 ▲0.20 | 408.18 ▲34.41 | 118.66 ▲9.90 |
Media Library /wp-admin/upload.php | 1,859 ▲49 | 5.17 ▲0.13 | 144.70 ▼8.38 | 123.17 ▲9.66 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 4 options in the database
- gmrbw_hide_unpurchase
- gmrbw_showimg
- gmrbw_showdesc
- gmrbw_enable
Smoke tests 75% from 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)
Even though no errors were found, this is by no means 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
The following issues need your attention
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/gm-variations-radio-buttons-for-woocommerce/includes/GMRBW_Radio_Button.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Contributors: The plugin contributors field is not present
- Screenshots: Please add descriptions for these screenshots #1, #2 in gm-variations-radio-buttons-for-woocommerce/assets to your readme.txt
gm-variations-radio-buttons-for-woocommerce/gm-variations-radio-buttons.php 85% from 13 tests
The main PHP script in "GM Variations Radio Buttons for WooCommerce" version 3.0 is automatically included on every request by WordPress
You should first fix the following items:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("gm-variations-radio-buttons-for-woocommerce.php" instead of "gm-variations-radio-buttons.php")
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
No dangerous file extensions were detected3,447 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 566 | 380 | 2,596 |
CSS | 3 | 113 | 19 | 575 |
PHP | 6 | 139 | 23 | 276 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 6.25 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 2.40 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 15 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 15 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
2 PNG files occupy 0.04MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/close_btn.png | 36.22KB | 17.59KB | ▼ 51.42% |
assets/js/select2/select2.png | 0.51KB | 0.99KB | 0.00% |