Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
You still need to fix the following installer errors
- The plugin did not install without errors
- > User notice in wp-includes/functions.php+5905
Function wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.)
Server metrics [RAM: ▲0.02MB] [CPU: ▼10.89ms] Passed 4 tests
Server-side resources used by Shipsy's FlowPL Extension
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 35.87 ▼4.29 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 44.46 ▼19.81 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 45.88 ▼0.72 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 88.68 ▼18.68 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 34.12 ▼0.76 |
Server storage [IO: ▲0.52MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 42 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_sync_track_order |
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Shipsy's FlowPL Extension: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲29 | 13.38 ▼0.81 | 1.72 ▼0.09 | 41.88 ▼0.26 |
| Dashboard /wp-admin | 2,206 ▲14 | 4.84 ▼0.11 | 108.21 ▼4.98 | 37.79 ▼3.43 |
| Posts /wp-admin/edit.php | 2,086 ▼6 | 2.02 ▼0.02 | 39.78 ▲1.23 | 35.06 ▲4.35 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.19 ▼0.39 | 641.53 ▼116.04 | 50.52 ▼4.06 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.24 ▲0.02 | 98.62 ▼9.18 | 40.14 ▼4.38 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > User notice in wp-includes/functions.php+5905
Function wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.)
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/shipsys-flowpl-extension/public/partials/dtdc-econnect-public-display.php
- > /wp-content/plugins/shipsys-flowpl-extension/admin/partials/dtdc-econnect-admin-display.php
- 26× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Warning
include_once(): Failed opening 'DTDC_ECONNECT_PATHadmin/helper/helper.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/shipsys-flowpl-extension/admin/apis/js-shipping-address-helper-api.php on line 2
- > PHP Fatal error
Uncaught Error: Call to undefined function shipsySanitizeArray() in wp-content/plugins/shipsys-flowpl-extension/admin/apis/js-shipping-address-helper-api.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/shipsys-flowpl-extension/admin/partials/ec-sync-form.php:5
- > PHP Fatal error
require_once(): Failed opening required 'DTDC_ECONNECT_PATHadmin/helper/helper.php' (include_path='.:/usr/share/php') in wp-content/plugins/shipsys-flowpl-extension/admin/partials/ec-setup.php on line 2
- > PHP Fatal error
require(): Failed opening required 'DTDC_ECONNECT_PATHconfig/settings.php' (include_path='.:/usr/share/php') in wp-content/plugins/shipsys-flowpl-extension/admin/apis/js-endpoint-helper-api.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'DTDC_ECONNECT_PATHadmin/helper/helper.php' (include_path='.:/usr/share/php') in wp-content/plugins/shipsys-flowpl-extension/admin/partials/ec-vseries.php on line 2
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/upgrade.php' (include_path='.:/usr/share/php') in wp-content/plugins/shipsys-flowpl-extension/utils/db/class-shipsydbconnector.php on line 3
- > PHP Warning
include_once(DTDC_ECONNECT_PATHadmin/helper/helper.php): failed to open stream: No such file or directory in wp-content/plugins/shipsys-flowpl-extension/admin/apis/js-addresses-helper-api.php on line 3
- > PHP Warning
require_once(DTDC_ECONNECT_PATHadmin/helper/helper.php): failed to open stream: No such file or directory in wp-content/plugins/shipsys-flowpl-extension/admin/partials/ec-setup.php on line 2
- > PHP Fatal error
Uncaught Error: Call to undefined function dtdcGetAddresses() in wp-content/plugins/shipsys-flowpl-extension/admin/apis/js-addresses-helper-api.php:5
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
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
3 plugin tags: ecommerce, shipsy, flowpl
shipsys-flowpl-extension/dtdc-econnect.php 85% from 13 tests
The main file in "Shipsy's FlowPL Extension" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("shipsys-flowpl-extension.php" instead of "dtdc-econnect.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 Passed 3 tests
File types Passed 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
Good job! No executable or dangerous file extensions detected4,095 lines of code in 36 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 25 | 311 | 703 | 2,103 |
| JavaScript | 6 | 286 | 260 | 1,312 |
| CSS | 5 | 0 | 22 | 680 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 6.25 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 31.00 |
| Average method complexity | 1.79 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 52 | |
| ▷ Static methods | 1 | 1.92% |
| ▷ Public methods | 45 | 86.54% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 7 | 13.46% |
| Functions | 27 | |
| ▷ Named functions | 27 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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
No PNG files were detected