Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼17.14ms] Passed 4 tests
Analyzing server-side resources used by Checkout Field Visibility for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 41.29 ▼8.12 |
Dashboard /wp-admin | 3.31 ▼0.04 | 46.19 ▼19.40 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.32 ▼21.83 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.15 ▼19.22 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.58 ▲2.66 |
Dashboard /wp-admin/admin.php?page=zamartz-admin | 3.00 | 20.85 |
Status /wp-admin/admin.php?page=zamartz-status | 3.00 | 31.24 |
Settings /wp-admin/admin.php?page=zamartz-settings | 3.00 | 22.28 |
Server storage [IO: ▲0.41MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 52 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Checkout Field Visibility for WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,814 ▲68 | 14.34 ▼0.03 | 1.96 ▼0.28 | 45.02 ▲2.01 |
Dashboard /wp-admin | 2,195 ▲15 | 5.62 ▼0.08 | 84.43 ▼15.68 | 41.10 ▼1.05 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▼0.02 | 33.55 ▼2.82 | 34.73 ▼1.48 |
Add New Post /wp-admin/post-new.php | 1,526 ▼1 | 23.16 ▲0.14 | 667.65 ▼28.46 | 63.21 ▲5.04 |
Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.18 ▼0.01 | 144.74 ▲47.99 | 56.28 ▲11.07 |
Dashboard /wp-admin/admin.php?page=zamartz-admin | 28 | 0.42 | 0.09 | 6.16 |
Status /wp-admin/admin.php?page=zamartz-status | 28 | 0.42 | 0.07 | 7.80 |
Settings /wp-admin/admin.php?page=zamartz-settings | 28 | 0.42 | 0.17 | 3.86 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
Smoke tests 50% 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)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 12× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/class-zamartz-network-admin-addons.php on line 22
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/network/class-zamartz-network-settings.php on line 12
- > PHP Fatal error
Trait 'Zamartz_HTML_Template' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/helper/trait-zamartz-rss-methods.php on line 12
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/partials/wp-checkout-vis-fields-woo-admin-html-form.php:22
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/class-zamartz-settings.php on line 12
- > PHP Fatal error
Trait 'Zamartz_HTML_Template' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/class-zamartz-status.php on line 12
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/network/class-zamartz-network-dashboard.php on line 12
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/class-zamartz-admin-addons.php on line 22
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/zamartz/class-zamartz-dashboard.php on line 12
- > PHP Fatal error
Trait 'Zamartz_General' not found in wp-content/plugins/checkout-field-visibility-for-woocommerce/admin/class-wp-checkout-vis-fields-woo-settings.php on line 22
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please fix the following browser errors
- > GET request to /wp-admin/admin.php?page=zamartz-admin
- > Network (severe)
wp-admin/admin.php?page=zamartz-admin - Failed to load resource: the server responded with a status of 403 (Forbidden)
- > GET request to /wp-admin/admin.php?page=zamartz-status
- > Network (severe)
wp-admin/admin.php?page=zamartz-status - Failed to load resource: the server responded with a status of 403 (Forbidden)
- > GET request to /wp-admin/admin.php?page=zamartz-settings
- > Network (severe)
wp-admin/admin.php?page=zamartz-settings - Failed to load resource: the server responded with a status of 403 (Forbidden)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: woocommerce checkout fields, shipping, ecommerce, billing, checkout field customizer...
checkout-field-visibility-for-woocommerce/wp-checkout-vis-fields-woo.php 85% from 13 tests
"Checkout Field Visibility for WooCommerce" version 1.2.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("checkout-field-visibility-for-woocommerce.php" instead of "wp-checkout-vis-fields-woo.php")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin6,978 lines of code in 44 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 35 | 841 | 2,249 | 5,227 |
CSS | 4 | 230 | 52 | 1,030 |
JavaScript | 4 | 72 | 48 | 720 |
SVG | 1 | 0 | 0 | 1 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
The following items need your attention
- Please reduce cyclomatic complexity of methods to less than 100 (currently 192)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 26.79 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 311.00 |
Average method complexity | 4.93 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 192.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 4 | |
Classes | 25 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 25 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 189 | |
▷ Static methods | 2 | 1.06% |
▷ Public methods | 180 | 95.24% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 9 | 4.76% |
Functions | 9 | |
▷ Named functions | 6 | 66.67% |
▷ Anonymous functions | 3 | 33.33% |
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
It is recommended to compress PNG files in your plugin to 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 |
admin/zamartz/assets/images/zamartz-icon-menu.png | 0.43KB | 0.50KB | 0.00% |
admin/images/dashboard-default.png | 7.03KB | 3.46KB | ▼ 50.76% |