Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.11MB] [CPU: ▼3.87ms] Passed 4 tests
Server-side resources used by FlagShip WooCommerce Shipping
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.07 | 44.98 ▼0.71 |
| Dashboard /wp-admin | 3.43 ▲0.12 | 49.35 ▼0.76 |
| Posts /wp-admin/edit.php | 3.54 ▲0.18 | 49.06 ▼0.80 |
| Add New Post /wp-admin/post-new.php | 6.01 ▲0.12 | 91.13 ▼13.22 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 35.66 ▲1.73 |
Server storage [IO: ▲0.48MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 157 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| flagship_shipping_method_data_migrations |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
FlagShip WooCommerce Shipping: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,790 ▲3 | 14.67 ▼0.04 | 1.65 ▼0.31 | 45.76 ▲0.68 |
| Dashboard /wp-admin | 2,195 ▲21 | 5.51 ▼0.16 | 87.36 ▼16.72 | 40.06 ▼7.16 |
| Posts /wp-admin/edit.php | 2,100 ▲18 | 2.02 ▼0.02 | 33.89 ▼6.77 | 33.24 ▼1.86 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.23 ▲0.03 | 652.34 ▼18.40 | 50.81 ▼7.17 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.19 ▲0.04 | 102.45 ▼1.46 | 44.50 ▲0.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin cannot be uninstalled
- > Warning in wp-includes/functions.php+6691
file_get_contents(wp-content/plugins/flagship-woocommerce-shipping/flagship-for-woocommerce.php): failed to open stream: No such file or directory
- This plugin did not uninstall successfully, leaving 8 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- flagship_shipping_method_data_migrations
- recovery_mode_email_last_sent
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
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
Almost there! Just fix the following items
- 107× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\AbstractComponent' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Shipping/RateProcessor/ProcessRateProcessor.php:8
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\Validation\\AbstractValidator' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Validation/PhoneValidator.php:7
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\AbstractComponent' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Shipping/Request/Builder/Order/ShippingServiceBuilder.php:8
- > PHP Fatal error
Uncaught Error: Interface 'FS\\Injection\\InjectorInterface' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Injection/Injector/Asset.php:7
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\Shipping\\Request\\Factory\\AbstractRequestFactory' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Shipping/Request/Factory/ShoppingCartRate.php:8
- > PHP Notice
Undefined variable: packing_box_field_name in wp-content/plugins/flagship-woocommerce-shipping/templates/option/box-split.php on line 1
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\AbstractComponent' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Model/AbstractModel.php:7
- > PHP Fatal error
Uncaught Error: Class 'FS\\Components\\AbstractComponent' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Components/Shipping/Request/Builder/AbstractPackageItemsBuilder.php:7
- > PHP Fatal error
Uncaught Error: Interface 'FS\\Context\\ApplicationContextAwareInterface' not found in wp-content/plugins/flagship-woocommerce-shipping/src/Context/Support/AbstractApplicationObjectSupport.php:5
- > PHP Notice
Undefined variable: tooltip_html in wp-content/plugins/flagship-woocommerce-shipping/templates/option/box-split.php on line 3
- > 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 90% from 29 tests
readme.txt Passed 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
6 plugin tags: courier, woocommerce, e-commerce, shipping, ecommerce...
flagship-woocommerce-shipping/flagship-for-woocommerce.php 77% from 13 tests
The primary PHP file in "FlagShip WooCommerce Shipping" version 3.0.23 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("flagship-woocommerce-shipping.php" instead of "flagship-for-woocommerce.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Description: The description should be shorter than 140 characters (currently 339 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin10,442 lines of code in 153 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 144 | 2,219 | 435 | 9,343 |
| PO File | 2 | 439 | 585 | 886 |
| Bourne Shell | 1 | 21 | 7 | 99 |
| JSON | 2 | 0 | 0 | 58 |
| XML | 2 | 2 | 1 | 36 |
| JavaScript | 1 | 2 | 0 | 11 |
| Markdown | 1 | 3 | 0 | 9 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 6.65 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 159.00 |
| Average method complexity | 2.36 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 44 | |
| Interfaces | 21 | |
| Traits | 3 | |
| Classes | 107 | |
| ▷ Abstract classes | 10 | 9.35% |
| ▷ Concrete classes | 97 | 90.65% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 533 | |
| ▷ Static methods | 46 | 8.63% |
| ▷ Public methods | 444 | 83.30% |
| ▷ Protected methods | 88 | 16.51% |
| ▷ Private methods | 1 | 0.19% |
| Functions | 62 | |
| ▷ Named functions | 1 | 1.61% |
| ▷ Anonymous functions | 61 | 98.39% |
| Constants | 31 | |
| ▷ Global constants | 2 | 6.45% |
| ▷ Class constants | 29 | 93.55% |
| ▷ Public constants | 29 | 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
PNG images were not found in this plugin