Benchmarks
Plugin footprint 47% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼1.73MB] [CPU: ▲228.28ms] 75% from 4 tests
A check of server-side resources used by Veiligvertoon | Safety information management for WooCommerce
Please have a look at the following items
- Extra CPU: Extra CPU usage must be kept under 200.00ms (currently 228.28ms on /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.26 ▼1.20 | 9.39 ▼30.74 |
| Dashboard /wp-admin | 2.28 ▼1.06 | 11.16 ▼49.84 |
| Posts /wp-admin/edit.php | 2.29 ▼1.07 | 570.55 ▲523.66 |
| Add New Post /wp-admin/post-new.php | 2.29 ▼3.60 | 571.23 ▲478.12 |
| Media Library /wp-admin/upload.php | 2.29 ▼0.94 | 550.83 ▲515.57 |
| Styling /wp-admin/admin.php?page=veiligvertoon-admin-menu-styling | 2.28 | 9.29 |
| Activatie /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation | 2.28 | 11.53 |
Server storage [IO: ▲1.34MB] [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: 83 new files
Database: no new tables, 10 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| veiligvertoonClientSecret |
| widget_recent-comments |
| can_compress_scripts |
| veiligvertoonClientId |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| veiligvertoon_product_balance |
| veiligvertoonUserId |
Browser metrics Passed 4 tests
Checking browser requirements for Veiligvertoon | Safety information management for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,932 ▲171 | 15.56 ▲1.21 | 7.32 ▲5.71 | 35.00 ▼5.71 |
| Dashboard /wp-admin | 2,199 ▲18 | 5.59 ▼0.03 | 81.75 ▼15.48 | 37.07 ▼3.58 |
| Posts /wp-admin/edit.php | 2,178 ▲78 | 4.12 ▲2.16 | 49.82 ▲14.92 | 33.89 ▼4.20 |
| Add New Post /wp-admin/post-new.php | 6,327 ▲4,801 | 23.61 ▲0.56 | 928.43 ▲291.58 | 38.04 ▼12.36 |
| Media Library /wp-admin/upload.php | 1,475 ▲81 | 5.83 ▲1.67 | 114.11 ▲19.00 | 45.08 ▼0.51 |
| Styling /wp-admin/admin.php?page=veiligvertoon-admin-menu-styling | 1,452 | 5.02 | 66.21 | 113.53 |
| Activatie /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation | 978 | 4.30 | 46.11 | 42.39 |
Uninstaller [IO: ▲1.34MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the followingZombie WordPress options were found after uninstall: 11 options
- This plugin did not uninstall without warnings or errors
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-font-awesome handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- This plugin has failed uninstalling correctly, leaving 83 files (1.34MB) in the plugin directory
- (new file) admin/js/authManager.js
- (new file) admin/js/customTooltips.js
- (new file) admin/css/veiligvertoon.css
- (new file) admin/js/adminProductDetailExtension/adminProductDetailExtension.js
- (new file) admin/js/settings/veiligvertoonActivationSettings.js
- (new file) admin/js/settings/veiligvertoonLicenseSettings.js
- (new file) .gitignore
- (new file) admin/js/adminProductDetailExtension/dynamicElementRenderer.js
- (new file) admin/css/productDetail.css
- (new file) admin/css/veiligvertoonSettings.css
- ...
- theysaidso_admin_options
- veiligvertoon_product_balance
- widget_theysaidso_widget
- veiligvertoonClientSecret
- veiligvertoonUserId
- can_compress_scripts
- veiligvertoonClientId
- recovery_mode_email_last_sent
- db_upgraded
- widget_recent-posts
- ...
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Please fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-settings handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-select2 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-colorpicker handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the custom handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-select-2 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-settings handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-colorpicker handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-font-awesome handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-font-awesome handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-dropzone handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-tippy-animations handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery-ui-tabs handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-toastr handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-jquery-confirm handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-parsley handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-shepherd handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the veiligvertoon handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the veiligvertoon handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-constants handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-tippytools handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-tippy handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-dropzone handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-autosize handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery-ui-tabs handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-toastr handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-jquery-confirm handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-parsley handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the veiligvertoon handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the cookie-util handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-shepherd handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-auth handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-custom-tour handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=veiligvertoon-admin-menu-activation
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the vv-custom-tour handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
SRP 0% 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 output text when accessed directly:
- > /wp-content/plugins/veiligvertoon/veiligvertoon.php
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/veiligvertoon/admin/settings/adminVeiligvertoonSettings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/veiligvertoon/admin/veiligvertoonAdminProductTableExtension.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/veiligvertoon/uninstall.php:5
- > 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 on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
7 plugin tags: msds, ghs, sds, veiligvertoon, clp...
veiligvertoon/veiligvertoon.php Passed 13 tests
This is the main PHP file of "Veiligvertoon | Safety information management for WooCommerce" version 1.1.11, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
21 characters long description:
Veiligvertoon plugin.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin17,091 lines of code in 74 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 29 | 1,959 | 1,589 | 9,666 |
| JSON | 6 | 0 | 0 | 5,237 |
| PHP | 16 | 227 | 302 | 1,195 |
| CSS | 14 | 90 | 30 | 805 |
| Markdown | 5 | 64 | 0 | 146 |
| HTML | 1 | 1 | 0 | 28 |
| SVG | 3 | 0 | 0 | 14 |
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.25 |
| Average class complexity | 6.77 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 23.00 |
| Average method complexity | 2.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 2 | 15.38% |
| ▷ Concrete classes | 11 | 84.62% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 64 | |
| ▷ Static methods | 55 | 85.94% |
| ▷ Public methods | 64 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 8 | |
| ▷ Named functions | 4 | 50.00% |
| ▷ Anonymous functions | 4 | 50.00% |
| Constants | 14 | |
| ▷ Global constants | 1 | 7.14% |
| ▷ Class constants | 13 | 92.86% |
| ▷ Public constants | 13 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| shared/images/product-status-examples/paused-example.png | 5.66KB | 2.67KB | ▼ 52.73% |
| shared/images/product-status-examples/active-example.png | 6.08KB | 2.83KB | ▼ 53.42% |