Benchmarks
Plugin footprint Passed 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: ▲0.02MB] [CPU: ▼301.26ms] Passed 4 tests
Analyzing server-side resources used by Sovereign Crypto Payments
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.04 | 59.17 ▲4.76 |
| Dashboard /wp-admin | 3.45 ▲0.05 | 85.10 ▲50.90 |
| Posts /wp-admin/edit.php | 3.68 ▲0.04 | 39.18 ▲2.88 |
| Add New Post /wp-admin/post-new.php | 6.91 ▼0.05 | 94.73 ▼1,195.16 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.04 | 24.78 ▼17.52 |
Server storage [IO: ▲0.67MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 35 new files
Database: 3 new tables, no new options
| New tables |
|---|
| wp_obzsscp_carousel |
| wp_obzsscp_electrum_addresses |
| wp_obzsscp_payments |
Browser metrics Passed 4 tests
An overview of browser requirements for Sovereign Crypto Payments
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,781 ▲27 | 15.96 ▼0.02 | 5.69 ▼0.12 | 2.72 ▼0.20 |
| Dashboard /wp-admin | 2,878 ▲27 | 6.12 ▼0.09 | 119.86 ▼18.17 | 158.64 ▼41.87 |
| Posts /wp-admin/edit.php | 2,672 ▼16 | 3.24 ▲0.00 | 70.61 ▲5.79 | 185.21 ▲41.28 |
| Add New Post /wp-admin/post-new.php | 1,661 ▼91 | 16.95 ▼3.93 | 433.27 ▼36.90 | 159.88 ▼1.29 |
| Media Library /wp-admin/upload.php | 1,701 ▲3 | 5.52 ▲0.05 | 148.83 ▼1.80 | 188.73 ▲0.96 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/sovereign-crypto-payments/src/OBZSSCP_Gateway.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sovereign-crypto-payments/sovereign-crypto-payments.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 97% 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
Please fix the following attributes:
- Tags: Too many tags (14 tag instead of maximum 10); only the first 5 tags are used in your directory listing
sovereign-crypto-payments/sovereign-crypto-payments.php Passed 13 tests
The main PHP script in "Sovereign Crypto Payments" version 1.0.4 is automatically included on every request by WordPress
47 characters long description:
Cryptocurrency Payment Gateway for WooCommerce.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin7,645 lines of code in 27 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 25 | 1,426 | 1,144 | 7,332 |
| JavaScript | 1 | 45 | 14 | 290 |
| CSS | 1 | 4 | 0 | 23 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 34.42 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 233.00 |
| Average method complexity | 4.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 47.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 38 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 38 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 372 | |
| ▷ Static methods | 205 | 55.11% |
| ▷ Public methods | 335 | 90.05% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 37 | 9.95% |
| Functions | 24 | |
| ▷ Named functions | 23 | 95.83% |
| ▷ Anonymous functions | 1 | 4.17% |
| Constants | 51 | |
| ▷ Global constants | 40 | 78.43% |
| ▷ Class constants | 11 | 21.57% |
| ▷ Public constants | 11 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
7 PNG files occupy 0.31MB with 0.15MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshots/screenshot-1.png | 80.57KB | 31.35KB | ▼ 61.09% |
| assets/screenshots/screenshot-2.png | 88.10KB | 33.76KB | ▼ 61.68% |
| assets/screenshots/screenshot-5.png | 5.70KB | 2.91KB | ▼ 48.96% |
| assets/img/bitcoin_logo_small.png | 1.01KB | 0.84KB | ▼ 16.96% |
| assets/screenshots/screenshot-6.png | 44.08KB | 18.16KB | ▼ 58.81% |