Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.23MB] [CPU: ▼0.95ms] Passed 4 tests
Analyzing server-side resources used by UniPayment Gateway for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.71 ▲0.25 | 51.50 ▲11.32 |
| Dashboard /wp-admin | 3.57 ▲0.27 | 51.56 ▲0.16 |
| Posts /wp-admin/edit.php | 3.62 ▲0.27 | 49.12 ▲0.68 |
| Add New Post /wp-admin/post-new.php | 6.09 ▲0.21 | 85.44 ▼7.37 |
| Media Library /wp-admin/upload.php | 3.43 ▲0.21 | 39.02 ▲2.72 |
Server storage [IO: ▲1.41MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 193 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for UniPayment Gateway for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.63 ▼0.72 | 2.09 ▲0.32 | 45.65 ▲3.87 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.87 ▼0.00 | 113.03 ▼3.04 | 42.56 ▼2.31 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.05 ▼0.00 | 35.86 ▼7.63 | 34.44 ▼3.70 |
| Add New Post /wp-admin/post-new.php | 1,519 ▲5 | 23.28 ▲5.63 | 661.09 ▼46.52 | 50.38 ▼1.33 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.19 ▼0.00 | 101.20 ▼22.69 | 42.30 ▼4.42 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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 items
- 63× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/guzzlehttp/psr7/src/Stream.php:12
- > PHP Parse error
syntax error, unexpected '|', expecting '{' in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/symfony/polyfill-intl-normalizer/bootstrap80.php on line 18
- > PHP Fatal error
Uncaught Error: Class 'Symfony\\Polyfill\\Intl\ormalizer\ormalizer' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/symfony/polyfill-intl-normalizer/Resources/stubs/Normalizer.php:3
- > PHP Fatal error
Uncaught Error: Interface 'UniPayment\\Client\\Model\\ModelInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/lib/Model/GetExchangeRateByCurrencyPairResponse.php:14
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/guzzlehttp/psr7/src/LimitStream.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/unipayment-gateway-for-woocommerce/index.php:15
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/guzzlehttp/promises/src/Promise.php:10
- > PHP Fatal error
Uncaught Error: Interface 'UniPayment\\Client\\Model\\ModelInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/lib/Model/GetCurrenciesResponse.php:14
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/vendor/guzzlehttp/promises/src/EachPromise.php:9
- > PHP Fatal error
Uncaught Error: Interface 'UniPayment\\Client\\Model\\ModelInterface' not found in wp-content/plugins/unipayment-gateway-for-woocommerce/lib/Model/CreateInvoiceRequest.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
9 plugin tags: payment, usdt, usc, woocommerce, busd...
unipayment-gateway-for-woocommerce/index.php 85% from 13 tests
The principal PHP file in "UniPayment Gateway for WooCommerce" v. 1.0.2 is loaded by WordPress automatically on each request
You should first fix the following items:
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.9" instead of "3.0")
- Main file name: The principal plugin file should be the same as the plugin slug ("unipayment-gateway-for-woocommerce.php" instead of "index.php")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin36,541 lines of code in 183 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 153 | 3,328 | 10,158 | 31,980 |
| Markdown | 14 | 1,149 | 0 | 3,449 |
| JSON | 9 | 0 | 0 | 1,002 |
| YAML | 5 | 22 | 3 | 91 |
| Dockerfile | 1 | 8 | 0 | 10 |
| make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Please tend to the following items
- Method cyclomatic complexity should be reduced to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 17.09 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 212.00 |
| Average method complexity | 2.61 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 15 | |
| Interfaces | 16 | |
| Traits | 2 | |
| Classes | 104 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 104 | 100.00% |
| ▷ Final classes | 23 | 22.12% |
| Methods | 1,237 | |
| ▷ Static methods | 255 | 20.61% |
| ▷ Public methods | 1,086 | 87.79% |
| ▷ Protected methods | 14 | 1.13% |
| ▷ Private methods | 137 | 11.08% |
| Functions | 189 | |
| ▷ Named functions | 76 | 40.21% |
| ▷ Anonymous functions | 113 | 59.79% |
| Constants | 213 | |
| ▷ Global constants | 76 | 35.68% |
| ▷ Class constants | 137 | 64.32% |
| ▷ Public constants | 137 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There are no PNG files in this plugin