Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼4.99ms] Passed 4 tests
A check of server-side resources used by Latipay WooCommerce Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 43.92 ▲2.98 |
| Dashboard /wp-admin | 3.36 ▲0.01 | 54.95 ▼8.31 |
| Posts /wp-admin/edit.php | 3.41 ▲0.05 | 49.32 ▼7.58 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 90.56 ▼2.35 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 32.61 ▼1.73 |
| Latipay /wp-admin/options-general.php?page=xh_latipay | 3.23 | 31.77 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 26 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Latipay WooCommerce Payment Gateway: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.33 ▲0.36 | 1.95 ▲0.33 | 44.27 ▲2.35 |
| Dashboard /wp-admin | 2,202 ▲28 | 5.63 ▼0.03 | 85.22 ▼11.12 | 44.27 ▲6.15 |
| Posts /wp-admin/edit.php | 2,104 ▲1 | 2.00 ▼0.02 | 33.75 ▼8.21 | 38.30 ▲1.90 |
| Add New Post /wp-admin/post-new.php | 1,529 ▲3 | 23.28 ▼0.48 | 678.35 ▲60.98 | 49.72 ▲0.08 |
| Media Library /wp-admin/upload.php | 1,401 ▲4 | 4.22 ▲0.01 | 99.61 ▼6.48 | 46.28 ▲2.68 |
| Latipay /wp-admin/options-general.php?page=xh_latipay | 921 | 1.97 | 22.15 | 29.68 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=xh_latipay
- > Notice in wp-content/plugins/latipay-for-woo/init.php+116
Undefined variable: response
- > GET request to /wp-admin/options-general.php?page=xh_latipay
- > Notice in wp-content/plugins/latipay-for-woo/init.php+116
Trying to access array offset on value of type null
SRP Passed 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
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
10 plugin tags: moneymore, wechatpay, payid, latipay, card payments...
latipay-for-woo/init.php 92% from 13 tests
This is the main PHP file of "Latipay WooCommerce Payment Gateway" version 3.2.6, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("latipay-for-woo.php" instead of "init.php")
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 plugin1,019 lines of code in 17 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 17 | 241 | 42 | 1,019 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 3.94 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 27.00 |
| Average method complexity | 1.90 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 16 | |
| ▷ Abstract classes | 1 | 6.25% |
| ▷ Concrete classes | 15 | 93.75% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 53 | |
| ▷ Static methods | 4 | 7.55% |
| ▷ Public methods | 53 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 6 | |
| ▷ Named functions | 3 | 50.00% |
| ▷ Anonymous functions | 3 | 50.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
8 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/wechat.png | 0.93KB | 0.41KB | ▼ 56.22% |
| images/alipay.png | 1.31KB | 0.49KB | ▼ 62.37% |
| images/moneymore.png | 2.73KB | 2.11KB | ▼ 22.68% |
| images/nzbanks.png | 1.19KB | 0.72KB | ▼ 39.82% |
| images/payid.png | 2.35KB | 1.90KB | ▼ 18.89% |