Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼6.67ms] Passed 4 tests
A check of server-side resources used by ScanForPay - Alipay & AlipayHK & WechatPay Payment Solutions for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 45.60 ▲3.98 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 50.37 ▼3.68 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.77 ▼6.50 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.12 ▼16.77 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.08 ▲0.27 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 13 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for ScanForPay - Alipay & AlipayHK & WechatPay Payment Solutions for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.27 ▼0.10 | 1.68 ▼0.13 | 43.63 ▼2.02 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.59 ▼0.07 | 84.48 ▼7.50 | 41.06 ▼1.82 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 1.98 ▼0.16 | 35.69 ▼1.80 | 36.33 ▼0.24 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.16 ▲0.16 | 681.25 ▼29.98 | 53.35 ▼2.38 |
| Media Library /wp-admin/upload.php | 1,403 ▼0 | 4.25 ▲0.05 | 99.79 ▼18.87 | 45.99 ▼2.75 |
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
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% 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
6 plugin tags: alipayhk, payment, alipay, wechatpay, scanforpay...
scanforpay-alipay-alipayhk-for-woocommerce/scanforpay-alipay-for-woocommerce.php 77% from 13 tests
"ScanForPay - Alipay & AlipayHK & WechatPay Payment Solutions for WooCommerce" version 1.1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 202 characters long)
- Plugin Name: Keep the plugin name shorter than 70 characters (currently 88 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("scanforpay-alipay-alipayhk-for-woocommerce.php" instead of "scanforpay-alipay-for-woocommerce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin908 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 149 | 177 | 817 |
| SVG | 3 | 0 | 3 | 91 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 28.25 |
| ▷ Minimum class complexity | 21.00 |
| ▷ Maximum class complexity | 32.00 |
| Average method complexity | 3.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.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 | 45 | |
| ▷ Static methods | 24 | 53.33% |
| ▷ Public methods | 44 | 97.78% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 2.22% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.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.04MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/white_logo.png | 41.19KB | 21.84KB | ▼ 46.98% |