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.25MB] [CPU: ▲3.20ms] Passed 4 tests
Analyzing server-side resources used by Payje for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.74 ▲0.28 | 50.29 ▲8.20 |
| Dashboard /wp-admin | 3.58 ▲0.28 | 52.40 ▲1.81 |
| Posts /wp-admin/edit.php | 3.63 ▲0.27 | 55.89 ▲5.47 |
| Add New Post /wp-admin/post-new.php | 6.12 ▲0.23 | 91.45 ▼2.70 |
| Media Library /wp-admin/upload.php | 3.44 ▲0.21 | 43.99 ▲8.96 |
Server storage [IO: ▲1.34MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 207 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by Payje for WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,846 ▲111 | 14.80 ▲0.23 | 1.91 ▼0.15 | 42.24 ▼4.58 |
| Dashboard /wp-admin | 2,240 ▲52 | 5.86 ▼0.04 | 99.92 ▼12.27 | 68.44 ▲14.47 |
| Posts /wp-admin/edit.php | 2,137 ▲45 | 2.01 ▲0.05 | 40.08 ▲3.30 | 40.95 ▲3.99 |
| Add New Post /wp-admin/post-new.php | 1,560 ▲26 | 23.17 ▲0.08 | 708.30 ▲1.15 | 62.44 ▲5.63 |
| Media Library /wp-admin/upload.php | 1,431 ▲40 | 4.25 ▲0.04 | 135.44 ▲22.23 | 58.00 ▲9.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 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 does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 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
Please take a closer look at the following
- 51× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UriInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/psr7/src/Uri.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/payje-for-woocommerce/libraries/payje/admin/views/dashboard.php:8
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Handler\\CurlFactoryInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UploadedFileInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/psr7/src/UploadedFile.php:12
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/guzzle/src/Exception/InvalidArgumentException.php:5
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/psr7/src/InflateStream.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/psr7/src/CachingStream.php:13
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/promises/src/RejectedPromise.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/payje-for-woocommerce/libraries/payje/vendor/guzzlehttp/psr7/src/FnStream.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/payje-for-woocommerce/admin/views/settings.php:8
- > 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 on the user side
Optimizations
Plugin configuration 93% 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 descriptions for screenshots #1, #2, #3, #4, #5, #6 in payje-for-woocommerce/assets to your readme.txt
payje-for-woocommerce/payje-wc.php 92% from 13 tests
"Payje for WooCommerce" version 1.0.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("payje-for-woocommerce.php" instead of "payje-wc.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
No dangerous file extensions were detected18,573 lines of code in 181 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 137 | 2,499 | 5,937 | 11,229 |
| Markdown | 17 | 1,307 | 0 | 3,751 |
| JavaScript | 5 | 605 | 173 | 2,412 |
| JSON | 10 | 0 | 0 | 1,045 |
| CSS | 5 | 0 | 0 | 76 |
| SVG | 5 | 0 | 1 | 44 |
| make | 1 | 4 | 0 | 9 |
| YAML | 1 | 0 | 0 | 7 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 13.24 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 88.00 |
| Average method complexity | 2.80 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 11 | |
| Interfaces | 26 | |
| Traits | 3 | |
| Classes | 88 | |
| ▷ Abstract classes | 1 | 1.14% |
| ▷ Concrete classes | 87 | 98.86% |
| ▷ Final classes | 35 | 40.23% |
| Methods | 817 | |
| ▷ Static methods | 144 | 17.63% |
| ▷ Public methods | 678 | 82.99% |
| ▷ Protected methods | 10 | 1.22% |
| ▷ Private methods | 129 | 15.79% |
| Functions | 135 | |
| ▷ Named functions | 45 | 33.33% |
| ▷ Anonymous functions | 90 | 66.67% |
| Constants | 74 | |
| ▷ Global constants | 9 | 12.16% |
| ▷ Class constants | 65 | 87.84% |
| ▷ Public constants | 54 | 83.08% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected