Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼9.22ms] Passed 4 tests
This is a short check of server-side resources used by Visma Pay for Woocommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 36.58 ▼4.07 |
Dashboard /wp-admin | 3.31 ▼0.03 | 45.51 ▼16.01 |
Posts /wp-admin/edit.php | 3.43 ▲0.07 | 47.36 ▼0.53 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 80.30 ▼16.27 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.45 ▲5.55 |
Server storage [IO: ▲0.28MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 45 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Visma Pay for Woocommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.34 ▼0.97 | 1.82 ▲0.06 | 38.99 ▼4.52 |
Dashboard /wp-admin | 2,209 ▲21 | 4.87 ▼1.03 | 100.71 ▼12.12 | 37.52 ▼9.01 |
Posts /wp-admin/edit.php | 2,089 ▲21 | 1.99 ▼0.02 | 41.60 ▲3.41 | 35.82 ▼2.51 |
Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.44 ▲5.78 | 681.34 ▼11.68 | 55.79 ▲1.53 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.28 ▲0.09 | 95.33 ▼8.13 | 39.52 ▼5.78 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
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 everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'Automattic\\WooCommerce\\Blocks\\Payments\\Integrations\\AbstractPaymentMethodType' not found in wp-content/plugins/visma-pay-payment-gateway/includes/blocks/visma_pay_blocks_support.php:5
- > PHP Fatal error
Uncaught Error: Interface 'Visma\\VismaPayConnector' not found in wp-content/plugins/visma-pay-payment-gateway/includes/lib/Visma/VismaPayWPConnector.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Donate link: Invalid url: ""
visma-pay-payment-gateway/visma-pay-payment-gateway.php 92% from 13 tests
The primary PHP file in "Visma Pay for Woocommerce" version 1.1.2 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Requires at least: Required version must match the one declared in readme.txt ("3.3" instead of "3.0.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected1,650 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 198 | 29 | 1,261 |
PO File | 1 | 96 | 98 | 286 |
CSS | 1 | 7 | 1 | 72 |
JavaScript | 2 | 2 | 0 | 21 |
XML | 1 | 0 | 0 | 9 |
JSON | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.43 |
Average class complexity | 34.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 180.00 |
Average method complexity | 5.55 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 57.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 1 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 1 | 20.00% |
Methods | 45 | |
▷ Static methods | 2 | 4.44% |
▷ Public methods | 41 | 91.11% |
▷ Protected methods | 4 | 8.89% |
▷ Private methods | 0 | 0.00% |
Functions | 5 | |
▷ Named functions | 3 | 60.00% |
▷ Anonymous functions | 2 | 40.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 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
28 PNG files occupy 0.19MB with 0.11MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/handelsbanken.png | 3.47KB | 1.72KB | ▼ 50.39% |
assets/images/spankki.png | 12.20KB | 1.84KB | ▼ 84.92% |
assets/images/fellowfinance_big.png | 14.81KB | 6.39KB | ▼ 56.85% |
assets/images/joustoraha.png | 4.36KB | 2.18KB | ▼ 50.06% |
assets/images/fellowfinance.png | 3.22KB | 1.74KB | ▼ 45.78% |