Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.15MB] [CPU: ▼9.61ms] Passed 4 tests
An overview of server-side resources used by Payment Gateway PayPay for WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.18 ▼0.28 | 22.48 ▼22.71 |
Dashboard /wp-admin | 3.64 ▲0.34 | 52.79 ▲0.23 |
Posts /wp-admin/edit.php | 3.69 ▲0.34 | 54.49 ▲0.04 |
Add New Post /wp-admin/post-new.php | 6.16 ▲0.27 | 94.87 ▼16.01 |
Media Library /wp-admin/upload.php | 3.50 ▲0.27 | 42.18 ▲4.78 |
Server storage [IO: ▲1.60MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 243 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Payment Gateway PayPay for WooCommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,464 ▼293 | 13.33 ▼1.07 | 0.49 ▼1.75 | 20.91 ▼25.87 |
Dashboard /wp-admin | 2,214 ▲26 | 4.87 ▼1.01 | 109.64 ▲0.49 | 41.08 ▼6.15 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.04 ▼0.10 | 41.52 ▼1.04 | 32.42 ▼0.73 |
Add New Post /wp-admin/post-new.php | 1,545 ▲9 | 23.41 ▼0.18 | 632.40 ▼19.63 | 60.67 ▼2.86 |
Media Library /wp-admin/upload.php | 1,390 ▲2 | 4.21 ▼0.10 | 110.23 ▼7.30 | 46.42 ▼1.66 |
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
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking 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
- 74× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/guzzle/src/Pool.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/psr7/src/AppendStream.php:14
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/guzzle/src/Exception/TooManyRedirectsException.php:4
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/psr7/src/DroppingStream.php:13
- > PHP Fatal error
Uncaught Error: Class 'PayPay\\OpenPaymentAPI\\Models\\Model' not found in wp-content/plugins/wc-paypay-gateway/vendor/paypayopa/php-sdk/src/Models/ReverseCashBackPayload.php:7
- > PHP Fatal error
Uncaught Error: Class 'PayPay\\OpenPaymentAPI\\Models\\Model' not found in wp-content/plugins/wc-paypay-gateway/vendor/paypayopa/php-sdk/src/Models/RefundPaymentPayload.php:7
- > PHP Fatal error
Uncaught Error: Class 'PayPay\\OpenPaymentAPI\\Models\\Model' not found in wp-content/plugins/wc-paypay-gateway/vendor/paypayopa/php-sdk/src/Models/CapturePaymentAuthPayload.php:7
- > PHP Fatal error
Uncaught UnexpectedValueException: creating archive "wp-content/plugins/wc-paypay-gateway/vendor/paragonie/random_compat/dist/random_compat.phar" disabled by the php.ini setting phar.readonly in /var/www/wordpress/wp-content/plugins/wc-paypay-gateway/vendor/paragonie/random_compat/other/build_phar.php:12
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\TransferException' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:12
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/wc-paypay-gateway/vendor/guzzlehttp/guzzle/src/Cookie/FileCookieJar.php:7
- > 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 86% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Screenshots: Please add images for these screenshots: #1 (PayPay - Settings), #2 (PayPay - Payment Screen)
wc-paypay-gateway/wc-paypay-gateway.php 77% from 13 tests
The main PHP file in "Payment Gateway PayPay for WooCommerce" ver. 0.7 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Domain Path: Prefix the domain path with a forward slash character ("//")
- Requires at least: Required version must be the same as the one declared in readme.txt ("5.0" instead of "4.4")
- Domain Path: You should use only dashes and lowercase characters for the domain path ("/")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin35,754 lines of code in 218 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 180 | 2,811 | 7,661 | 30,037 |
Markdown | 18 | 1,305 | 0 | 4,013 |
JSON | 14 | 0 | 0 | 1,452 |
PO File | 1 | 1,529 | 3,270 | 196 |
XML | 2 | 0 | 0 | 34 |
Dockerfile | 1 | 8 | 0 | 10 |
make | 1 | 4 | 0 | 9 |
Bourne Shell | 1 | 2 | 0 | 3 |
PHP code 50% from 2 tests
A short review of cyclomatic complexity and code structure
Please fix the following
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 179)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 14.20 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 179.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 179.00 |
Code structure | ||
---|---|---|
Namespaces | 19 | |
Interfaces | 16 | |
Traits | 2 | |
Classes | 121 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 121 | 100.00% |
▷ Final classes | 24 | 19.83% |
Methods | 953 | |
▷ Static methods | 177 | 18.57% |
▷ Public methods | 796 | 83.53% |
▷ Protected methods | 10 | 1.05% |
▷ Private methods | 147 | 15.42% |
Functions | 171 | |
▷ Named functions | 80 | 46.78% |
▷ Anonymous functions | 91 | 53.22% |
Constants | 163 | |
▷ Global constants | 42 | 25.77% |
▷ Class constants | 121 | 74.23% |
▷ Public constants | 121 | 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
3 PNG files occupy 0.09MB with 0.04MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
paypay.png | 3.51KB | 1.90KB | ▼ 45.80% |
screenshot-2.png | 52.71KB | 30.73KB | ▼ 41.70% |
screenshot-1.png | 32.09KB | 13.65KB | ▼ 57.45% |