Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲1.39MB] [CPU: ▲15.68ms] Passed 4 tests
An overview of server-side resources used by Change Payments Account
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.83 ▲1.37 | 53.43 ▲7.91 |
| Dashboard /wp-admin | 4.75 ▲1.44 | 71.10 ▲21.79 |
| Posts /wp-admin/edit.php | 4.79 ▲1.44 | 71.49 ▲24.07 |
| Add New Post /wp-admin/post-new.php | 7.28 ▲1.39 | 109.89 ▲14.63 |
| Media Library /wp-admin/upload.php | 4.58 ▲1.35 | 51.97 ▲18.39 |
Server storage [IO: ▲8.59MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 516 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
Change Payments Account: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,106 ▲349 | 18.55 ▲4.03 | 1.67 ▼0.94 | 37.45 ▼13.17 |
| Dashboard /wp-admin | 2,484 ▲299 | 9.18 ▲4.28 | 188.01 ▲70.46 | 42.01 ▼2.36 |
| Posts /wp-admin/edit.php | 2,402 ▲316 | 6.08 ▲4.07 | 85.14 ▲50.10 | 35.60 ▲3.64 |
| Add New Post /wp-admin/post-new.php | 1,839 ▲306 | 22.22 ▼0.96 | 713.62 ▲72.88 | 39.03 ▼11.58 |
| Media Library /wp-admin/upload.php | 1,551 ▲163 | 6.64 ▲2.46 | 108.20 ▲14.15 | 39.24 ▼0.66 |
| Change Payments Account /wp-admin/crb_carbon_fields_container_change_payments_account.php | 26 | 0.44 | 0.13 | 13.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
Smoke tests 25% 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 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
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/templates/Exception/incorrect-syntax.php
- 134× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Datastore\\Meta_Datastore' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Datastore/Term_Meta_Datastore.php:10
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Service\\Service' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Service/Revisions_Service.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/change-payments-account/vendor/pimple/pimple/src/Pimple/Tests/Psr11/ServiceLocatorTest.php:39
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Condition' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Container/Condition/Current_User_ID_Condition.php:8
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Field' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Field/Map_Field.php:12
- > PHP Fatal error
Uncaught Error: Interface 'CPY\\ProcessorInterface' not found in wp-content/plugins/change-payments-account/processors/Filters.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Carbon_Fields\\Datastore\\Datastore_Holder_Interface' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Container/Container.php:18
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Date_Field' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Field/Time_Field.php:8
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Condition' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Container/Condition/Post_Parent_ID_Condition.php:8
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Service\\Service' not found in wp-content/plugins/change-payments-account/vendor/htmlburger/carbon-fields/core/Service/REST_API_Service.php:11
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
These are user-side errors you should fix
- > GET request to /wp-admin/crb_carbon_fields_container_change_payments_account.php
- > Network (severe)
wp-admin/crb_carbon_fields_container_change_payments_account.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 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
4 plugin tags: credit card, payment, woocommerce, payment request
change-payments-account/change-payments-account.php 77% from 13 tests
The entry point to "Change Payments Account" version 0.0.1 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Requires PHP: Required version must match the one declared in readme.txt ("7.0" instead of "7.4")
- Domain Path: You should use only dashes and lowercase characters for the domain path ("languages")
- Domain Path: Prefix the domain path with a forward slash character ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin29,818 lines of code in 459 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 172 | 5,187 | 8,459 | 12,929 |
| PHP | 192 | 3,038 | 7,446 | 10,467 |
| PO File | 27 | 835 | 1,039 | 2,254 |
| Sass | 48 | 338 | 0 | 1,764 |
| CSS | 7 | 325 | 1,139 | 1,658 |
| JSON | 6 | 0 | 0 | 542 |
| reStructuredText | 1 | 96 | 139 | 97 |
| Markdown | 4 | 29 | 0 | 76 |
| XML | 1 | 2 | 0 | 16 |
| YAML | 1 | 4 | 0 | 15 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 7.12 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 50.00 |
| Average method complexity | 2.01 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 38 | |
| Interfaces | 12 | |
| Traits | 0 | |
| Classes | 155 | |
| ▷ Abstract classes | 11 | 7.10% |
| ▷ Concrete classes | 144 | 92.90% |
| ▷ Final classes | 3 | 2.08% |
| Methods | 1,059 | |
| ▷ Static methods | 100 | 9.44% |
| ▷ Public methods | 887 | 83.76% |
| ▷ Protected methods | 165 | 15.58% |
| ▷ Private methods | 7 | 0.66% |
| Functions | 163 | |
| ▷ Named functions | 23 | 14.11% |
| ▷ Anonymous functions | 140 | 85.89% |
| Constants | 31 | |
| ▷ Global constants | 7 | 22.58% |
| ▷ Class constants | 24 | 77.42% |
| ▷ Public constants | 24 | 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
No PNG files were detected