Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.97ms] Passed 4 tests
An overview of server-side resources used by RedPay Payment Gateway
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 36.66 ▼3.54 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 43.42 ▲0.13 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.92 ▼2.22 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.96 ▼10.25 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.87 ▲0.84 |
Server storage [IO: ▲0.72MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for RedPay Payment Gateway
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.21 ▼1.16 | 1.64 ▼0.33 | 36.48 ▼13.21 |
| Dashboard /wp-admin | 2,206 ▲21 | 4.85 ▼1.05 | 110.13 ▼2.65 | 38.93 ▼9.24 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.00 ▼0.06 | 40.14 ▼1.89 | 35.44 ▼0.53 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼0 | 17.73 ▲0.28 | 664.40 ▲15.85 | 58.87 ▲9.61 |
| Media Library /wp-admin/upload.php | 1,391 ▲9 | 4.18 ▼0.08 | 92.09 ▼7.81 | 43.05 ▼1.52 |
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 were found after uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/redpay-payment-gateway/payment_success.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function wc_get_logger() in wp-content/plugins/redpay-payment-gateway/ape_payment.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
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
4 plugin tags: woocommerce, payment request, redpay, credit card
redpay-payment-gateway/redpay.php 85% from 13 tests
The main PHP script in "RedPay Payment Gateway" version 1.2 is automatically included on every request by WordPress
The following require your attention:
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.4" instead of "5.0")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("redpay-payment-gateway.php" instead of "redpay.php")
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 detected4,119 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 901 | 667 | 3,373 |
| PHP | 3 | 131 | 102 | 730 |
| HTML | 1 | 2 | 0 | 16 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 55.00 |
| ▷ Minimum class complexity | 55.00 |
| ▷ Maximum class complexity | 55.00 |
| Average method complexity | 5.91 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 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 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
6 PNG files occupy 0.51MB with 0.32MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| amex.png | 317.22KB | 145.18KB | ▼ 54.24% |
| visa-and-mastercard-logo.png | 76.00KB | 21.72KB | ▼ 71.41% |
| redpay_1.png | 8.26KB | 3.21KB | ▼ 61.15% |
| redpay_logo_netpay.png | 16.56KB | 7.08KB | ▼ 57.23% |
| red-pay-logo.png | 60.74KB | 17.66KB | ▼ 70.92% |