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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.09MB] [CPU: ▼7.85ms] Passed 4 tests
This is a short check of server-side resources used by MixPay Crypto Payment Gateway for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 37.84 ▼0.21 |
| Dashboard /wp-admin | 3.40 ▲0.06 | 48.68 ▼15.91 |
| Posts /wp-admin/edit.php | 3.51 ▲0.16 | 49.40 ▼8.12 |
| Add New Post /wp-admin/post-new.php | 5.98 ▲0.10 | 97.37 ▼6.54 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.10 | 38.69 ▼0.83 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for MixPay Crypto Payment Gateway for WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.23 ▼0.12 | 1.69 ▲0.05 | 40.80 ▼5.60 |
| Dashboard /wp-admin | 2,195 ▲21 | 5.59 ▼0.02 | 94.61 ▼4.64 | 41.54 ▼3.01 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 1.97 ▼0.01 | 39.58 ▲1.96 | 36.58 ▲1.99 |
| Add New Post /wp-admin/post-new.php | 1,528 ▼0 | 23.51 ▲0.19 | 650.75 ▲0.22 | 59.07 ▼5.78 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.19 ▲0.00 | 96.98 ▼6.04 | 41.97 ▼2.32 |
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
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests Passed 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 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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
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:
- Requires php: Version format is invalid
mixpay-gateway-for-woocommerce/class-wc-gateway-mixpay.php 85% from 13 tests
The principal PHP file in "MixPay Crypto Payment Gateway for WooCommerce" v. 1.0.10 is loaded by WordPress automatically on each request
It is important to fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; 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 ("mixpay-gateway-for-woocommerce.php" instead of "class-wc-gateway-mixpay.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
Success! There were no dangerous files found in this plugin546 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 109 | 106 | 465 |
| Markdown | 1 | 29 | 0 | 81 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 51.00 |
| ▷ Minimum class complexity | 51.00 |
| ▷ Maximum class complexity | 51.00 |
| Average method complexity | 3.38 |
| ▷ 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 | 21 | |
| ▷ Static methods | 1 | 4.76% |
| ▷ Public methods | 21 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 14 | |
| ▷ Global constants | 14 | 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
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/payemt_button.png | 21.32KB | 6.81KB | ▼ 68.06% |