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
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.19ms] Passed 4 tests
This is a short check of server-side resources used by Payment Gateway for Alipay and WeChat Pay (支付宝，微信支付，银联支付北美版)
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 48.25 ▲1.97 |
| Dashboard /wp-admin | 3.32 ▼0.02 | 51.11 ▼17.96 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 50.57 ▼4.11 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 101.96 ▼9.68 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 37.44 ▼1.00 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Payment Gateway for Alipay and WeChat Pay (支付宝，微信支付，银联支付北美版)
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,909 ▲163 | 13.96 ▼0.38 | 10.41 ▲8.68 | 40.60 ▼4.67 |
| Dashboard /wp-admin | 2,193 ▲13 | 5.57 ▼0.05 | 89.59 ▼1.73 | 43.12 ▼0.01 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 1.94 ▼0.06 | 34.14 ▼4.05 | 41.96 ▲4.17 |
| Add New Post /wp-admin/post-new.php | 1,528 ▼3 | 21.64 ▼1.49 | 752.37 ▲116.84 | 57.38 ▲8.14 |
| Media Library /wp-admin/upload.php | 1,395 ▼8 | 4.14 ▼0.06 | 103.64 ▲0.56 | 45.29 ▲2.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- 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
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
Please fix the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/snappay-alipay-wechat-payment-gateway/snappaynotifyresponse.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 86% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
8 plugin tags: alipay, payment gateway, woocommerce, cad, usd...
snappay-alipay-wechat-payment-gateway/snappaymain.php 69% from 13 tests
"Payment Gateway for Alipay and WeChat Pay (支付宝，微信支付，银联支付北美版)" version 2.3.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("snappay-alipay-wechat-payment-gateway.php" instead of "snappaymain.php")
- Plugin Name: It is recommended to keep the plugin name shorter than 70 characters (currently 100 characters long)
- Description: The description should be shorter than 140 characters (currently 191 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin659 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 112 | 34 | 629 |
| JavaScript | 3 | 0 | 2 | 30 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 52.00 |
| ▷ Minimum class complexity | 52.00 |
| ▷ Maximum class complexity | 52.00 |
| Average method complexity | 3.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.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 | 18 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 18 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 15 | |
| ▷ Named functions | 15 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.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
6 PNG files occupy 0.06MB with 0.03MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/wechat_webscan01.png | 1.67KB | 1.09KB | ▼ 34.95% |
| images/wechat_webscan02.png | 32.63KB | 13.58KB | ▼ 58.40% |
| images/Alipay_logo.png | 8.37KB | 3.39KB | ▼ 59.45% |
| images/Wechat_logo.png | 9.22KB | 3.83KB | ▼ 58.45% |
| images/unionpay_logo.png | 5.00KB | 2.59KB | ▼ 48.13% |