Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲1.89MB] [CPU: ▲13.72ms] Passed 4 tests
A check of server-side resources used by WooCommerce Cryptocurrency Payment Gateway for WordPress by CryptoPay
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 5.24 ▲1.78 | 54.30 ▲15.61 |
| Dashboard /wp-admin | 5.26 ▲1.96 | 60.16 ▲14.20 |
| Posts /wp-admin/edit.php | 5.31 ▲1.96 | 67.77 ▲21.75 |
| Add New Post /wp-admin/post-new.php | 7.80 ▲1.91 | 96.68 ▲3.31 |
| Media Library /wp-admin/upload.php | 5.12 ▲1.90 | 57.05 ▲23.15 |
| Settings /wp-admin/admin.php?page=cryptopay_lite_settings | 5.19 | 49.49 |
| Buy premium /wp-admin/admin.php?page=cryptopay_lite_home | 5.12 | 45.58 |
Server storage [IO: ▲18.11MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 1,723 new files
Database: 1 new table, 10 new options
| New tables |
|---|
| wp_cpl_order_transaction |
| New WordPress options |
|---|
| widget_theysaidso_widget |
| cryptopay_premium_version_promotion |
| cryptopay_premium_version_promotion_date |
| wp_cpl_order_transaction_version |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| cryptopay_lite_settings |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by WooCommerce Cryptocurrency Payment Gateway for WordPress by CryptoPay
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,684 ▲949 | 24.00 ▲9.62 | 57.20 ▲55.43 | 28.79 ▼10.90 |
| Dashboard /wp-admin | 2,222 ▲34 | 4.92 ▼0.96 | 110.70 ▲3.03 | 76.74 ▲33.07 |
| Posts /wp-admin/edit.php | 2,117 ▲25 | 1.98 ▼0.02 | 35.81 ▼3.95 | 33.20 ▼1.53 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲33 | 23.16 ▲5.56 | 765.15 ▲161.77 | 52.20 ▼12.67 |
| Media Library /wp-admin/upload.php | 1,416 ▲28 | 4.16 ▼0.04 | 123.90 ▲22.19 | 51.05 ▲6.85 |
| Settings /wp-admin/admin.php?page=cryptopay_lite_settings | 1,432 | 3.77 | 65.85 | 84.51 |
| Buy premium /wp-admin/admin.php?page=cryptopay_lite_home | 1,619 | 9.42 | 254.38 | 58.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie tables were found after uninstall: 1 table
- wp_cpl_order_transaction
- This plugin did not uninstall successfully, leaving 10 options in the database
- wp_cpl_order_transaction_version
- theysaidso_admin_options
- db_upgraded
- cryptopay_lite_settings
- cryptopay_premium_version_promotion_date
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- cryptopay_premium_version_promotion
- can_compress_scripts
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 6× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/cryptopay-wc-lite/app/PluginHero/Templates/log.php
- > /wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/docker/php/composer-setup.php
- > /wp-content/plugins/cryptopay-wc-lite/vendor/beycanpress/wp-table/src/Table.php
- > /wp-content/plugins/cryptopay-wc-lite/vendor/beycanpress/request/api.php
- > /wp-content/plugins/cryptopay-wc-lite/views/checkout.php
- > /wp-content/plugins/cryptopay-wc-lite/views/feedback.php
- 283× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/cryptopay-wc-lite/views/pages/transaction-page/form.php:11
- > PHP Fatal error
Uncaught Error: Class 'Test\\TestCase' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/test/unit/BooleanFormatterTest.php:9
- > PHP Fatal error
Uncaught Error: Class 'Web3\\Methods\\EthMethod' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/src/Methods/Eth/Accounts.php:17
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Client\\ClientExceptionInterface' not found in wp-content/plugins/cryptopay-wc-lite/vendor/guzzlehttp/guzzle/src/Exception/GuzzleException.php:7
- > PHP Fatal error
Uncaught Error: Class 'phpseclib\\Crypt\\Base' not found in wp-content/plugins/cryptopay-wc-lite/vendor/phpseclib/phpseclib/phpseclib/Crypt/RC4.php:54
- > PHP Fatal error
Uncaught Error: Interface 'Web3\\Formatters\\IFormatter' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/src/Formatters/TransactionFormatter.php:20
- > PHP Fatal error
Uncaught Error: Class 'Web3\\Methods\\EthMethod' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/src/Methods/Eth/Hashrate.php:18
- > PHP Fatal error
Uncaught Error: Class 'Web3\\Methods\\EthMethod' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/src/Methods/Net/PeerCount.php:18
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Client\\ClientExceptionInterface' not found in wp-content/plugins/cryptopay-wc-lite/vendor/psr/http-client/src/NetworkExceptionInterface.php:14
- > PHP Fatal error
Uncaught Error: Class 'Web3\\Contracts\\SolidityType' not found in wp-content/plugins/cryptopay-wc-lite/vendor/web3p/web3.php/src/Contracts/Types/Integer.php:20
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There are user-side issues you should fix
- > GET request to /wp-admin/admin.php?page=cryptopay_lite_home
- > Other (warning) in unknown
/wp-admin/admin.php?page=cryptopay_lite_home 161 Unrecognized feature: 'web-share'.
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Tags: Please reduce the number of tags, currently 19 tag instead of maximum 10
cryptopay-wc-lite/index.php 85% from 13 tests
"WooCommerce Cryptocurrency Payment Gateway for WordPress by CryptoPay" version 1.6.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Text Domain: The text domain should only use lowercase characters and dashes
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("cryptopay-wc-lite.php" instead of "index.php")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected185,733 lines of code in 1,537 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 561 | 15,408 | 30,087 | 78,387 |
| SVG | 804 | 79 | 797 | 59,317 |
| CSS | 11 | 1,392 | 1,284 | 12,869 |
| JavaScript | 14 | 2,559 | 872 | 10,615 |
| Sass | 22 | 1,432 | 3 | 8,055 |
| PO File | 21 | 3,358 | 3,771 | 6,824 |
| Markdown | 37 | 1,896 | 0 | 5,162 |
| JSON | 43 | 10 | 0 | 4,026 |
| YAML | 11 | 69 | 0 | 276 |
| XML | 6 | 12 | 0 | 127 |
| Solidity | 2 | 9 | 0 | 32 |
| Python | 1 | 8 | 5 | 17 |
| Bourne Shell | 1 | 5 | 0 | 10 |
| make | 1 | 3 | 0 | 10 |
| Dockerfile | 1 | 4 | 0 | 5 |
| HTML | 1 | 0 | 0 | 1 |
PHP code 50% from 2 tests
Analyzing cyclomatic complexity and code structure
It is recommended to fix the following
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 109)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 21.07 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 644.00 |
| Average method complexity | 4.26 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 109.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 62 | |
| Interfaces | 33 | |
| Traits | 6 | |
| Classes | 476 | |
| ▷ Abstract classes | 12 | 2.52% |
| ▷ Concrete classes | 464 | 97.48% |
| ▷ Final classes | 51 | 10.99% |
| Methods | 3,265 | |
| ▷ Static methods | 428 | 13.11% |
| ▷ Public methods | 3,038 | 93.05% |
| ▷ Protected methods | 43 | 1.32% |
| ▷ Private methods | 184 | 5.64% |
| Functions | 486 | |
| ▷ Named functions | 167 | 34.36% |
| ▷ Anonymous functions | 319 | 65.64% |
| Constants | 289 | |
| ▷ Global constants | 35 | 12.11% |
| ▷ Class constants | 254 | 87.89% |
| ▷ Public constants | 223 | 87.80% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
12 PNG files occupy 0.18MB with 0.04MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/menu.png | 1.97KB | 1.72KB | ▼ 12.51% |
| assets/images/wallets/binancewallet.png | 5.24KB | 5.21KB | ▼ 0.58% |
| vendor/beycanpress/csf/assets/images/checkerboard.png | 2.29KB | 2.54KB | 0.00% |
| assets/images/wallets/trustwallet.png | 8.38KB | 5.17KB | ▼ 38.28% |
| assets/images/wallets/walletconnect.png | 10.49KB | 4.10KB | ▼ 60.95% |