Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.53ms] Passed 4 tests
Server-side resources used by KuPay Payment Gateway for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 35.44 ▼7.16 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 44.12 ▼5.48 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.92 ▼1.87 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.34 ▼19.60 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.00 ▲0.45 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by KuPay Payment Gateway for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.37 ▼0.29 | 1.68 ▲0.06 | 38.98 ▼2.48 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.55 ▼0.11 | 104.94 ▲16.30 | 43.11 ▲3.54 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 1.96 ▼0.00 | 39.30 ▲3.52 | 34.83 ▼0.41 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼10 | 23.21 ▼0.04 | 608.12 ▼86.49 | 46.34 ▼9.65 |
| Media Library /wp-admin/upload.php | 1,394 ▼3 | 4.22 ▼0.01 | 100.64 ▼13.30 | 45.65 ▼2.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/kupay-payment-gateway-for-woocommerce/includes/kupay-checkout-description-fields.php:3
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/kupay-payment-gateway-for-woocommerce/includes/class-wc-payment-gateway-kupay.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
8 plugin tags: defi, woocommerce, metamask, kcc, gateway...
kupay-payment-gateway-for-woocommerce/kupay-payment-gateway.php 85% from 13 tests
The principal PHP file in "KuPay Payment Gateway for WooCommerce" v. 0.1.3 is loaded by WordPress automatically on each request
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.7" instead of "6.3.0")
- Main file name: Name the main plugin file the same as the plugin slug ("kupay-payment-gateway-for-woocommerce.php" instead of "kupay-payment-gateway.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected366 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 110 | 165 | 366 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.56 |
| Average class complexity | 67.00 |
| ▷ Minimum class complexity | 67.00 |
| ▷ Maximum class complexity | 67.00 |
| Average method complexity | 5.12 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 8 | 50.00% |
| ▷ Protected methods | 1 | 6.25% |
| ▷ Private methods | 7 | 43.75% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon.png | 3.72KB | 3.23KB | ▼ 13.20% |