Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.21ms] Passed 4 tests
An overview of server-side resources used by Delivengo: Shipping methods for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.73 ▼0.89 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 49.19 ▼6.76 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.52 ▲0.96 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 92.69 ▼6.87 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.73 ▼2.31 |
Server storage [IO: ▲2.88MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 234 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Delivengo: Shipping methods for WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,790 ▲28 | 14.26 ▼0.45 | 1.85 ▲0.15 | 46.77 ▲3.54 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.60 ▲0.05 | 86.18 ▼9.04 | 37.08 ▼8.03 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 1.98 ▲0.04 | 40.16 ▼0.83 | 34.59 ▼6.93 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.31 ▲0.42 | 676.14 ▲49.75 | 56.58 ▲1.93 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.20 ▲0.05 | 96.81 ▼8.26 | 40.95 ▼2.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
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/delivengo/delivengo.php
- > /wp-content/plugins/delivengo/vendor/tecnickcom/tcpdf/tools/tcpdf_addfont.php
- 103× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Delivengo\\Classes\\Shipping\\ShippingMethod' not found in wp-content/plugins/delivengo/src/Classes/Shipping/ShippingMethodTracked.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/delivengo/src/Partials/Orders/Tracking.php:3
- > PHP Fatal error
require_once(): Failed opening required '../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/delivengo/vendor/setasign/fpdi/local-tests/simple-v1.php on line 6
- > PHP Warning
require_once(../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/delivengo/vendor/setasign/fpdi/local-tests/memory.php on line 9
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\Tcpdf\\Fpdi' not found in wp-content/plugins/delivengo/vendor/setasign/fpdi/src/TcpdfFpdi.php:20
- > PHP Notice
Undefined variable: data in wp-content/plugins/delivengo/src/Partials/ShippingMethods/RatesTable.php on line 4
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\CrossReference\\AbstractReader' not found in wp-content/plugins/delivengo/vendor/setasign/fpdi/src/PdfParser/CrossReference/LineReader.php:22
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Type\\PdfType' not found in wp-content/plugins/delivengo/vendor/setasign/fpdi/src/PdfParser/Type/PdfHexString.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/delivengo/src/Partials/Settings/Logs.php:2
- > PHP Fatal error
Uncaught Error: Class 'Delivengo\\Services\\Api\\Api' not found in wp-content/plugins/delivengo/src/Services/Api/ApiEasy.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 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
3 plugin tags: delivengo, shipping, woocommerce
delivengo/delivengo.php 85% from 13 tests
"Delivengo: Shipping methods for WooCommerce" version 1.1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Requires PHP: Required version must be the same as the one declared in readme.txt ("7.4.0" instead of "7.4")
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
Code Analysis 95% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin61,343 lines of code in 216 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 177 | 3,859 | 14,881 | 58,029 |
| PO File | 2 | 616 | 0 | 1,236 |
| JSON | 12 | 0 | 0 | 847 |
| JavaScript | 9 | 111 | 2 | 601 |
| CSS | 9 | 50 | 0 | 230 |
| Markdown | 3 | 49 | 0 | 171 |
| Bourne Shell | 1 | 22 | 13 | 163 |
| XML | 2 | 5 | 2 | 40 |
| SQL | 1 | 1 | 0 | 26 |
PHP code 0% from 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Please tend to the following items
- Class cyclomatic complexity should be reduced to less than 1000 (currently 4,415)
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 500)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 63.89 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 4,415.00 |
| Average method complexity | 7.32 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 500.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 27 | |
| Interfaces | 2 | |
| Traits | 2 | |
| Classes | 119 | |
| ▷ Abstract classes | 3 | 2.52% |
| ▷ Concrete classes | 116 | 97.48% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 1,228 | |
| ▷ Static methods | 198 | 16.12% |
| ▷ Public methods | 853 | 69.46% |
| ▷ Protected methods | 332 | 27.04% |
| ▷ Private methods | 43 | 3.50% |
| Functions | 36 | |
| ▷ Named functions | 5 | 13.89% |
| ▷ Anonymous functions | 31 | 86.11% |
| Constants | 237 | |
| ▷ Global constants | 114 | 48.10% |
| ▷ Class constants | 123 | 51.90% |
| ▷ Public constants | 123 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/logo_laposte.png | 8.27KB | 2.35KB | ▼ 71.60% |
| assets/images/logo.png | 3.66KB | 3.70KB | 0.00% |