Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.93ms] Passed 4 tests
An overview of server-side resources used by Cryptocurrency Payments for Paid Memberships Pro (PMPro) by CryptoPay
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 40.41 ▼6.67 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 47.20 ▼1.23 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 45.80 ▲1.92 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 85.23 ▼13.73 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 37.10 ▲2.26 |
Server storage [IO: ▲0.62MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 21 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Cryptocurrency Payments for Paid Memberships Pro (PMPro) by CryptoPay
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,809 ▲52 | 14.45 ▲0.20 | 1.89 ▼0.34 | 44.76 ▼4.51 |
| Dashboard /wp-admin | 2,212 ▲24 | 5.83 ▲0.95 | 98.00 ▼8.98 | 40.65 ▼1.94 |
| Posts /wp-admin/edit.php | 2,098 ▲9 | 2.04 ▲0.06 | 38.94 ▲0.89 | 37.49 ▲4.90 |
| Add New Post /wp-admin/post-new.php | 1,543 ▲29 | 23.27 ▲5.62 | 678.28 ▼12.76 | 57.96 ▲8.13 |
| Media Library /wp-admin/upload.php | 1,397 ▲9 | 4.22 ▲0.01 | 94.09 ▼17.19 | 41.51 ▼3.51 |
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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 10× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
require_once(): Failed opening required 'PMPRO_DIR/classes/gateways/class.pmprogateway.php' (include_path='.:/usr/share/php') in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/pro/class.pmprogateway_cryptopay.php on line 3
- > PHP Warning
require_once(PMPRO_DIR/classes/gateways/class.pmprogateway.php): failed to open stream: No such file or directory in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/pro/class.pmprogateway_cryptopay.php on line 3
- > PHP Fatal error
Uncaught Error: Class 'BeycanPress\\CryptoPayLite\\Models\\AbstractTransaction' not found in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/lite/class.pmpro_transaction_model.php:5
- > PHP Warning
Use of undefined constant PMPRO_DIR - assumed 'PMPRO_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/lite/class.pmprogateway_cryptopay.php on line 3
- > PHP Warning
require_once(PMPRO_DIR/classes/gateways/class.pmprogateway.php): failed to open stream: No such file or directory in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/lite/class.pmprogateway_cryptopay.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'PMPRO_DIR/classes/gateways/class.pmprogateway.php' (include_path='.:/usr/share/php') in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/lite/class.pmprogateway_cryptopay.php on line 3
- > PHP Fatal error
Uncaught Error: Class 'BeycanPress\\CryptoPay\\Models\\AbstractTransaction' not found in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/pro/class.pmpro_transaction_model.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/class.pmpro_ajax_api.php:10
- > PHP Warning
Use of undefined constant PMPRO_DIR - assumed 'PMPRO_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/classes/pro/class.pmprogateway_cryptopay.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/cryptocurrency-payments-for-paid-memberships-pro/index.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
10 plugin tags: networks, cryptocurrency, ethereum, bitcoin, blockchain...
cryptocurrency-payments-for-paid-memberships-pro/index.php 85% from 13 tests
The main PHP file in "Cryptocurrency Payments for Paid Memberships Pro (PMPro) by CryptoPay" ver. 1.0.2 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("cryptocurrency-payments-for-paid-memberships-pro.php" instead of "index.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin751 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 137 | 88 | 695 |
| JavaScript | 1 | 3 | 0 | 46 |
| Markdown | 1 | 9 | 0 | 10 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| Average class complexity | 4.71 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 8.00 |
| Average method complexity | 1.70 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 24 | |
| ▷ Static methods | 14 | 58.33% |
| ▷ Public methods | 24 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 20 | |
| ▷ Named functions | 1 | 5.00% |
| ▷ Anonymous functions | 19 | 95.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
8 PNG files occupy 0.55MB with 0.34MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-256x256.png | 18.31KB | 5.92KB | ▼ 67.69% |
| assets/Screenshot_3.png | 77.95KB | 30.90KB | ▼ 60.36% |
| assets/Screenshot_2.png | 80.28KB | 32.93KB | ▼ 58.98% |
| assets/icon-128x128.png | 8.34KB | 3.48KB | ▼ 58.29% |
| assets/banner-772x250.png | 67.84KB | 21.02KB | ▼ 69.01% |