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: ▲2.68MB] [CPU: ▲19.86ms] Passed 4 tests
Analyzing server-side resources used by Bot for Telegram on WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 32.36 ▼5.04 |
| Dashboard /wp-admin | 6.95 ▲3.65 | 82.02 ▲37.93 |
| Posts /wp-admin/edit.php | 7.03 ▲3.67 | 92.71 ▲48.05 |
| Add New Post /wp-admin/post-new.php | 9.17 ▲3.29 | 119.48 ▲21.63 |
| Media Library /wp-admin/upload.php | 6.94 ▲3.71 | 62.54 ▲24.90 |
Server storage [IO: ▲11.23MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 284 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| bftow_patch_settings |
| theysaidso_admin_options |
| bftow_settings |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Bot for Telegram on WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,281 ▲546 | 19.34 ▲4.97 | 1.63 ▼0.12 | 38.63 ▼4.75 |
| Dashboard /wp-admin | 2,670 ▲496 | 10.36 ▲4.36 | 203.57 ▲96.61 | 163.82 ▲122.36 |
| Posts /wp-admin/edit.php | 2,556 ▲467 | 7.56 ▲5.52 | 127.26 ▲92.12 | 109.38 ▲76.29 |
| Add New Post /wp-admin/post-new.php | 1,932 ▲390 | 20.58 ▲2.40 | 680.78 ▲10.32 | 213.71 ▲152.33 |
| Media Library /wp-admin/upload.php | 1,755 ▲367 | 7.82 ▲3.60 | 144.83 ▲32.99 | 126.82 ▲78.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin did not uninstall successfully, leaving 8 options in the database
- can_compress_scripts
- widget_recent-posts
- bftow_settings
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- bftow_patch_settings
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/not_exist.php
- 123× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/NUXY.php:17
- > PHP Notice
Undefined variable: section_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/notice.php on line 12
- > PHP Notice
Undefined variable: field_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/button_group.php on line 13
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/bot-for-telegram-on-woocommerce/includes/notices/settings.php:20
- > PHP Notice
Undefined variable: field_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/image_select.php on line 13
- > PHP Notice
Undefined variable: field_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/typography.php on line 14
- > PHP Notice
Undefined variable: field_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/ace_editor.php on line 13
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/range_slider.php:18
- > PHP Notice
Undefined variable: section_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/hint.php on line 8
- > PHP Notice
Undefined variable: field_name in wp-content/plugins/bot-for-telegram-on-woocommerce/nuxy/metaboxes/fields/import_export.php on line 13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4, #5, #6, #7 in bot-for-telegram-on-woocommerce/assets to your readme.txt
bot-for-telegram-on-woocommerce/bot-for-telegram-on-woocommerce.php Passed 13 tests
"Bot for Telegram on WooCommerce" version 1.2.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
133 characters long description:
Bot for Telegram on WooCommerce is a plugin that allows you to create a telegram online store based on your website with WooCommerce.
Code Analysis Passed 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
No dangerous file extensions were detected143,531 lines of code in 246 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 5 | 0 | 0 | 76,788 |
| JavaScript | 88 | 5,055 | 1,694 | 38,382 |
| SVG | 8 | 0 | 12 | 9,175 |
| CSS | 11 | 1,466 | 9 | 7,860 |
| PHP | 75 | 1,092 | 433 | 5,416 |
| Sass | 54 | 392 | 108 | 4,930 |
| PO File | 3 | 414 | 447 | 955 |
| Markdown | 2 | 10 | 0 | 25 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 24.28 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 133.00 |
| Average method complexity | 3.60 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 58.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 18 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 18 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 160 | |
| ▷ Static methods | 38 | 23.75% |
| ▷ Public methods | 137 | 85.62% |
| ▷ Protected methods | 2 | 1.25% |
| ▷ Private methods | 21 | 13.12% |
| Functions | 51 | |
| ▷ Named functions | 36 | 70.59% |
| ▷ Anonymous functions | 15 | 29.41% |
| Constants | 9 | |
| ▷ Global constants | 9 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.04MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/icon.png | 39.41KB | 14.70KB | ▼ 62.69% |