Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.13ms] Passed 4 tests
This is a short check of server-side resources used by Up2pay e-Transactions WooCommerce Payment Gateway
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 46.98 ▲3.72 |
Dashboard /wp-admin | 3.31 ▼0.04 | 51.84 ▼14.11 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.25 ▲0.93 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.53 ▼16.97 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.02 ▼2.35 |
Server storage [IO: ▲0.81MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 54 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Up2pay e-Transactions WooCommerce Payment Gateway
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲3 | 14.38 ▼0.20 | 1.72 ▼0.27 | 43.14 ▼1.77 |
Dashboard /wp-admin | 2,198 ▲18 | 5.65 ▼0.22 | 96.79 ▲6.18 | 41.70 ▲1.95 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.00 ▼0.06 | 36.09 ▼0.10 | 34.82 ▼3.82 |
Add New Post /wp-admin/post-new.php | 1,545 ▼1 | 23.09 ▼0.18 | 639.65 ▲22.84 | 54.33 ▲1.64 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.23 ▼0.02 | 97.85 ▼5.16 | 46.01 ▼1.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however 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
The following issues need your attention
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WC_Etransactions_Abstract_Gateway' not found in wp-content/plugins/e-transactions-wc/class/wc-etransactions-threetime-gateway.php:11
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/e-transactions-wc/class/wc-etransactions-abstract-gateway.php:11
- > PHP Fatal error
Uncaught Error: Class 'WC_Etransactions_Abstract_Gateway' not found in wp-content/plugins/e-transactions-wc/class/wc-etransactions-standard-gateway.php:9
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Donate link: Invalid url: "none"
- Screenshots: These screenshots do not have images: #1 (The administration panel: payment configuration), #2 (The administration panel: Up2pay e-Transactions Account parameters), #3 (The Checkout page: Payment method choice (1/ 3 times)), #4 (The Payment Means choice (hosted at Up2pay e-Transactions)), #5 (The Payment page), #6 (Once successfully processed, the Payment transaction details appear in the order details)
e-transactions-wc/wc-etransactions.php 85% from 13 tests
The principal PHP file in "Up2pay e-Transactions WooCommerce Payment Gateway" v. 1.0.9 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("e-transactions-wc.php" instead of "wc-etransactions.php")
Code Analysis Passed 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
Everything looks great! No dangerous files found in this plugin4,129 lines of code in 28 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 482 | 858 | 3,458 |
PO File | 1 | 147 | 223 | 333 |
SVG | 12 | 0 | 0 | 121 |
CSS | 2 | 25 | 3 | 115 |
JavaScript | 2 | 9 | 3 | 102 |
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.37 |
Average class complexity | 38.90 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 197.00 |
Average method complexity | 3.54 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 20.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 1 | 10.00% |
▷ Concrete classes | 9 | 90.00% |
▷ Final classes | 0 | 0.00% |
Methods | 150 | |
▷ Static methods | 4 | 2.67% |
▷ Public methods | 106 | 70.67% |
▷ Protected methods | 34 | 22.67% |
▷ Private methods | 10 | 6.67% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 12 | |
▷ Global constants | 4 | 33.33% |
▷ Class constants | 8 | 66.67% |
▷ Public constants | 8 | 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
22 compressed PNG files occupy 0.05MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
cards/MAESTRO.png | 2.13KB | 1.69KB | ▼ 20.53% |
cards/ILLICADO.png | 1.34KB | 1.40KB | 0.00% |
cards/PSC.png | 0.70KB | 1.28KB | 0.00% |
cards/MASTERPASS.png | 2.60KB | 1.84KB | ▼ 29.22% |
cards/UNEURO.png | 1.05KB | 1.54KB | 0.00% |