Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.43MB] [CPU: ▼180.95ms] Passed 4 tests
This is a short check of server-side resources used by Payvision Payment Gateway
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.26 ▲0.42 | 30.18 ▲6.57 |
Dashboard /wp-admin | 3.54 ▲0.48 | 34.87 ▼6.89 |
Posts /wp-admin/edit.php | 3.59 ▲0.48 | 34.58 ▼6.98 |
Add New Post /wp-admin/post-new.php | 5.84 ▲0.40 | 74.42 ▼712.22 |
Media Library /wp-admin/upload.php | 3.43 ▲0.42 | 27.54 ▲2.28 |
Server storage [IO: ▲4.78MB] [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: 805 new files
Database: 1 new table, 1 new option
New tables |
---|
wp_payvision_webhook |
New WordPress options |
---|
payvision_db_version |
Browser metrics Passed 4 tests
An overview of browser requirements for Payvision Payment Gateway
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,666 ▲65 | 16.04 ▲0.22 | 5.11 ▼0.71 | 76.07 ▲1.83 |
Dashboard /wp-admin | 2,929 ▲33 | 6.13 ▲0.04 | 113.63 ▼16.91 | 174.16 ▲3.00 |
Posts /wp-admin/edit.php | 2,740 ▼0 | 3.23 ▼0.00 | 60.50 ▼2.54 | 132.37 ▼3.69 |
Add New Post /wp-admin/post-new.php | 3,815 ▲8 | 19.44 ▲0.53 | 436.03 ▼20.32 | 164.36 ▲5.17 |
Media Library /wp-admin/upload.php | 1,752 ▼0 | 5.51 ▼0.04 | 138.68 ▼0.62 | 191.87 ▲10.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie tables were found after uninstall: 1 table
- wp_payvision_webhook
- This plugin does not fully uninstall, leaving 1 option in the database
- payvision_db_version
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: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 441× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Payvision\\WooCommerce\\Handler\\ResultHandlerInterface' not found in wp-content/plugins/payvision-payment-gateway/payvision/src/Handler/Result/AbstractFailed.php:19
- > PHP Fatal error
Uncaught Error: Class 'Payvision_Vendor\\Payvision\\SDK\\Domain\\Service\\Builder\\Basic' not found in wp-content/plugins/payvision-payment-gateway/payvision/vendor_prefixed/payvision/src/Domain/Paymentlinks/Service/Builder/Link/Response.php:16
- > PHP Fatal error
Uncaught Error: Interface 'Payvision_Vendor\\GuzzleHttp\\Cookie\\CookieJarInterface' not found in wp-content/plugins/payvision-payment-gateway/payvision/vendor_prefixed/guzzlehttp/guzzle/src/Cookie/CookieJar.php:10
- > PHP Fatal error
Uncaught Error: Class 'Payvision_Vendor\\Payvision\\SDK\\Domain\\Service\\Builder\\Basic' not found in wp-content/plugins/payvision-payment-gateway/payvision/vendor_prefixed/payvision/src/Domain/Checkouts/Service/Builder/Checkout/ResponseHeader.php:14
- > PHP Fatal error
Uncaught Error: Class 'Payvision\\WooCommerce\\Handler\\Result\\Refund\\AbstractRefund' not found in wp-content/plugins/payvision-payment-gateway/payvision/src/Handler/Result/Refund/Timeout.php:16
- > PHP Fatal error
Uncaught Error: Class 'Payvision\\WooCommerce\\Gateway\\AbstractReceiptPagePaymentGateway' not found in wp-content/plugins/payvision-payment-gateway/payvision/src/Gateway/Cards.php:28
- > PHP Fatal error
Uncaught Error: Class 'Payvision\\WooCommerce\\Handler\\Result\\AbstractFailed' not found in wp-content/plugins/payvision-payment-gateway/payvision/src/Handler/Result/Payment/Timeout.php:17
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/payvision-payment-gateway/payvision/src/PaymentGateway.php:58
- > PHP Fatal error
Uncaught Error: Class 'Payvision_Vendor\\Payvision\\SDK\\Domain\\Service\\Builder\\Basic' not found in wp-content/plugins/payvision-payment-gateway/payvision/vendor_prefixed/payvision/src/Domain/Checkouts/Service/Builder/Request/Header.php:14
- > PHP Fatal error
Uncaught Error: Class 'Payvision_Vendor\\Payvision\\SDK\\Domain\\Service\\Builder\\Basic' not found in wp-content/plugins/payvision-payment-gateway/payvision/vendor_prefixed/payvision/src/Domain/Payments/Service/Builder/Payment/Request.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
8 plugin tags: psp, paypal, woocommerce, bancontact, payment...
payvision-payment-gateway/payvision-payment-gateway.php 85% from 13 tests
The primary PHP file in "Payvision Payment Gateway" version 2.7.0 is used by WordPress to initiate all plugin 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
- Requires at least: The required version number must match the one declared in readme.txt ("5.2" instead of "3.6.2")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin57,887 lines of code in 775 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 740 | 3,195 | 26,187 | 54,330 |
PO File | 4 | 780 | 1,220 | 1,624 |
JSON | 16 | 0 | 0 | 1,493 |
XML | 3 | 8 | 17 | 257 |
Markdown | 1 | 43 | 0 | 78 |
XSD | 1 | 0 | 4 | 48 |
SVG | 7 | 0 | 0 | 35 |
CSS | 2 | 2 | 0 | 21 |
JavaScript | 1 | 0 | 0 | 1 |
PHP code 50% from 2 tests
Analyzing cyclomatic complexity and code structure
It is recommended to fix the following
- Method cyclomatic complexity has to be reduced to less than 100 (currently 179)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.31 |
Average class complexity | 6.10 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 179.00 |
Average method complexity | 1.92 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 179.00 |
Code structure | ||
---|---|---|
Namespaces | 103 | |
Interfaces | 35 | |
Traits | 7 | |
Classes | 665 | |
▷ Abstract classes | 24 | 3.61% |
▷ Concrete classes | 641 | 96.39% |
▷ Final classes | 23 | 3.59% |
Methods | 3,859 | |
▷ Static methods | 278 | 7.20% |
▷ Public methods | 3,232 | 83.75% |
▷ Protected methods | 386 | 10.00% |
▷ Private methods | 241 | 6.25% |
Functions | 184 | |
▷ Named functions | 74 | 40.22% |
▷ Anonymous functions | 110 | 59.78% |
Constants | 1,175 | |
▷ Global constants | 45 | 3.83% |
▷ Class constants | 1,130 | 96.17% |
▷ Public constants | 1,129 | 99.91% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
7 compressed PNG files occupy 0.01MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
payvision/assets/images/payvision_eps.png | 1.08KB | 1.07KB | ▼ 1.62% |
payvision/assets/images/payvision_sofort.png | 0.83KB | 0.70KB | ▼ 15.11% |
payvision/assets/images/payvision_paypal.png | 1.74KB | 1.65KB | ▼ 5.18% |
payvision/assets/images/payvision_afterpay.png | 2.56KB | 1.95KB | ▼ 23.81% |
payvision/assets/images/payvision_ideal.png | 1.03KB | 0.95KB | ▼ 7.57% |