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: ▲0.38MB] [CPU: ▲0.90ms] Passed 4 tests
An overview of server-side resources used by NinjaTeam Chat for Telegram
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.92 ▲0.46 | 41.92 ▲2.46 |
Dashboard /wp-admin | 3.70 ▲0.40 | 52.41 ▲1.36 |
Posts /wp-admin/edit.php | 3.75 ▲0.39 | 59.46 ▲10.85 |
Add New Post /wp-admin/post-new.php | 6.28 ▲0.40 | 96.31 ▲1.39 |
Media Library /wp-admin/upload.php | 3.56 ▲0.33 | 36.62 ▼1.60 |
Settings /wp-admin/admin.php?page=nta_telegram_setting | 3.60 | 38.07 |
Add New account /wp-admin/post-new.php?post_type=telegram-accounts | 3.74 | 50.80 |
All Accounts /wp-admin/edit.php?post_type=telegram-accounts | 3.60 | 41.39 |
Floating Widget /wp-admin/admin.php?page=nta_telegram_floating_widget | 3.66 | 39.79 |
Server storage [IO: ▲0.40MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 58 new files
Database: no new tables, 9 new options
New WordPress options |
---|
db_upgraded |
njt_tele_version |
njt_tele_review |
widget_recent-posts |
can_compress_scripts |
njt_tele_first_time_active |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for NinjaTeam Chat for Telegram
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,966 ▲205 | 14.04 ▼0.35 | 9.29 ▲7.56 | 39.40 ▼4.84 |
Dashboard /wp-admin | 2,247 ▲44 | 5.88 ▲0.98 | 106.06 ▼7.62 | 73.93 ▲31.75 |
Posts /wp-admin/edit.php | 2,141 ▲44 | 1.97 ▼0.08 | 37.79 ▼1.79 | 36.17 ▲2.29 |
Add New Post /wp-admin/post-new.php | 6,229 ▲4,684 | 19.02 ▼4.44 | 949.64 ▲274.23 | 54.03 ▼1.90 |
Media Library /wp-admin/upload.php | 1,432 ▲35 | 4.17 ▼0.04 | 102.84 ▼16.40 | 69.08 ▲21.28 |
Settings /wp-admin/admin.php?page=nta_telegram_setting | 1,157 | 2.70 | 50.42 | 67.27 |
Add New account /wp-admin/post-new.php?post_type=telegram-accounts | 5,155 | 4.84 | 92.23 | 94.26 |
All Accounts /wp-admin/edit.php?post_type=telegram-accounts | 1,117 | 1.94 | 30.26 | 30.49 |
Floating Widget /wp-admin/admin.php?page=nta_telegram_floating_widget | 2,588 | 9.50 | 191.20 | 35.80 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 9 options in the database
- widget_theysaidso_widget
- njt_tele_first_time_active
- db_upgraded
- widget_recent-posts
- njt_tele_version
- widget_recent-comments
- njt_tele_review
- 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)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 10× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/woocommerce-button.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/design-settings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/display-settings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/meta-accounts.php:9
- > PHP Fatal error
Uncaught Error: Class 'NTA_Telegram\\Helper' not found in wp-content/plugins/ninjateam-telegram/views/selected-accounts.php:22
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_errors() in wp-content/plugins/ninjateam-telegram/views/floating-widget-settings.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/analytics.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_errors() in wp-content/plugins/ninjateam-telegram/views/settings.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/ninjateam-telegram/views/meta-button-style.php:4
- > PHP Fatal error
Uncaught Error: Class 'NTA_Telegram\\Helper' not found in wp-content/plugins/ninjateam-telegram/views/design-preview.php:36
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 96% 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
8 plugin tags: woocommerce telegram, join chat, click to chat, wp social chat, wp telegram...
ninjateam-telegram/telegram.php 92% from 13 tests
The main PHP file in "NinjaTeam Chat for Telegram" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("ninjateam-telegram.php" instead of "telegram.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin4,906 lines of code in 48 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 6 | 226 | 48 | 2,260 |
PHP | 24 | 275 | 49 | 2,190 |
PO File | 1 | 103 | 104 | 252 |
JavaScript | 8 | 4 | 13 | 164 |
XML | 1 | 0 | 0 | 21 |
SVG | 7 | 1 | 1 | 15 |
JSON | 1 | 0 | 0 | 4 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 11.75 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 25.00 |
Average method complexity | 2.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 12 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 12 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 100 | |
▷ Static methods | 32 | 32.00% |
▷ Public methods | 92 | 92.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 8.00% |
Functions | 8 | |
▷ Named functions | 4 | 50.00% |
▷ Anonymous functions | 4 | 50.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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
7 PNG files occupy 0.07MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/woo_settings/after_short_desc.png | 1.41KB | 1.42KB | 0.00% |
assets/img/woo_settings/after_long_desc.png | 1.44KB | 1.43KB | 0.20% |
assets/img/woo_settings/before_add_to_cart.png | 1.41KB | 1.42KB | 0.00% |
assets/img/FB_Wireframe.png | 10.56KB | 4.88KB | ▼ 53.83% |
assets/img/filebird-recommended.png | 20.96KB | 10.34KB | ▼ 50.67% |