Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.73ms] Passed 4 tests
An overview of server-side resources used by ShipperHQ for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.93 ▼1.69 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 44.87 ▼2.51 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.49 ▲2.59 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 81.65 ▼13.00 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.45 ▲2.27 |
Server storage [IO: ▲1.90MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 239 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
ShipperHQ for WooCommerce: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲53 | 14.24 ▼0.12 | 2.05 ▲0.29 | 43.39 ▼1.05 |
| Dashboard /wp-admin | 2,195 ▲14 | 5.58 ▼0.14 | 94.14 ▼8.10 | 39.36 ▲0.80 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.00 ▼0.01 | 38.80 ▲2.68 | 36.30 ▲2.93 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 23.23 ▲0.09 | 677.90 ▲36.44 | 54.23 ▼1.26 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.18 ▼0.12 | 100.27 ▲5.09 | 43.46 ▲2.90 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Please fix the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/woo-shipperhq/includes/external/lib/jsonmapper/example/run.php
- 91× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'ShipperHQ\\WS\\AbstractWebServiceRequest' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/library-ws/src/PostOrder/Placeorder/Request/PlaceOrderRequest.php:23
- > PHP Fatal error
Uncaught Error: Class 'Lcobucci\\JWT\\Signer\\OpenSSL' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Signer/Rsa.php:18
- > PHP Fatal error
Uncaught Error: Class 'Lcobucci\\JWT\\Claim\\Basic' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Claim/GreaterOrEqualsTo.php:21
- > PHP Fatal error
Uncaught Error: Class 'Lcobucci\\JWT\\Signer\\Rsa' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Signer/Rsa/Sha384.php:18
- > PHP Fatal error
Uncaught Error: Interface 'Lcobucci\\JWT\\Claim' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Claim/Basic.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Lcobucci\\JWT\\Signer\\Ecdsa\\SignatureConverter' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Signer/Ecdsa/MultibyteStringConverter.php:29
- > PHP Fatal error
Uncaught Error: Class 'Lcobucci\\JWT\\Claim\\Basic' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/jwt/src/Claim/LesserOrEqualsTo.php:21
- > PHP Notice
Trying to get property 'lat' of non-object in wp-content/plugins/woo-shipperhq/includes/external/lib/jsonmapper/example/Address.php on line 17
- > PHP Fatal error
Uncaught Error: Interface 'ShipperHQ\\GraphQL\\Response\\ResponseInterface' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/library-graphql/src/Response/CreateListing.php:16
- > PHP Fatal error
Uncaught Error: Class 'Magento\\Framework\\Component\\ComponentRegistrar' not found in wp-content/plugins/woo-shipperhq/includes/external/lib/library-graphql/src/registration.php:12
- > PHP Fatal error
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 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Tags: You are using too many tags: 15 tag instead of maximum 10
woo-shipperhq/woocommerce-shipperhq.php 92% from 13 tests
The main file in "ShipperHQ for WooCommerce" v. 1.6.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
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 ("woo-shipperhq.php" instead of "woocommerce-shipperhq.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin12,220 lines of code in 214 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 189 | 2,656 | 9,210 | 10,898 |
| Markdown | 9 | 267 | 0 | 441 |
| JavaScript | 1 | 131 | 218 | 268 |
| reStructuredText | 2 | 175 | 155 | 255 |
| JSON | 6 | 1 | 0 | 184 |
| YAML | 4 | 10 | 0 | 123 |
| XML | 2 | 1 | 0 | 47 |
| CSS | 1 | 2 | 13 | 4 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| Average class complexity | 4.40 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 128.00 |
| Average method complexity | 1.48 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 45.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 36 | |
| Interfaces | 10 | |
| Traits | 1 | |
| Classes | 168 | |
| ▷ Abstract classes | 12 | 7.14% |
| ▷ Concrete classes | 156 | 92.86% |
| ▷ Final classes | 5 | 3.21% |
| Methods | 1,266 | |
| ▷ Static methods | 27 | 2.13% |
| ▷ Public methods | 1,123 | 88.70% |
| ▷ Protected methods | 45 | 3.55% |
| ▷ Private methods | 98 | 7.74% |
| Functions | 12 | |
| ▷ Named functions | 2 | 16.67% |
| ▷ Anonymous functions | 10 | 83.33% |
| Constants | 41 | |
| ▷ Global constants | 1 | 2.44% |
| ▷ Class constants | 40 | 97.56% |
| ▷ Public constants | 40 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin