Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.21ms] Passed 4 tests
Server-side resources used by Pay for Payment for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 35.58 ▼4.08 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 46.59 ▲0.33 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 42.44 ▼4.25 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.17 ▼12.83 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.69 ▲0.57 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 28 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
Pay for Payment for WooCommerce: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲69 | 13.14 ▼1.25 | 1.74 ▲0.05 | 40.91 ▼2.71 |
| Dashboard /wp-admin | 2,224 ▲36 | 4.84 ▼0.05 | 98.32 ▼7.41 | 39.82 ▼1.28 |
| Posts /wp-admin/edit.php | 2,103 ▲14 | 1.99 ▲0.01 | 34.85 ▼1.78 | 37.09 ▲6.67 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲29 | 23.10 ▼0.00 | 628.15 ▼72.05 | 52.22 ▼3.04 |
| Media Library /wp-admin/upload.php | 1,403 ▲12 | 4.29 ▲0.10 | 99.11 ▼0.92 | 40.57 ▼3.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means 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 take a closer look at the following
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woocommerce-pay-for-payment/woocommerce-payforpayment.php:22
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woocommerce-pay-for-payment/inc/class-pay4pay-admin.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Screenshots: Add a description for screenshot #2 in woocommerce-pay-for-payment/assets to your readme.txt
woocommerce-pay-for-payment/woocommerce-payforpayment.php 85% from 13 tests
The main file in "Pay for Payment for WooCommerce" v. 2.1.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Requires at least: The required version number did not match the one declared in readme.txt ("4.6" instead of "2.6")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woocommerce-pay-for-payment.php" instead of "woocommerce-payforpayment.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected1,870 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 8 | 372 | 425 | 1,160 |
| PHP | 8 | 149 | 190 | 672 |
| JavaScript | 1 | 3 | 0 | 35 |
| CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.51 |
| Average class complexity | 12.86 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 53.00 |
| Average method complexity | 3.18 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 41.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 | 38 | |
| ▷ Static methods | 16 | 42.11% |
| ▷ Public methods | 32 | 84.21% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 15.79% |
| Functions | 3 | |
| ▷ Named functions | 2 | 66.67% |
| ▷ Anonymous functions | 1 | 33.33% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
There are no PNG files in this plugin