Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼0.13ms] Passed 4 tests
Server-side resources used by WooCommerce 3D Secure (Bankart) Payment Gateway
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.11 | 35.84 ▼0.23 |
| Dashboard /wp-admin | 3.42 ▲0.11 | 44.35 ▲1.08 |
| Posts /wp-admin/edit.php | 3.53 ▲0.17 | 47.39 ▼1.66 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 92.07 ▲0.31 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.11 | 39.60 ▲6.12 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WooCommerce 3D Secure (Bankart) Payment Gateway
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲53 | 14.38 ▼0.19 | 1.80 ▲0.01 | 36.00 ▼5.23 |
| Dashboard /wp-admin | 2,195 ▲14 | 5.57 ▼0.11 | 93.20 ▼18.76 | 42.60 ▼6.65 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.06 | 38.83 ▼1.86 | 35.94 ▲0.75 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.00 ▼0.04 | 657.14 ▼0.98 | 60.69 ▲2.29 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▲0.05 | 94.54 ▼3.25 | 46.12 ▲4.29 |
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 does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
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)
Good news, no errors were detected
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/woo-3d-secure-bankart-payment-gateway/index.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 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
8 plugin tags: bankart, mastercard, woocommerce, visa, gateway...
woo-3d-secure-bankart-payment-gateway/index.php 85% from 13 tests
The main file in "WooCommerce 3D Secure (Bankart) Payment Gateway" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-3d-secure-bankart-payment-gateway.php" instead of "index.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected579 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 108 | 31 | 579 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 10.75 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 19.00 |
| Average method complexity | 2.39 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 24 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 21 | 87.50% |
| ▷ Protected methods | 1 | 4.17% |
| ▷ Private methods | 2 | 8.33% |
| Functions | 3 | |
| ▷ Named functions | 2 | 66.67% |
| ▷ Anonymous functions | 1 | 33.33% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/mc.png | 5.42KB | 1.77KB | ▼ 67.41% |