Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.08MB] [CPU: ▼2.11ms] Passed 4 tests
A check of server-side resources used by WordPress Live Chat Plugin - Olark
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 37.57 ▼10.22 |
| Dashboard /wp-admin | 3.38 ▲0.07 | 48.72 ▲0.95 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 81.16 ▲32.07 |
| Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 95.07 ▲0.11 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 35.52 ▲0.71 |
| Olark Settings /wp-admin/options-general.php?page=olark-wp | 3.31 | 39.84 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WordPress Live Chat Plugin - Olark
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲64 | 13.19 ▼1.19 | 1.74 ▼0.21 | 40.18 ▼3.96 |
| Dashboard /wp-admin | 2,217 ▲29 | 5.85 ▼0.03 | 96.76 ▼21.83 | 38.42 ▼6.29 |
| Posts /wp-admin/edit.php | 2,100 ▲11 | 2.00 ▼0.02 | 40.38 ▲1.61 | 35.76 ▲3.91 |
| Add New Post /wp-admin/post-new.php | 1,521 ▲2 | 23.67 ▲0.53 | 675.33 ▼8.01 | 50.60 ▲3.93 |
| Media Library /wp-admin/upload.php | 1,399 ▲14 | 4.21 ▼0.01 | 97.11 ▼7.93 | 43.83 ▼0.96 |
| Olark Settings /wp-admin/options-general.php?page=olark-wp | 952 | 2.03 | 23.12 | 39.13 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- 8 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=olark-wp
- > Notice in wp-content/plugins/olark-live-chat/admin/partials/olark-wp-admin-display.php+37
Trying to access array offset on value of type bool
SRP 0% 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 perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/olark-live-chat/public/partials/olark-wp-public-display.php
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/olark-live-chat/admin/partials/olark-wp-admin-display.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
9 plugin tags: chat plugin, chatbox, live chat, wordpress live chat, accessible chatbot...
olark-live-chat/olark-wp.php 77% from 13 tests
The entry point to "WordPress Live Chat Plugin - Olark" version 1.0.9 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("olark-live-chat.php" instead of "olark-wp.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Description: Please don't use more than 140 characters for the plugin description (currently 156 characters long)
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
Good job! No executable or dangerous file extensions detected412 lines of code in 17 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 12 | 156 | 541 | 337 |
| JavaScript | 3 | 4 | 34 | 75 |
| CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 3.86 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 1.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.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 | 29 | |
| ▷ Static methods | 2 | 6.90% |
| ▷ Public methods | 23 | 79.31% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 20.69% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected