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.19MB] [CPU: ▼4.92ms] Passed 4 tests
Analyzing server-side resources used by Brenger for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.68 ▲0.21 | 37.88 ▲0.66 |
| Dashboard /wp-admin | 3.54 ▲0.23 | 46.38 ▼1.49 |
| Posts /wp-admin/edit.php | 3.59 ▲0.23 | 51.48 ▲1.40 |
| Add New Post /wp-admin/post-new.php | 6.06 ▲0.17 | 86.05 ▼20.26 |
| Media Library /wp-admin/upload.php | 3.40 ▲0.17 | 37.76 ▲1.70 |
Server storage [IO: ▲5.09MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 253 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Brenger for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 13.18 ▼1.61 | 1.81 ▲0.13 | 40.79 ▼4.63 |
| Dashboard /wp-admin | 2,207 ▲19 | 4.85 ▼0.08 | 108.45 ▼10.66 | 50.75 ▲10.67 |
| Posts /wp-admin/edit.php | 2,095 ▲3 | 2.05 ▲0.04 | 41.01 ▼1.09 | 37.04 ▼0.04 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲18 | 23.31 ▲0.28 | 636.24 ▲12.76 | 52.50 ▲1.88 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.25 ▲0.06 | 101.92 ▼1.21 | 43.44 ▼2.72 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
Please fix the following items
- 77× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/brenger-for-woocommerce/vendor/guzzlehttp/psr7/src/CachingStream.php:13
- > PHP Fatal error
Uncaught Error: Class 'WP_List_Table' not found in wp-content/plugins/brenger-for-woocommerce/src/Orders/OrderItemsWithOptions.php:15
- > PHP Fatal error
Uncaught Error: Interface 'BrengerClient\\Model\\ModelInterface' not found in wp-content/plugins/brenger-for-woocommerce/vendor/level-level/brenger-client/lib/Model/CreatedShipmentAllOf.php:46
- > PHP Parse error
syntax error, unexpected '|', expecting '{' in wp-content/plugins/brenger-for-woocommerce/vendor/symfony/polyfill-intl-idn/bootstrap80.php on line 121
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/brenger-for-woocommerce/vendor/level-level/brenger-client/test/Model/ItemSetPartTest.php:43
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/brenger-for-woocommerce/vendor/level-level/brenger-client/test/Model/CreatedShipmentAllOfTest.php:43
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/brenger-for-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/TransferException.php:4
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/brenger-for-woocommerce/vendor/guzzlehttp/guzzle/src/Cookie/SessionCookieJar.php:7
- > PHP Fatal error
Uncaught Error: Interface 'BrengerClient\\Model\\ModelInterface' not found in wp-content/plugins/brenger-for-woocommerce/vendor/level-level/brenger-client/lib/Model/Address.php:46
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/brenger-for-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/InvalidArgumentException.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Add images for these screenshots: #1 (The plugin adds 2 custom actions to your Order detail page), #2 (Customize the order details), #3 (Shipment status is automatically tracked)
brenger-for-woocommerce/brenger-for-woocommerce.php Passed 13 tests
The principal PHP file in "Brenger for WooCommerce" v. 1.0.0 is loaded by WordPress automatically on each request
49 characters long description:
Adds Brenger as a shipping plugin to WooCommerce.
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected37,879 lines of code in 234 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 186 | 3,701 | 11,203 | 32,898 |
| Markdown | 28 | 1,246 | 0 | 3,708 |
| JSON | 10 | 0 | 0 | 1,096 |
| YAML | 6 | 22 | 5 | 99 |
| Bourne Shell | 1 | 14 | 8 | 36 |
| XML | 1 | 0 | 0 | 23 |
| Dockerfile | 1 | 8 | 0 | 10 |
| make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
An overview of cyclomatic complexity and code structure
The following items need your attention
- Please reduce cyclomatic complexity of methods to less than 100 (currently 179)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 13.99 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 2.43 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 179.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 27 | |
| Interfaces | 16 | |
| Traits | 2 | |
| Classes | 134 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 134 | 100.00% |
| ▷ Final classes | 23 | 17.16% |
| Methods | 1,367 | |
| ▷ Static methods | 278 | 20.34% |
| ▷ Public methods | 1,193 | 87.27% |
| ▷ Protected methods | 6 | 0.44% |
| ▷ Private methods | 168 | 12.29% |
| Functions | 177 | |
| ▷ Named functions | 76 | 42.94% |
| ▷ Anonymous functions | 101 | 57.06% |
| Constants | 215 | |
| ▷ Global constants | 78 | 36.28% |
| ▷ Class constants | 137 | 63.72% |
| ▷ Public constants | 137 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 3.59MB with 2.70MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 1,468.72KB | 386.02KB | ▼ 73.72% |
| assets/screenshot-3.png | 1,309.45KB | 310.43KB | ▼ 76.29% |
| assets/screenshot-2.png | 894.92KB | 216.07KB | ▼ 75.86% |