Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.09MB] [CPU: ▼0.96ms] Passed 4 tests
A check of server-side resources used by TalkM Chat Widget
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 40.35 ▲0.10 |
Dashboard /wp-admin | 3.39 ▲0.09 | 48.53 ▼2.29 |
Posts /wp-admin/edit.php | 3.50 ▲0.15 | 49.13 ▼0.24 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 97.63 ▲1.34 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 36.71 ▼1.41 |
TalkM /wp-admin/options-general.php?page=talkm_plugin | 3.30 | 34.00 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 13 new options
New WordPress options |
---|
db_upgraded |
talkm-embed-widget-company-id |
talkm-embed-widget-username-id |
widget_recent-posts |
talkm-embed-widget-expire-id |
widget_recent-comments |
talkm-embed-widget-password-id |
can_compress_scripts |
talkm-visibility-options |
theysaidso_admin_options |
... |
Browser metrics Passed 4 tests
An overview of browser requirements for TalkM Chat Widget
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,819 ▲58 | 14.45 ▼0.11 | 1.84 ▲0.03 | 41.14 ▼3.89 |
Dashboard /wp-admin | 2,225 ▲19 | 5.87 ▲0.97 | 112.60 ▲7.88 | 42.03 ▲2.44 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.03 ▲0.00 | 40.19 ▲0.82 | 37.40 ▼1.70 |
Add New Post /wp-admin/post-new.php | 1,549 ▲9 | 23.43 ▲0.26 | 624.96 ▼71.93 | 59.32 ▼6.58 |
Media Library /wp-admin/upload.php | 1,404 ▲10 | 4.24 ▼0.03 | 98.70 ▼0.40 | 44.99 ▼1.35 |
TalkM /wp-admin/options-general.php?page=talkm_plugin | 948 | 1.88 | 24.82 | 28.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/talkm-chat-widget/talkm.php:465
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Donate link: Invalid url: ""
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
- Screenshots: Add descriptions for screenshots #4, #5 in talkm-chat-widget/assets to your readme.txt
talkm-chat-widget/talkm.php 85% from 13 tests
"TalkM Chat Widget" version 1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("talkm-chat-widget.php" instead of "talkm.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 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected755 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 106 | 58 | 478 |
CSS | 1 | 10 | 0 | 223 |
JavaScript | 1 | 3 | 5 | 54 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 18.00 |
▷ Minimum class complexity | 17.00 |
▷ Maximum class complexity | 19.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 17 | |
▷ Static methods | 2 | 11.76% |
▷ Public methods | 17 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 7 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 7 | 100.00% |
▷ Public constants | 7 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin