Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.10ms] Passed 4 tests
A check of server-side resources used by Bitcoin Payments by Yellow (for woocommerce)
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 40.33 ▼8.08 |
Dashboard /wp-admin | 3.31 ▲0.00 | 47.08 ▼2.21 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.00 ▲6.78 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 97.09 ▲2.36 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.65 ▼0.46 |
Server storage [IO: ▲1.25MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 260 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Bitcoin Payments by Yellow (for woocommerce)
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 14.48 ▲0.13 | 1.76 ▼0.11 | 42.60 ▼3.13 |
Dashboard /wp-admin | 2,203 ▲15 | 5.86 ▲0.01 | 94.18 ▼24.31 | 40.16 ▼2.95 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.03 ▲0.02 | 39.76 ▲3.70 | 34.65 ▼0.83 |
Add New Post /wp-admin/post-new.php | 1,542 ▲6 | 18.20 ▼5.09 | 609.83 ▼49.78 | 56.46 ▲5.49 |
Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.18 ▼0.02 | 94.38 ▼8.70 | 41.70 ▼1.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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
- 132× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Ring\\Future\\FutureInterface' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Pool.php:34
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/streams/tests/NoSeekStreamTest.php:11
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/CouldNotRewindStreamException.php:4
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Event\\HasEmitterInterface' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/ClientInterface.php:12
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\ClientInterface' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Client.php:18
- > PHP Fatal error
Uncaught Error: Interface 'React\\Promise\\ExtendedPromiseInterface' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/react/promise/src/RejectedPromise.php:5
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\TransferException' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:13
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Message\\AbstractMessage' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Message/Request.php:12
- > PHP Fatal error
Cannot use lexical variable $eventName as a parameter name in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/guzzlehttp/guzzle/src/Event/Emitter.php on line 48
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in wp-content/plugins/yellow-bitcoin-payment-for-woocommerce/vendor/react/promise/tests/TestCase.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
5 plugin tags: bitcoin, woocommerce, yellow, payment, yellowpay
yellow-bitcoin-payment-for-woocommerce/woocommerce-yellow.php 92% from 13 tests
The principal PHP file in "Bitcoin Payments by Yellow (for woocommerce)" v. 1.0.1 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("yellow-bitcoin-payment-for-woocommerce.php" instead of "woocommerce-yellow.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 plugin21,866 lines of code in 245 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 192 | 3,005 | 4,693 | 16,123 |
Markdown | 10 | 646 | 0 | 2,576 |
reStructuredText | 19 | 1,222 | 1,570 | 2,029 |
JSON | 7 | 0 | 0 | 451 |
make | 5 | 78 | 10 | 333 |
JavaScript | 1 | 18 | 60 | 163 |
YAML | 4 | 17 | 0 | 76 |
XML | 4 | 2 | 0 | 71 |
Python | 2 | 10 | 0 | 41 |
HTML | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
Average class complexity | 7.22 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 89.00 |
Average method complexity | 1.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 43.00 |
Code structure | ||
---|---|---|
Namespaces | 25 | |
Interfaces | 25 | |
Traits | 15 | |
Classes | 150 | |
▷ Abstract classes | 4 | 2.67% |
▷ Concrete classes | 146 | 97.33% |
▷ Final classes | 3 | 2.05% |
Methods | 1,377 | |
▷ Static methods | 86 | 6.25% |
▷ Public methods | 1,265 | 91.87% |
▷ Protected methods | 18 | 1.31% |
▷ Private methods | 94 | 6.83% |
Functions | 252 | |
▷ Named functions | 19 | 7.54% |
▷ Anonymous functions | 233 | 92.46% |
Constants | 11 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 11 | 100.00% |
▷ Public constants | 11 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.24MB with 0.08MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/guzzlehttp/guzzle/docs/_static/logo.png | 241.87KB | 69.68KB | ▼ 71.19% |
vendor/guzzlehttp/guzzle/docs/_static/guzzle-icon.png | 0.78KB | 0.94KB | 0.00% |