Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.25MB] [CPU: ▼2.32ms] Passed 4 tests
Analyzing server-side resources used by OnPay.io for WooCommerce
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.71 ▲0.25 | 46.09 ▲1.58 |
Dashboard /wp-admin | 3.55 ▲0.25 | 51.72 ▼9.70 |
Posts /wp-admin/edit.php | 3.67 ▲0.31 | 55.01 ▲7.27 |
Add New Post /wp-admin/post-new.php | 6.13 ▲0.25 | 102.39 ▼3.38 |
Media Library /wp-admin/upload.php | 3.47 ▲0.25 | 38.06 ▲2.21 |
Server storage [IO: ▲0.83MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 249 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for OnPay.io for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.45 ▲0.09 | 1.74 ▲0.12 | 45.20 ▲9.03 |
Dashboard /wp-admin | 2,195 ▲18 | 5.60 ▼0.02 | 90.59 ▼11.34 | 42.60 ▼2.13 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▲0.04 | 42.34 ▲2.39 | 35.23 ▼1.16 |
Add New Post /wp-admin/post-new.php | 1,525 ▼1 | 22.88 ▼0.03 | 618.50 ▼67.46 | 57.43 ▼5.85 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.22 ▲0.00 | 96.79 ▼19.66 | 46.90 ▼4.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- 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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 89× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\Psr\\Log\\AbstractLogger' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/oauth2-client/src/ErrorLogger.php:30
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/onpay-io-for-woocommerce/classes/abstract-gateway.php:26
- > PHP Fatal error
Uncaught Error: Interface 'WoocommerceOnpay\\Psr\\Log\\LoggerInterface' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/psr/log/Psr/Log/AbstractLogger.php:12
- > PHP Fatal error
Uncaught Error: Interface 'WoocommerceOnpay\\fkooman\\OAuth\\Client\\TokenStorageInterface' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/oauth2-client/src/PdoTokenStorage.php:27
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/oauth2-client/tests/Http/RequestTest.php:28
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\fkooman\\OAuth\\Client\\Exception\\OAuthException' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/oauth2-client/src/Exception/AccessTokenException.php:26
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\OnPay\\API\\Util\\PaymentMethods\\Methods\\PaymentMethodAbstract' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/php-sdk/src/API/Util/PaymentMethods/Methods/Vipps.php:10
- > PHP Warning
require_once(wp-content/plugins/onpay-io-for-woocommerce/build/vendor/paragonie/constant_time_encoding/tests/../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/paragonie/constant_time_encoding/tests/autoload.php on line 5
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\fkooman\\OAuth\\Client\\Exception\\OAuthException' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/oauth2-client/src/Exception/SessionException.php:26
- > PHP Fatal error
Uncaught Error: Class 'WoocommerceOnpay\\OnPay\\API\\Transaction\\SimpleTransaction' not found in wp-content/plugins/onpay-io-for-woocommerce/build/vendor/onpayio/php-sdk/src/API/Transaction/DetailedTransaction.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Screenshots: No descriptions were found for these screenshots #1, #2 in onpay-io-for-woocommerce/assets to your readme.txt
onpay-io-for-woocommerce/woocommerce-onpay.php 85% from 13 tests
"OnPay.io for WooCommerce" version 1.0.36's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("onpay-io-for-woocommerce.php" instead of "woocommerce-onpay.php")
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
There were no executable files found in this plugin12,766 lines of code in 234 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 185 | 783 | 6,398 | 8,753 |
SVG | 19 | 15 | 13 | 2,007 |
JSON | 10 | 0 | 0 | 819 |
Markdown | 11 | 226 | 0 | 661 |
PO File | 1 | 129 | 135 | 303 |
XML | 5 | 6 | 0 | 97 |
JavaScript | 2 | 13 | 15 | 89 |
CSS | 1 | 7 | 31 | 37 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 5.81 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 124.00 |
Average method complexity | 2.20 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 31.00 |
Code structure | ||
---|---|---|
Namespaces | 29 | |
Interfaces | 9 | |
Traits | 2 | |
Classes | 155 | |
▷ Abstract classes | 15 | 9.68% |
▷ Concrete classes | 140 | 90.32% |
▷ Final classes | 14 | 10.00% |
Methods | 694 | |
▷ Static methods | 115 | 16.57% |
▷ Public methods | 592 | 85.30% |
▷ Protected methods | 32 | 4.61% |
▷ Private methods | 70 | 10.09% |
Functions | 39 | |
▷ Named functions | 30 | 76.92% |
▷ Anonymous functions | 9 | 23.08% |
Constants | 134 | |
▷ Global constants | 8 | 5.97% |
▷ Class constants | 126 | 94.03% |
▷ Public constants | 126 | 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
No PNG files were detected