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.42MB] [CPU: ▼5.32ms] Passed 4 tests
An overview of server-side resources used by WooCommerce PensoPay
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.95 ▲0.44 | 48.73 ▲9.13 |
Dashboard /wp-admin | 3.78 ▲0.44 | 57.36 ▲7.86 |
Posts /wp-admin/edit.php | 3.83 ▲0.44 | 52.17 ▼3.05 |
Add New Post /wp-admin/post-new.php | 6.35 ▲0.43 | 86.52 ▼29.45 |
Media Library /wp-admin/upload.php | 3.64 ▲0.37 | 41.25 ▲3.38 |
PensoPay - Virtual Terminal /wp-admin/edit.php?post_type=vterminal_payment | 3.75 | 53.73 |
Server storage [IO: ▲1.65MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 158 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WooCommerce PensoPay
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲39 | 14.44 ▲0.01 | 1.83 ▲0.21 | 45.83 ▲0.02 |
Dashboard /wp-admin | 2,206 ▲39 | 5.61 ▲0.01 | 92.87 ▼12.53 | 44.94 ▲4.95 |
Posts /wp-admin/edit.php | 2,108 ▲8 | 2.13 ▲0.16 | 38.71 ▼3.29 | 34.90 ▼3.41 |
Add New Post /wp-admin/post-new.php | 1,539 ▲13 | 23.35 ▲0.32 | 634.55 ▼77.69 | 51.98 ▼4.36 |
Media Library /wp-admin/upload.php | 1,408 ▲8 | 4.23 ▲0.04 | 97.98 ▼6.78 | 47.16 ▲2.80 |
PensoPay - Virtual Terminal /wp-admin/edit.php?post_type=vterminal_payment | 1,083 | 1.94 | 38.63 | 37.93 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
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 take a closer look at the following
- 41× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function get_template_part() in wp-content/plugins/woo-pensopay/templates/checkout/iframe.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr_e() in wp-content/plugins/woo-pensopay/views/checkout/payment-overlay.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function get_user_meta() in wp-content/plugins/woo-pensopay/templates/admin/virtualterminal/grid-notices.php:2
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_Instance' not found in wp-content/plugins/woo-pensopay/classes/instances/resurs.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/woo-pensopay/extensions/polylang.php:19
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_Instance' not found in wp-content/plugins/woo-pensopay/classes/instances/klarna.php:3
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_Instance' not found in wp-content/plugins/woo-pensopay/classes/instances/ideal.php:3
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_Instance' not found in wp-content/plugins/woo-pensopay/classes/instances/pensopay-extra.php:9
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_VirtualTerminal_Payment' not found in wp-content/plugins/woo-pensopay/templates/admin/virtualterminal/payment.php:2
- > PHP Fatal error
Uncaught Error: Class 'WC_PensoPay_Instance' not found in wp-content/plugins/woo-pensopay/classes/instances/paypal.php:3
- > 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)
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
9 plugin tags: woocommerce pensopay, woo commerce, woocommerce, pensopay, payment...
woo-pensopay/woocommerce-pensopay.php 85% from 13 tests
"WooCommerce PensoPay" version 6.3.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-pensopay.php" instead of "woocommerce-pensopay.php")
- Requires at least: The required version number must match the one declared in readme.txt ("4.0.0" instead of "3.0.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected16,521 lines of code in 113 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 67 | 1,557 | 3,099 | 6,561 |
JavaScript | 8 | 438 | 524 | 3,723 |
PO File | 4 | 1,274 | 1,903 | 3,021 |
SVG | 30 | 9 | 25 | 2,924 |
CSS | 3 | 51 | 3 | 281 |
XML | 1 | 0 | 0 | 11 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 16.90 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 214.00 |
Average method complexity | 2.74 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 25.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 48 | |
▷ Abstract classes | 1 | 2.08% |
▷ Concrete classes | 47 | 97.92% |
▷ Final classes | 0 | 0.00% |
Methods | 413 | |
▷ Static methods | 95 | 23.00% |
▷ Public methods | 387 | 93.70% |
▷ Protected methods | 8 | 1.94% |
▷ Private methods | 18 | 4.36% |
Functions | 39 | |
▷ Named functions | 25 | 64.10% |
▷ Anonymous functions | 14 | 35.90% |
Constants | 37 | |
▷ Global constants | 3 | 8.11% |
▷ Class constants | 34 | 91.89% |
▷ Public constants | 34 | 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
33 PNG files occupy 0.22MB with 0.15MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/mobilepay-checkout/white/small@1x.png | 4.93KB | 1.44KB | ▼ 70.77% |
assets/images/mobilepay-checkout/darkblue/medium@2x.png | 10.23KB | 3.24KB | ▼ 68.35% |
assets/images/mobilepay-checkout/white/medium@2x.png | 8.91KB | 3.16KB | ▼ 64.58% |
assets/images/mobilepay-checkout/mpblue/small@1x.png | 5.29KB | 1.65KB | ▼ 68.72% |
assets/images/mobilepay-checkout/whitestroke/medium@2x.png | 9.02KB | 3.22KB | ▼ 64.26% |