Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼10.33ms] Passed 4 tests
An overview of server-side resources used by WooCommerce MWS Sync
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.04 | 37.88 ▼1.92 |
| Dashboard /wp-admin | 3.35 ▲0.01 | 53.40 ▼9.39 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 45.68 ▼5.68 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 80.37 ▼23.13 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 31.95 ▼3.10 |
Server storage [IO: ▲0.77MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 127 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for WooCommerce MWS Sync
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲68 | 14.27 ▼0.08 | 1.95 ▲0.49 | 43.95 ▲4.39 |
| Dashboard /wp-admin | 2,198 ▲17 | 5.61 ▼0.10 | 94.04 ▼2.00 | 42.56 ▼4.62 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.04 ▲0.04 | 34.84 ▼1.76 | 34.36 ▼1.83 |
| Add New Post /wp-admin/post-new.php | 1,535 ▼1 | 18.59 ▼6.37 | 634.61 ▲46.01 | 75.88 ▲2.81 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.15 ▼0.05 | 96.62 ▼2.54 | 42.37 ▲1.44 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 5× PHP files output text when accessed directly:
- > /wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Samples/CancelFeedSubmissionsSample.php
- > /wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Samples/GetReportSample.php
- > /wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Samples/RequestReportSample.php
- > /wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Samples/GetFeedSubmissionCountSample.php
- > /wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Samples/GetFeedSubmissionResultSample.php
- 170× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetFeedSubmissionCountRequest.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetReportScheduleListByNextTokenResult.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetFeedSubmissionResultResult.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/UpdateReportAcknowledgementsResponse.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetReportRequestCountResult.php on line 22
- > PHP Fatal error
require_once(): Failed opening required 'MarketplaceWebService/Model.php' (include_path='.:/usr/share/php') in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/UpdateReportAcknowledgementsRequest.php on line 22
- > PHP Fatal error
require_once(): Failed opening required 'MarketplaceWebService/Model.php' (include_path='.:/usr/share/php') in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetFeedSubmissionCountRequest.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetReportRequestListResult.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/SubmitFeedResponse.php on line 22
- > PHP Warning
require_once(MarketplaceWebService/Model.php): failed to open stream: No such file or directory in wp-content/plugins/woocommerce-mws-sync/api/src/MarketplaceWebService/Model/GetReportScheduleListResponse.php on line 22
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
8 plugin tags: sku, integration, amazon, sync, woocommerce...
woocommerce-mws-sync/woocommerce-mws-sync.php 92% from 13 tests
The principal PHP file in "WooCommerce MWS Sync" v. 1.0.2 is loaded by WordPress automatically on each request
Please take the time to fix the following:
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.0.1" instead of "3.0")
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
No dangerous file extensions were detected9,840 lines of code in 123 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 101 | 3,001 | 11,900 | 9,515 |
| XML | 21 | 0 | 25 | 313 |
| YAML | 1 | 4 | 1 | 12 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 5.41 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 222.00 |
| Average method complexity | 1.28 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 21.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 77 | |
| ▷ Abstract classes | 1 | 1.30% |
| ▷ Concrete classes | 76 | 98.70% |
| ▷ Final classes | 1 | 1.32% |
| Methods | 1,256 | |
| ▷ Static methods | 22 | 1.75% |
| ▷ Public methods | 1,200 | 95.54% |
| ▷ Protected methods | 2 | 0.16% |
| ▷ Private methods | 54 | 4.30% |
| Functions | 31 | |
| ▷ Named functions | 31 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 21 | |
| ▷ Global constants | 11 | 52.38% |
| ▷ Class constants | 10 | 47.62% |
| ▷ Public constants | 10 | 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
No PNG files were detected