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.01MB] [CPU: ▼11.44ms] Passed 4 tests
A check of server-side resources used by TrackingMore Order Tracking for WooCommerce (Free plan available)
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 39.45 ▼1.95 |
Dashboard /wp-admin | 3.31 ▼0.04 | 50.36 ▼16.35 |
Posts /wp-admin/edit.php | 3.42 ▲0.07 | 51.56 ▲2.39 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.83 ▼25.61 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.84 ▼1.86 |
Server storage [IO: ▲3.30MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 50 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by TrackingMore Order Tracking for WooCommerce (Free plan available)
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.26 ▼0.01 | 1.58 ▼0.15 | 46.08 ▲1.20 |
Dashboard /wp-admin | 2,195 ▲24 | 5.60 ▼0.02 | 84.87 ▼10.32 | 40.76 ▼1.24 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.04 ▼0.00 | 40.30 ▲4.98 | 35.23 ▼1.52 |
Add New Post /wp-admin/post-new.php | 1,545 ▼0 | 23.10 ▼0.34 | 623.09 ▼44.29 | 53.06 ▼4.77 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.21 ▼0.08 | 95.10 ▼17.20 | 42.22 ▼8.28 |
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
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
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)
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 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
Please fix the following items
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php
- > /wp-content/plugins/trackingmore-woocommerce-tracking/trackingmore.php
- 14× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 453
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 540
- > PHP Notice
Undefined index: trackingmore in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 474
- > PHP Notice
Trying to get property 'couriers' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 474
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/trackingmore-woocommerce-tracking/trackingmore-fields.php:25
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 419
- > PHP Notice
Trying to get property 'couriers' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 262
- > PHP Warning
file_get_contents(/assets/js/couriers.json): failed to open stream: No such file or directory in wp-content/plugins/trackingmore-woocommerce-tracking/couriers.php on line 2
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 390
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/trackingmore-woocommerce-tracking/includes/views/trackingmore_meta_box.php on line 100
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Tags: Please delete some tags, you are using 31 tag instead of maximum 10
- Screenshots: Add descriptions for screenshots #7, #8, #9 in trackingmore-woocommerce-tracking/assets to your readme.txt
trackingmore-woocommerce-tracking/trackingmore.php 77% from 13 tests
The main PHP file in "TrackingMore Order Tracking for WooCommerce (Free plan available)" ver. 1.1.5 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("trackingmore-woocommerce-tracking.php" instead of "trackingmore.php")
- Description: Keep the plugin description shorter than 140 characters (currently 143 characters long)
- 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 Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected19,036 lines of code in 41 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 7,814 |
JavaScript | 13 | 32 | 17 | 5,711 |
PO File | 2 | 1,429 | 1,434 | 2,871 |
PHP | 18 | 633 | 110 | 2,611 |
CSS | 5 | 4 | 1 | 16 |
SVG | 1 | 0 | 0 | 13 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 26.45 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 71.00 |
Average method complexity | 3.80 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 17.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 1 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 1 | 10.00% |
Methods | 104 | |
▷ Static methods | 5 | 4.81% |
▷ Public methods | 82 | 78.85% |
▷ Protected methods | 8 | 7.69% |
▷ Private methods | 14 | 13.46% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 15 | |
▷ Global constants | 1 | 6.67% |
▷ Class constants | 14 | 93.33% |
▷ Public constants | 14 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/plugin/chosen/chosen-sprite@2x.png | 0.72KB | 0.83KB | 0.00% |
assets/plugin/chosen/chosen-sprite.png | 0.53KB | 0.88KB | 0.00% |