Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼0.68ms] Passed 4 tests
Server-side resources used by Smartarget Telegram - Contact Us
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 46.11 ▲1.04 |
Dashboard /wp-admin | 3.37 ▲0.07 | 49.43 ▼0.31 |
Posts /wp-admin/edit.php | 3.48 ▲0.13 | 51.30 ▲3.60 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 88.67 ▼7.06 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 41.19 ▲5.91 |
Smartarget Telegram - Contact Us /wp-admin/options-general.php?page=smartarget_telegram | 3.26 | 32.56 |
Server storage [IO: ▲1.91MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
Smartarget Telegram - Contact Us: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,921 ▲135 | 21.33 ▲6.97 | 10.52 ▲8.29 | 43.42 ▼0.96 |
Dashboard /wp-admin | 2,205 ▲28 | 10.62 ▲5.09 | 176.88 ▲81.00 | 39.51 ▼1.47 |
Posts /wp-admin/edit.php | 2,119 ▲19 | 7.25 ▲5.23 | 123.24 ▲87.16 | 35.72 ▼2.09 |
Add New Post /wp-admin/post-new.php | 1,694 ▲168 | 27.32 ▲3.52 | 709.75 ▲23.89 | 62.59 ▼5.72 |
Media Library /wp-admin/upload.php | 1,407 ▲7 | 9.69 ▲5.51 | 190.22 ▲93.31 | 47.57 ▲5.31 |
Smartarget Telegram - Contact Us /wp-admin/options-general.php?page=smartarget_telegram | 2,383 | 11.92 | 229.63 | 133.51 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.31MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 50% 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)
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
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/smartarget-telegram-contact-us/public/partials/smartarget-telegram-public-display.php
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_home_url() in wp-content/plugins/smartarget-telegram-contact-us/admin/partials/smartarget-telegram-admin-display.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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
7 plugin tags: telegram, telegram bot, telegram group, telegram channel, telegram messages...
smartarget-telegram-contact-us/smartarget-telegram.php 85% from 13 tests
The main file in "Smartarget Telegram - Contact Us" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("smartarget-telegram-contact-us.php" instead of "smartarget-telegram.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
Success! There were no dangerous files found in this plugin430 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 130 | 522 | 225 |
JavaScript | 3 | 5 | 1,397 | 205 |
CSS | 1 | 0 | 4 | 0 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.10 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 28 | |
▷ Static methods | 2 | 7.14% |
▷ Public methods | 23 | 82.14% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 17.86% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 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
PNG images were not found in this plugin