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.39MB] [CPU: ▼18.02ms] Passed 4 tests
An overview of server-side resources used by ChatBot for Telegram
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.73 ▲0.26 | 43.02 ▲2.53 |
Dashboard /wp-admin | 3.65 ▲0.31 | 48.96 ▼15.36 |
Posts /wp-admin/edit.php | 3.70 ▲0.35 | 54.63 ▲1.64 |
Add New Post /wp-admin/post-new.php | 3.47 ▼2.42 | 41.87 ▼60.88 |
Media Library /wp-admin/upload.php | 3.51 ▲0.28 | 38.00 ▲4.77 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for ChatBot for Telegram
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,812 ▲51 | 14.23 ▲0.13 | 1.92 ▲0.31 | 39.09 ▼1.63 |
Dashboard /wp-admin | 2,215 ▲38 | 5.56 ▼0.12 | 91.91 ▼0.32 | 44.77 ▼1.15 |
Posts /wp-admin/edit.php | 2,124 ▲24 | 1.99 ▼0.04 | 40.34 ▼1.32 | 37.29 ▲1.39 |
Add New Post /wp-admin/post-new.php | 1,547 ▲19 | 23.41 ▲0.44 | 661.60 ▲20.94 | 72.13 ▲16.60 |
Media Library /wp-admin/upload.php | 1,423 ▲29 | 4.21 ▲0.00 | 97.60 ▼1.24 | 43.66 ▲1.02 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
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)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
Please fix the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/chatbot-for-telegram/includes/admin/menu.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/chatbot-for-telegram/includes/class-webhook.php:30
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/chatbot-for-telegram/includes/admin/templates/settings.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 86% 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: telegram chatbot, chatbot, bot telegram, telegram bot, telegram
chatbot-for-telegram/init.php 69% from 13 tests
Analyzing the main PHP file in "ChatBot for Telegram" version 0.9.8
Please take the time to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Domain Path: The domain path points to an invalid folder, "/languages" does not exist
- Requires at least: Required version must match the one declared in readme.txt ("4.9" instead of "4.6")
- Main file name: The principal plugin file should be the same as the plugin slug ("chatbot-for-telegram.php" instead of "init.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected1,539 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 489 | 391 | 1,539 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 17.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 65.00 |
Average method complexity | 3.57 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 39.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 1 | 12.50% |
Methods | 47 | |
▷ Static methods | 1 | 2.13% |
▷ Public methods | 42 | 89.36% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 10.64% |
Functions | 27 | |
▷ Named functions | 25 | 92.59% |
▷ Anonymous functions | 2 | 7.41% |
Constants | 6 | |
▷ Global constants | 4 | 66.67% |
▷ Class constants | 2 | 33.33% |
▷ Public constants | 2 | 100.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
PNG images were not found in this plugin