Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼290.59ms] Passed 4 tests
Analyzing server-side resources used by Send Form Entries To Telegram
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.66 ▲0.14 | 53.23 ▲7.32 |
| Dashboard /wp-admin | 3.49 ▲0.08 | 34.21 ▼4.09 |
| Posts /wp-admin/edit.php | 3.71 ▲0.07 | 37.57 ▼0.41 |
| Add New Post /wp-admin/post-new.php | 6.95 ▼0.02 | 90.74 ▼1,156.80 |
| Media Library /wp-admin/upload.php | 3.36 ▲0.07 | 24.85 ▼1.04 |
Server storage [IO: ▲3.68MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 1,475 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Send Form Entries To Telegram
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,776 ▲19 | 15.66 ▼0.30 | 5.85 ▲0.06 | 2.25 ▼0.27 |
| Dashboard /wp-admin | 2,905 ▲44 | 6.13 ▼0.03 | 118.98 ▼17.36 | 156.51 ▼8.99 |
| Posts /wp-admin/edit.php | 2,702 ▲14 | 3.24 ▲0.01 | 62.60 ▼6.14 | 140.80 ▼6.67 |
| Add New Post /wp-admin/post-new.php | 1,780 ▲70 | 21.13 ▼0.27 | 460.74 ▼4.19 | 157.51 ▲6.19 |
| Media Library /wp-admin/upload.php | 1,708 ▲10 | 5.53 ▼0.01 | 144.63 ▲9.94 | 189.55 ▲5.94 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The plugin uninstalled completely, with no zombie files or tables
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 | 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 task of outputting text when accessed with GET requests:
- > /wp-content/plugins/send-form-entries-to-telegram/include/vendor/symfony/translation/Resources/bin/translation-status.php
- 254× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Update.php:35
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/ChatPermissions.php:17
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\Passport\\PassportElementError' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Passport/PassportElementErrorDataField.php:16
- > PHP Fatal error
Trait 'Carbon\\Traits\\Cast' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/nesbot/carbon/src/Carbon/Traits/Mutability.php on line 21
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Passport/EncryptedPassportElement.php:21
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Exceptions\\TelegramSDKException' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Exceptions/CouldNotUploadInputFile.php:8
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Passport/IdDocumentData.php:13
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/VideoNote.php:15
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Venue.php:15
- > PHP Fatal error
Uncaught Error: Class 'Telegram\\Bot\\Objects\\BaseObject' not found in wp-content/plugins/send-form-entries-to-telegram/include/vendor/irazasyed/telegram-bot-sdk/src/Objects/Contact.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
2 plugin tags: gravityforms, telegram
send-form-entries-to-telegram/gravityforms-telegram.php 85% from 13 tests
The main PHP file in "Send Form Entries To Telegram" ver. 1.1.0 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("send-form-entries-to-telegram.php" instead of "gravityforms-telegram.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis 3% from 3 tests
File types 0% from 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Almost there! Just fix the following issues
- Do not include executable or dangerous files in your plugin
- .bat - Batch File in Windows
- ☣ wp-content/plugins/send-form-entries-to-telegram/include/vendor/bin/carbon.bat
- ☣ wp-content/plugins/send-form-entries-to-telegram/include/vendor/nesbot/carbon/bin/carbon.bat
- .bat - Batch File in Windows
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1,202 | 7,802 | 31,513 | 45,657 |
| JSON | 18 | 0 | 0 | 3,140 |
| XSD | 3 | 92 | 48 | 2,803 |
| Markdown | 19 | 330 | 0 | 780 |
| PO File | 1 | 33 | 37 | 97 |
| reStructuredText | 1 | 74 | 78 | 74 |
| YAML | 3 | 12 | 1 | 72 |
| XML | 1 | 0 | 0 | 45 |
| CSS | 1 | 0 | 0 | 20 |
| Bourne Shell | 1 | 3 | 1 | 10 |
| DOS Batch | 2 | 0 | 0 | 8 |
| JavaScript | 1 | 0 | 1 | 0 |
PHP code 50% from 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
These items need your attention
- Method cyclomatic complexity should be reduced to less than 100 (currently 139)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 8.03 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 295.00 |
| Average method complexity | 2.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 139.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 58 | |
| Interfaces | 44 | |
| Traits | 46 | |
| Classes | 287 | |
| ▷ Abstract classes | 11 | 3.83% |
| ▷ Concrete classes | 276 | 96.17% |
| ▷ Final classes | 27 | 9.78% |
| Methods | 2,101 | |
| ▷ Static methods | 424 | 20.18% |
| ▷ Public methods | 1,811 | 86.20% |
| ▷ Protected methods | 175 | 8.33% |
| ▷ Private methods | 115 | 5.47% |
| Functions | 303 | |
| ▷ Named functions | 63 | 20.79% |
| ▷ Anonymous functions | 240 | 79.21% |
| Constants | 203 | |
| ▷ Global constants | 46 | 22.66% |
| ▷ Class constants | 157 | 77.34% |
| ▷ Public constants | 156 | 99.36% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected