Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.72MB] [CPU: ▼22.51ms] Passed 4 tests
An overview of server-side resources used by BitPay QuickPay
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 40.42 ▲2.88 |
| Dashboard /wp-admin | 3.21 ▼0.09 | 30.34 ▼20.81 |
| Posts /wp-admin/edit.php | 3.28 ▼0.08 | 35.70 ▼8.80 |
| Add New Post /wp-admin/post-new.php | 3.20 ▼2.69 | 34.23 ▼54.31 |
| Media Library /wp-admin/upload.php | 3.22 ▼0.01 | 28.85 ▼6.12 |
Server storage [IO: ▲3.98MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 24 new files
Database: no new tables, 12 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| bitpayquickpay_option_dev_token |
| bitpayquickpay_option_message |
| db_upgraded |
| bitpayquickpay_option_endpoint |
| can_compress_scripts |
| bitpayquickpay_option_default_amount |
| bitpayquickpay_option_prod_token |
| widget_recent-posts |
| ... |
Browser metrics Passed 4 tests
A check of browser resources used by BitPay QuickPay
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,880 ▲145 | 13.26 ▼1.11 | 5.62 ▲3.96 | 47.39 ▲4.47 |
| Dashboard /wp-admin | 2,224 ▲42 | 5.90 ▲1.01 | 105.32 ▲5.25 | 41.25 ▼1.43 |
| Posts /wp-admin/edit.php | 2,107 ▲18 | 2.00 ▼0.02 | 41.06 ▲6.20 | 51.38 ▲15.79 |
| Add New Post /wp-admin/post-new.php | 1,543 ▲1 | 23.21 ▲5.05 | 657.04 ▲13.06 | 53.66 ▲2.44 |
| Media Library /wp-admin/upload.php | 1,406 ▲21 | 4.28 ▲0.01 | 94.87 ▲0.09 | 40.55 ▼2.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 12 options in the database
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- bitpayquickpay_option_endpoint
- widget_theysaidso_widget
- db_upgraded
- bitpayquickpay_option_default_amount
- bitpayquickpay_option_message
- bitpayquickpay_option_dev_token
- bitpayquickpay_option_currency
- ...
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: bitcoin, bitpay, cryptocurrency, bitcoin cash, payment gateway...
bitpay-quickpay/index.php 92% from 13 tests
"BitPay QuickPay" version 1.1.1910's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("bitpay-quickpay.php" instead of "index.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
Success! There were no dangerous files found in this plugin710 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 125 | 22 | 528 |
| JavaScript | 2 | 43 | 3 | 145 |
| Markdown | 1 | 22 | 0 | 25 |
| CSS | 1 | 3 | 0 | 12 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| Average class complexity | 1.60 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.14 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.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 | 21 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 21 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 16 | |
| ▷ Named functions | 15 | 93.75% |
| ▷ Anonymous functions | 1 | 6.25% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
11 PNG files occupy 3.94MB with 2.70MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-256x256.png | 53.83KB | 14.29KB | ▼ 73.45% |
| assets/screenshot-1.png | 298.82KB | 94.03KB | ▼ 68.53% |
| assets/screenshot-8.png | 657.68KB | 285.96KB | ▼ 56.52% |
| assets/screenshot-2.png | 310.49KB | 93.48KB | ▼ 69.89% |
| assets/screenshot-3.png | 442.71KB | 116.44KB | ▼ 73.70% |