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.01MB] [CPU: ▲1.29ms] Passed 4 tests
Analyzing server-side resources used by WooTrack
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.44 ▼0.52 |
Dashboard /wp-admin | 3.31 ▲0.01 | 50.08 ▲1.62 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.30 ▲3.59 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 94.76 ▲1.22 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.17 ▲2.83 |
Server storage [IO: ▲0.93MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by WooTrack
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,803 ▲68 | 14.74 ▲0.31 | 1.73 ▲0.03 | 46.90 ▲1.83 |
Dashboard /wp-admin | 2,206 ▲18 | 5.83 ▲0.78 | 101.20 ▼3.50 | 39.65 ▼4.49 |
Posts /wp-admin/edit.php | 2,091 ▲2 | 1.98 ▼0.14 | 39.53 ▲4.00 | 36.65 ▲1.82 |
Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.29 ▲0.07 | 649.65 ▼27.02 | 49.85 ▼10.83 |
Media Library /wp-admin/upload.php | 1,394 ▲6 | 4.23 ▲0.02 | 102.00 ▼6.14 | 43.12 ▼1.75 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
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
Good news, no errors were detected
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
- 5× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/wootrack.php:87
- > PHP Fatal error
Uncaught Error: Class 'SoapClient' not found in wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/WSSecurity.php:28
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/Wootrack_Register_Shipping.php:8
- > PHP Fatal error
Uncaught Error: Class 'SoapClient' not found in wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/WSSecurity.php:28
- > PHP Fatal error
Uncaught Error: Class 'WC_Shipping_Method' not found in wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/WC_StarTrackExpress.php:4
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Plugin configuration), #2 (Shipping methods displayed to customer)
wootrack-startrack-shipping-for-woocommerce/wootrack.php 85% from 13 tests
The principal PHP file in "WooTrack" v. 0.1 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wootrack-startrack-shipping-for-woocommerce.php" instead of "wootrack.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis 5% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Please fix the following items
- For security reasons, never distribute binary or executable files with your plugin
- .crt - Security Certificate in Firefox, IE, Chrome, Safari
- ☣ wp-content/plugins/wootrack-startrack-shipping-for-woocommerce/secure/cacert.crt
- .crt - Security Certificate in Firefox, IE, Chrome, Safari
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
XML | 2 | 0 | 2 | 4,722 |
PHP | 12 | 359 | 757 | 1,302 |
Markdown | 1 | 28 | 0 | 38 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 18.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 94.00 |
Average method complexity | 2.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 17.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 2 | 22.22% |
▷ Concrete classes | 7 | 77.78% |
▷ Final classes | 0 | 0.00% |
Methods | 102 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 72 | 70.59% |
▷ Protected methods | 28 | 27.45% |
▷ Private methods | 2 | 1.96% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 2 | 50.00% |
▷ Class constants | 2 | 50.00% |
▷ Public constants | 2 | 100.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.31MB with 0.22MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 265.41KB | 72.09KB | ▼ 72.84% |
assets/screenshot-2.png | 51.86KB | 14.80KB | ▼ 71.46% |