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: ▼4.00ms] Passed 4 tests
This is a short check of server-side resources used by GoPay for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.00 | 38.73 ▼11.49 |
| Dashboard /wp-admin | 3.35 ▲0.00 | 54.12 ▼1.08 |
| Posts /wp-admin/edit.php | 3.40 ▲0.00 | 45.81 ▼1.02 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.00 | 86.17 ▼0.51 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.00 | 35.10 ▼2.39 |
Server storage [IO: ▲1.72MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 300 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for GoPay for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.44 ▼0.23 | 2.39 ▲0.51 | 43.04 ▼4.93 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.88 ▼1.03 | 111.72 ▲1.74 | 38.81 ▼3.49 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.01 ▼0.01 | 40.38 ▲2.71 | 36.30 ▲4.04 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲9 | 23.17 ▲0.12 | 655.98 ▼26.44 | 62.28 ▲7.30 |
| Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.17 ▼0.03 | 97.48 ▼5.99 | 42.03 ▼2.75 |
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
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 99× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\BadResponseException' not found in wp-content/plugins/gopay-gateway/vendor/guzzlehttp/guzzle/src/Exception/ServerException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/gopay-gateway/vendor/guzzlehttp/psr7/src/InflateStream.php:20
- > PHP Fatal error
Uncaught Error: Class 'GoPay\\GivenGoPay' not found in wp-content/plugins/gopay-gateway/vendor/gopay/payments-sdk-php/tests/remote/WhenApiFailedTest.php:7
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/gopay-gateway/vendor/guzzlehttp/psr7/src/LazyOpenStream.php:13
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in wp-content/plugins/gopay-gateway/vendor/gopay/payments-sdk-php/tests/remote/GivenGoPay.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/gopay-gateway/vendor/psr/http-message/src/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Promise\\RejectionException' not found in wp-content/plugins/gopay-gateway/vendor/guzzlehttp/promises/src/AggregateException.php:8
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/gopay-gateway/vendor/gopay/payments-sdk-php/tests/phpunit/../../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/gopay-gateway/vendor/gopay/payments-sdk-php/tests/phpunit/TestUtils.php on line 5
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/gopay-gateway/vendor/psr/http-message/src/ResponseInterface.php:20
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/gopay-gateway/vendor/guzzlehttp/guzzle/src/Cookie/FileCookieJar.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 96% 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
2 plugin tags: woocommerce, gopay
gopay-gateway/gopay-gateway.php 92% from 13 tests
"GoPay for WooCommerce" version 1.0.4's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Requires at least: Required version must be the same as the one declared in readme.txt ("5.4" instead of "5.0")
Code Analysis 97% from 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
Good job! No executable or dangerous file extensions detected40,930 lines of code in 269 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 207 | 2,966 | 7,124 | 31,965 |
| Markdown | 19 | 1,308 | 0 | 3,990 |
| PO File | 12 | 2,920 | 0 | 3,217 |
| JSON | 13 | 0 | 0 | 1,392 |
| YAML | 7 | 23 | 4 | 127 |
| CSS | 3 | 26 | 12 | 124 |
| XML | 2 | 4 | 0 | 42 |
| make | 2 | 17 | 0 | 40 |
| Dockerfile | 2 | 11 | 0 | 16 |
| JavaScript | 1 | 4 | 20 | 14 |
| Bourne Shell | 1 | 2 | 0 | 3 |
PHP code 50% from 2 tests
An overview of cyclomatic complexity and code structure
These items need your attention
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 12.35 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 3.09 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 22 | |
| Interfaces | 19 | |
| Traits | 2 | |
| Classes | 145 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 145 | 100.00% |
| ▷ Final classes | 24 | 16.55% |
| Methods | 946 | |
| ▷ Static methods | 214 | 22.62% |
| ▷ Public methods | 774 | 81.82% |
| ▷ Protected methods | 21 | 2.22% |
| ▷ Private methods | 151 | 15.96% |
| Functions | 172 | |
| ▷ Named functions | 80 | 46.51% |
| ▷ Anonymous functions | 92 | 53.49% |
| Constants | 363 | |
| ▷ Global constants | 51 | 14.05% |
| ▷ Class constants | 312 | 85.95% |
| ▷ Public constants | 312 | 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
1 PNG file occupies 0.06MB with 0.06MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| includes/assets/images/gopay.png | 60.40KB | 3.38KB | ▼ 94.40% |