Benchmarks
Plugin footprint 75% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
It is recommended to fix the following installer errors
- The plugin did not install without errors
- > Warning in wp-includes/class-wp-hook.php+307
call_user_func_array() expects parameter 1 to be a valid callback, class '\WSB\Activator' not found
Server metrics [RAM: ▼0.01MB] [CPU: ▼313.72ms] Passed 4 tests
Analyzing server-side resources used by Payment Gateway for Wax with WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.08 | 54.61 ▲3.86 |
| Dashboard /wp-admin | 3.42 ▲0.01 | 35.72 ▲1.56 |
| Posts /wp-admin/edit.php | 3.65 ▲0.01 | 39.85 ▲2.24 |
| Add New Post /wp-admin/post-new.php | 6.89 ▼0.08 | 92.93 ▼1,258.35 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.01 | 24.89 ▼0.34 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 27 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Payment Gateway for Wax with WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,773 ▲19 | 15.55 ▼0.20 | 6.69 ▲0.48 | 2.03 ▼0.62 |
| Dashboard /wp-admin | 2,898 ▲37 | 6.02 ▼0.13 | 121.28 ▼16.23 | 155.63 ▼6.76 |
| Posts /wp-admin/edit.php | 2,695 ▲7 | 3.23 ▼0.01 | 66.24 ▲2.60 | 141.87 ▲4.66 |
| Add New Post /wp-admin/post-new.php | 1,672 ▼86 | 18.19 ▼3.86 | 397.39 ▼65.29 | 156.60 ▼6.54 |
| Media Library /wp-admin/upload.php | 1,704 ▲6 | 5.55 ▲0.01 | 143.69 ▼16.54 | 185.08 ▼5.28 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wc-wax-payment-gateway/includes/class-wc-wax-ajax.php:20
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/wc-wax-payment-gateway/includes/class-wc-gateway-wax.php:9
- > PHP Fatal error
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 90% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: These screenshots do not have images: #1 (The payment method show to customer under checkout.), #2 (The settings panel for store managers.)
wc-wax-payment-gateway/woocommerce-gateway-wax.php 85% from 13 tests
The main PHP file in "Payment Gateway for Wax with WooCommerce" ver. 1.2 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wc-wax-payment-gateway.php" instead of "woocommerce-gateway-wax.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
There were no executable files found in this plugin1,387 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 169 | 209 | 649 |
| PO File | 4 | 168 | 168 | 450 |
| Sass | 1 | 9 | 0 | 140 |
| CSS | 1 | 15 | 4 | 120 |
| SVG | 1 | 0 | 1 | 23 |
| JavaScript | 5 | 0 | 9 | 5 |
PHP code Passed 2 tests
A short 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.29 |
| Average class complexity | 17.40 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 2.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 50 | |
| ▷ Static methods | 22 | 44.00% |
| ▷ Public methods | 41 | 82.00% |
| ▷ Protected methods | 1 | 2.00% |
| ▷ Private methods | 8 | 16.00% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 7 | |
| ▷ Global constants | 7 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/copy.png | 0.42KB | 0.34KB | ▼ 19.59% |