Benchmarks
Plugin footprint 48% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▲4.16ms] Passed 4 tests
A check of server-side resources used by Woo Solo Api
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 44.80 ▲6.14 |
Dashboard /wp-admin | 3.31 ▲0.00 | 45.03 ▲0.09 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 54.14 ▲8.89 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 93.92 ▲5.24 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.16 ▲5.18 |
Server storage [IO: ▲1.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 221 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Woo Solo Api
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.69 ▼0.62 | 1.90 ▲0.07 | 42.53 ▼13.59 |
Dashboard /wp-admin | 2,209 ▲21 | 4.86 ▼0.04 | 100.15 ▼10.46 | 39.20 ▼5.76 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.04 ▼0.01 | 50.74 ▲9.37 | 39.25 ▲2.13 |
Add New Post /wp-admin/post-new.php | 1,543 ▲10 | 18.34 ▼4.80 | 649.93 ▼42.86 | 59.10 ▲2.88 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.21 ▲0.02 | 96.54 ▼5.78 | 42.20 ▼4.90 |
Uninstaller [IO: ▲1.01MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following itemsZombie WordPress options detected upon uninstall: 7 options
- Uninstall procedure had uncaught errors
- > Error in wp-content/plugins/woo-solo-api/uninstall.php+71
Uncaught Error: Call to undefined function WC() in wp-content/plugins/woo-solo-api/uninstall.php:71
Stack trace:
#0 wp-admin/includes/plugin.php(1245): include_once()
#1 wp-admin/includes/plugin.php(960): uninstall_plugin() - The plugin did not uninstall correctly, leaving 221 files (1.01MB) in the plugin directory
- (new file) README.md
- (new file) assets/public/assets/application-3c3a54ba.js.map
- (new file) CHANGELOG.md
- (new file) languages/woo-solo-api-hr-340d7e18ff6995a5fc0cc382b15e8694.json
- (new file) assets/public/assets/application-3c3a54ba.js
- (new file) LICENSE
- (new file) assets/public/assets/application-b79a819c.css
- (new file) assets/public/manifest.json
- (new file) languages/woo-solo-api-hr-13eea078c7ecc2d25d97ffbfcc42def6.json
- (new file) README.txt
- ...
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- recovery_mode_email_last_sent
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 | 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
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/woo-solo-api/views/options-page.php
- 102× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/woo-solo-api/woo-solo-api.php:43
- > PHP Fatal error
Uncaught Error: Interface 'Laravel\\SerializableClosure\\Contracts\\Signer' not found in wp-content/plugins/woo-solo-api/vendor/laravel/serializable-closure/src/Signers/Hmac.php:7
- > PHP Fatal error
Uncaught Error: Interface 'DI\\Definition\\Definition' not found in wp-content/plugins/woo-solo-api/vendor/php-di/php-di/src/Definition/EnvironmentVariableDefinition.php:13
- > PHP Fatal error
Uncaught Error: Interface 'MadeByDenis\\WooSoloApi\\Core\\Registrable' not found in wp-content/plugins/woo-solo-api/src/Rest/ModifySettingsRoute.php:29
- > PHP Fatal error
Uncaught Error: Interface 'DI\\Definition\\Source\\Autowiring' not found in wp-content/plugins/woo-solo-api/vendor/php-di/php-di/src/Definition/Source/NoAutowiring.php:15
- > PHP Fatal error
Uncaught Error: Class 'MadeByDenis\\WooSoloApi\\Rest\\BaseRoute' not found in wp-content/plugins/woo-solo-api/src/Rest/Endpoints/OrderDetailsCollection.php:29
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Container\\ContainerExceptionInterface' not found in wp-content/plugins/woo-solo-api/vendor/php-di/php-di/src/DependencyException.php:12
- > PHP Fatal error
Uncaught Error: Interface 'MadeByDenis\\WooSoloApi\\Exception\\GeneralException' not found in wp-content/plugins/woo-solo-api/src/Exception/FailedToLoadView.php:25
- > PHP Fatal error
Uncaught Error: Interface 'DI\\Definition\\Helper\\DefinitionHelper' not found in wp-content/plugins/woo-solo-api/vendor/php-di/php-di/src/Definition/Helper/CreateDefinitionHelper.php:18
- > PHP Fatal error
Uncaught Error: Interface 'DI\\Definition\\Definition' not found in wp-content/plugins/woo-solo-api/vendor/php-di/php-di/src/Definition/InstanceDefinition.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
8 plugin tags: api integration, payment, woocommerce, solo api, api...
woo-solo-api/woo-solo-api.php 92% from 13 tests
The main file in "Woo Solo Api" v. 3.2.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:
- Requires at least: Required version does not match the one declared in readme.txt ("6.0" instead of "7.0.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin12,553 lines of code in 206 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 169 | 2,554 | 6,097 | 10,047 |
Markdown | 16 | 626 | 0 | 1,269 |
JSON | 13 | 0 | 0 | 567 |
PO File | 1 | 211 | 239 | 503 |
YAML | 3 | 9 | 1 | 132 |
XML | 2 | 9 | 3 | 33 |
CSS | 1 | 0 | 0 | 1 |
JavaScript | 1 | 0 | 10 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 9.08 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 318.00 |
Average method complexity | 2.84 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 63.00 |
Code structure | ||
---|---|---|
Namespaces | 51 | |
Interfaces | 29 | |
Traits | 1 | |
Classes | 125 | |
▷ Abstract classes | 5 | 4.00% |
▷ Concrete classes | 120 | 96.00% |
▷ Final classes | 16 | 13.33% |
Methods | 609 | |
▷ Static methods | 53 | 8.70% |
▷ Public methods | 467 | 76.68% |
▷ Protected methods | 58 | 9.52% |
▷ Private methods | 84 | 13.79% |
Functions | 49 | |
▷ Named functions | 22 | 44.90% |
▷ Anonymous functions | 27 | 55.10% |
Constants | 55 | |
▷ Global constants | 4 | 7.27% |
▷ Class constants | 51 | 92.73% |
▷ Public constants | 42 | 82.35% |
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