Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.10ms] Passed 4 tests
Server-side resources used by Yandex Delivery
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 34.49 ▼5.32 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 43.84 ▼5.15 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.14 ▼4.44 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.87 ▼13.49 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 33.10 ▲0.96 |
Server storage [IO: ▲22.25MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 1,662 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Yandex Delivery
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲35 | 13.20 ▼1.20 | 1.61 ▼0.26 | 40.23 ▲0.45 |
| Dashboard /wp-admin | 2,212 ▲27 | 4.87 ▼0.99 | 106.96 ▲4.93 | 44.63 ▲8.03 |
| Posts /wp-admin/edit.php | 2,094 ▲5 | 2.04 ▲0.02 | 40.11 ▲2.50 | 35.68 ▲1.47 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲34 | 18.25 ▲0.64 | 592.17 ▼68.88 | 53.74 ▼3.98 |
| Media Library /wp-admin/upload.php | 1,394 ▲3 | 4.20 ▼0.06 | 96.77 ▼9.54 | 39.66 ▼6.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% 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 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
- 13× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'libphonenumber\\Leniency\\AbstractLeniency' not found in wp-content/plugins/yandex-go-delivery/core/vendor/giggsey/libphonenumber-for-php/src/Leniency/ExactGrouping.php:9
- > PHP Fatal error
Uncaught Error: Interface 'libphonenumber\\MetadataLoaderInterface' not found in wp-content/plugins/yandex-go-delivery/core/vendor/giggsey/libphonenumber-for-php/src/DefaultMetadataLoader.php:5
- > PHP Fatal error
Uncaught Error: Interface 'libphonenumber\\MatcherAPIInterface' not found in wp-content/plugins/yandex-go-delivery/core/vendor/giggsey/libphonenumber-for-php/src/RegexBasedMatcher.php:10
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/plugin.php' (include_path='.:/usr/share/php') in wp-content/plugins/yandex-go-delivery/yandex-go-delivery.php on line 16
- > PHP Warning
require_once(ABSPATHwp-admin/includes/plugin.php): failed to open stream: No such file or directory in wp-content/plugins/yandex-go-delivery/yandex-go-delivery.php on line 16
- > PHP Fatal error
Uncaught Error: Class 'libphonenumber\\Leniency\\AbstractLeniency' not found in wp-content/plugins/yandex-go-delivery/core/vendor/giggsey/libphonenumber-for-php/src/Leniency/Possible.php:8
- > PHP Fatal error
Uncaught Error: Class 'libphonenumber\\Leniency\\AbstractLeniency' not found in wp-content/plugins/yandex-go-delivery/core/vendor/giggsey/libphonenumber-for-php/src/Leniency/Valid.php:9
- > PHP Fatal error
Uncaught Error: Interface 'YandexTaxi\\Delivery\\Http\\Client' not found in wp-content/plugins/yandex-go-delivery/lib/Http/WpHttpClient.php:13
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/yandex-go-delivery/yandex-go-delivery.php on line 16
- > PHP Fatal error
Uncaught Error: Class 'WC_Yandex_Taxi_Admin_Menu' not found in wp-content/plugins/yandex-go-delivery/includes/views/tabs.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: shipping, shipment, delivery, shipping method, woocommerce shipping
yandex-go-delivery/yandex-go-delivery.php 85% from 13 tests
The main file in "Yandex Delivery" v. 1.11.5 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("5.4.1" instead of "5.0")
- Description: Please keep the plugin description shorter than 140 characters (currently 157 characters long)
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
Everything looks great! No dangerous files found in this plugin602,374 lines of code in 1,511 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1,480 | 5,171 | 18,317 | 597,093 |
| PO File | 5 | 909 | 1,209 | 2,220 |
| JavaScript | 12 | 257 | 60 | 1,582 |
| CSS | 3 | 118 | 156 | 832 |
| JSON | 4 | 1 | 0 | 336 |
| Markdown | 3 | 86 | 0 | 206 |
| Ant | 1 | 12 | 0 | 55 |
| YAML | 2 | 9 | 1 | 35 |
| XML | 1 | 3 | 0 | 15 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 11.81 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 366.00 |
| Average method complexity | 2.45 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 32.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 39 | |
| Interfaces | 7 | |
| Traits | 0 | |
| Classes | 141 | |
| ▷ Abstract classes | 6 | 4.26% |
| ▷ Concrete classes | 135 | 95.74% |
| ▷ Final classes | 13 | 9.63% |
| Methods | 1,105 | |
| ▷ Static methods | 241 | 21.81% |
| ▷ Public methods | 838 | 75.84% |
| ▷ Protected methods | 88 | 7.96% |
| ▷ Private methods | 179 | 16.20% |
| Functions | 70 | |
| ▷ Named functions | 44 | 62.86% |
| ▷ Anonymous functions | 26 | 37.14% |
| Constants | 197 | |
| ▷ Global constants | 10 | 5.08% |
| ▷ Class constants | 187 | 94.92% |
| ▷ Public constants | 124 | 66.31% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.23MB with 0.12MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/lib/intlTelInput/img/flags@2x.png | 170.28KB | 68.04KB | ▼ 60.04% |
| assets/lib/intlTelInput/img/flags.png | 69.20KB | 23.42KB | ▼ 66.16% |
| assets/favicon_he_IL.png | 0.32KB | 0.25KB | ▼ 22.96% |