Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.01MB] [CPU: ▼13.45ms] Passed 4 tests
A check of server-side resources used by Riverty Payments for Woocommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 37.55 ▼7.39 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 42.97 ▼20.60 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.74 ▲4.51 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.34 ▼25.05 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.88 ▼0.74 |
Server storage [IO: ▲3.78MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 288 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Riverty Payments for Woocommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.66 ▲0.30 | 1.91 ▲0.24 | 36.65 ▼9.41 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.63 ▲0.04 | 89.51 ▼11.98 | 39.95 ▼2.76 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.04 ▲0.02 | 41.86 ▼0.88 | 36.56 ▼1.92 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 22.95 ▼0.05 | 703.82 ▲68.65 | 58.55 ▼4.43 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.26 ▲0.04 | 96.96 ▼11.99 | 42.62 ▲0.14 |
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
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
Please fix the following items
- 108× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp6\\Promise\\PromisorInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor-static/guzzlehttp/guzzle/src/Pool.php:20
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/REST/Advanced/vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/REST/Advanced/installmentplans_submit.php on line 4
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp6\\Promise\\PromiseInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor-static/guzzlehttp/promises/src/FulfilledPromise.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor-static/guzzlehttp/psr7/src/Stream.php:12
- > PHP Warning
require_once(wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/SOAP-NL-BE/Advanced/vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/SOAP-NL-BE/Advanced/b2c.nl.requestorderstatus.php on line 4
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor-static/guzzlehttp/psr7/src/MultipartStream.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/psr/http-message/src/RequestInterface.php:24
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/REST/Simple/vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/REST/Simple/b2c.be.openinvoice.php on line 4
- > PHP Warning
require_once(wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/SOAP-NL-BE/Advanced/vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/payintegrator/afterpay/examples/SOAP-NL-BE/Advanced/b2c.be.push.php on line 4
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/afterpay-payment-gateway-for-woocommerce/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Screenshots: These screenshots lack descriptions #1, #2 in afterpay-payment-gateway-for-woocommerce/assets to your readme.txt
afterpay-payment-gateway-for-woocommerce/class-wc-gateway-afterpay.php 85% from 13 tests
The main PHP file in "Riverty Payments for Woocommerce" ver. 7.1.0 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("afterpay-payment-gateway-for-woocommerce.php" instead of "class-wc-gateway-afterpay.php")
- Description: The description should be shorter than 140 characters (currently 154 characters long)
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected59,711 lines of code in 265 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 219 | 4,413 | 10,166 | 48,778 |
| PO File | 11 | 2,402 | 20,696 | 5,805 |
| Markdown | 14 | 1,221 | 0 | 3,586 |
| JSON | 11 | 0 | 0 | 1,089 |
| CSS | 1 | 34 | 0 | 262 |
| YAML | 5 | 22 | 3 | 91 |
| JavaScript | 2 | 8 | 2 | 81 |
| Dockerfile | 1 | 8 | 0 | 10 |
| make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
An overview of cyclomatic complexity and code structure
The following items need your attention
- Method cyclomatic complexity has to be reduced to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 27.91 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 234.00 |
| Average method complexity | 5.41 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 14 | |
| Interfaces | 15 | |
| Traits | 2 | |
| Classes | 128 | |
| ▷ Abstract classes | 1 | 0.78% |
| ▷ Concrete classes | 127 | 99.22% |
| ▷ Final classes | 23 | 18.11% |
| Methods | 995 | |
| ▷ Static methods | 159 | 15.98% |
| ▷ Public methods | 837 | 84.12% |
| ▷ Protected methods | 15 | 1.51% |
| ▷ Private methods | 143 | 14.37% |
| Functions | 191 | |
| ▷ Named functions | 100 | 52.36% |
| ▷ Anonymous functions | 91 | 47.64% |
| Constants | 199 | |
| ▷ Global constants | 78 | 39.20% |
| ▷ Class constants | 121 | 60.80% |
| ▷ Public constants | 121 | 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