Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.13MB] [CPU: ▼4.92ms] Passed 4 tests
Analyzing server-side resources used by Contact for Telegram
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.05 | 38.72 ▲2.77 |
| Dashboard /wp-admin | 3.24 ▼0.07 | 32.36 ▼15.61 |
| Posts /wp-admin/edit.php | 3.30 ▼0.06 | 41.28 ▼0.40 |
| Add New Post /wp-admin/post-new.php | 5.48 ▼0.41 | 84.77 ▼6.43 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.20 ▲5.78 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 29 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
This is an overview of browser requirements for Contact for Telegram
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,838 ▲92 | 13.37 ▼0.59 | 1.64 ▲0.11 | 45.05 ▲5.78 |
| Dashboard /wp-admin | 2,227 ▲41 | 5.03 ▼0.90 | 143.39 ▲21.27 | 86.77 ▲40.03 |
| Posts /wp-admin/edit.php | 2,130 ▲41 | 2.28 ▲0.27 | 43.79 ▲3.02 | 38.81 ▲8.14 |
| Add New Post /wp-admin/post-new.php | 1,702 ▲160 | 22.77 ▲4.55 | 763.70 ▲130.19 | 47.33 ▼4.29 |
| Media Library /wp-admin/upload.php | 1,424 ▲39 | 4.34 ▲0.12 | 121.91 ▲19.59 | 49.12 ▲3.88 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/contact-for-telegram/contact-for-telegram.php
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/contact-for-telegram/Front/views/telegram.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/contact-for-telegram/Admin/views/config.php:4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 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
These attributes need to be fixed:
- Donate link: Invalid URI ("www.paypal.me/tupaginawebdesdecero")
contact-for-telegram/contact-for-telegram.php Passed 13 tests
The main file in "Contact for Telegram" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
80 characters long description:
Boton sencillo personalizable para enlace directo a usuario o canal de telegram.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected388 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 96 | 95 | 331 |
| JavaScript | 2 | 25 | 4 | 45 |
| CSS | 2 | 1 | 0 | 12 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 1.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 1.08 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 19 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 19 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.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
6 compressed PNG files occupy 0.01MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| Front/img/telegram_3.png | 1.49KB | 1.40KB | ▼ 6.08% |
| Front/img/telegram_2.png | 2.29KB | 2.22KB | ▼ 2.99% |
| Front/img/telegram_icon.png | 0.83KB | 0.78KB | ▼ 6.34% |
| Front/img/telegram_4.png | 1.50KB | 1.42KB | ▼ 5.41% |
| Admin/img/telegram_icon_menu.png | 0.45KB | 0.43KB | ▼ 5.21% |