Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼1.79ms] Passed 4 tests
A check of server-side resources used by WooCommerce Crypto Billings Payment Gateway
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 40.44 ▼4.60 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 51.88 ▼0.80 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.78 ▼1.23 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 92.11 ▲0.10 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.99 ▼0.54 |
Server storage [IO: ▲0.86MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 138 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
WooCommerce Crypto Billings 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,796 ▲35 | 14.35 ▼0.26 | 1.82 ▲0.11 | 42.98 ▼3.86 |
| Dashboard /wp-admin | 2,196 ▲16 | 5.64 ▼0.03 | 96.06 ▼2.78 | 43.75 ▲0.64 |
| Posts /wp-admin/edit.php | 2,107 ▲7 | 2.02 ▲0.00 | 40.42 ▲4.74 | 37.39 ▲1.68 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 23.28 ▼0.22 | 608.79 ▼15.71 | 54.83 ▲3.33 |
| Media Library /wp-admin/upload.php | 1,407 ▲4 | 4.20 ▼0.11 | 100.94 ▼4.45 | 43.85 ▼1.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 42× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/Stream.php:11
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\TransferException' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:12
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/Request.php:12
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/NoSeekStream.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/InflateStream.php:17
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Psr7\\Request' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/ServerRequest.php:25
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UriInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/Uri.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UploadedFileInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/psr7/src/UploadedFile.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/woo-cryptobillings-gateway/lib/vendor/guzzlehttp/guzzle/src/Exception/SeekException.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)
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
woo-cryptobillings-gateway/woocommerce-cryptobillings-gateway.php 85% from 13 tests
The main file in "WooCommerce Crypto Billings Payment Gateway" v. 1.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("woo-cryptobillings-gateway.php" instead of "woocommerce-cryptobillings-gateway.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin12,505 lines of code in 120 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 100 | 1,794 | 5,011 | 8,779 |
| Markdown | 10 | 943 | 0 | 3,177 |
| JSON | 7 | 0 | 0 | 470 |
| CSS | 1 | 14 | 0 | 63 |
| make | 1 | 4 | 0 | 9 |
| JavaScript | 1 | 3 | 0 | 7 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 13.49 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 81.00 |
| Average method complexity | 2.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 9 | |
| Interfaces | 14 | |
| Traits | 2 | |
| Classes | 71 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 71 | 100.00% |
| ▷ Final classes | 7 | 9.86% |
| Methods | 674 | |
| ▷ Static methods | 68 | 10.09% |
| ▷ Public methods | 559 | 82.94% |
| ▷ Protected methods | 6 | 0.89% |
| ▷ Private methods | 109 | 16.17% |
| Functions | 143 | |
| ▷ Named functions | 56 | 39.16% |
| ▷ Anonymous functions | 87 | 60.84% |
| Constants | 68 | |
| ▷ Global constants | 7 | 10.29% |
| ▷ Class constants | 61 | 89.71% |
| ▷ Public constants | 61 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
10 PNG files occupy 0.19MB with 0.09MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/coins/DASH.png | 0.73KB | 0.86KB | 0.00% |
| assets/images/coins/BCH.png | 3.86KB | 2.38KB | ▼ 38.37% |
| assets/images/coins/LTC.png | 8.42KB | 4.06KB | ▼ 51.72% |
| assets/images/coins/DOPE.png | 10.68KB | 4.08KB | ▼ 61.77% |
| assets/images/accepted-coin-banners/dopecoin-accepted.png | 112.17KB | 30.78KB | ▼ 72.56% |