Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲1.00MB] [CPU: ▼133.60ms] Passed 4 tests
A check of server-side resources used by Helpdesk Support Tickets Plugin for WordPress
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.86 ▲1.14 | 43.58 ▲18.59 |
Dashboard /wp-admin | 4.09 ▲1.03 | 51.17 ▲5.12 |
Posts /wp-admin/edit.php | 4.14 ▲1.03 | 51.37 ▲6.29 |
Add New Post /wp-admin/post-new.php | 6.38 ▲0.95 | 98.43 ▼553.95 |
Media Library /wp-admin/upload.php | 3.97 ▲0.97 | 41.79 ▲8.13 |
Server storage [IO: ▲3.39MB] [DB: ▲0.01MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 116 new files
Database: 6 new tables, 5 new options
New tables |
---|
wp_hst_tickets_statuses |
wp_hst_tickets_priorities |
wp_hst_tickets_categories |
wp_hst_attachments |
wp_hst_tickets |
wp_hst_tickets_events |
New WordPress options |
---|
hstDefaultStatusesInstalled |
hstDatabaseVersion |
hstDefaultPrioritiesInstalled |
hstDefaultCategoriesInstalled |
hstDefaultStatusLabelsInstalled |
Browser metrics Passed 4 tests
Helpdesk Support Tickets Plugin for WordPress: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,717 ▲121 | 15.93 ▲0.05 | 9.53 ▲0.62 | 45.41 ▼3.66 |
Dashboard /wp-admin | 2,977 ▲46 | 5.87 ▼0.04 | 131.31 ▼14.84 | 142.16 ▲28.55 |
Posts /wp-admin/edit.php | 2,768 ▲29 | 2.69 ▲0.01 | 70.10 ▲2.73 | 85.64 ▼5.53 |
Add New Post /wp-admin/post-new.php | 1,682 ▲12 | 18.91 ▼0.29 | 382.95 ▲9.33 | 104.00 ▼4.96 |
Media Library /wp-admin/upload.php | 1,759 ▼51 | 4.98 ▼0.03 | 127.69 ▼8.44 | 136.90 ▲21.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie tables detected upon uninstall: 6 tables
- wp_hst_tickets
- wp_hst_tickets_categories
- wp_hst_tickets_events
- wp_hst_attachments
- wp_hst_tickets_priorities
- wp_hst_tickets_statuses
- Zombie WordPress options detected upon uninstall: 5 options
- hstDefaultCategoriesInstalled
- hstDefaultPrioritiesInstalled
- hstDatabaseVersion
- hstDefaultStatusesInstalled
- hstDefaultStatusLabelsInstalled
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
The following issues need your attention
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/helpdesk-support-tickets/pages/dashboard.php
- 26× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/frontend/mytickets.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/settings/settings-system.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/dashboard/modals.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/settings/settings.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/dashboard/customers-list.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/frontend/createticketconfirmation.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/settings/settings-frontend.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/helpdesk-support-tickets/controls/dashboard/tickets-view-ticketdata.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/helpdesk-support-tickets/controls/frontend/home.php:4
- > PHP Fatal error
Uncaught Error: Class 'hst_Classes_Notification' not found in wp-content/plugins/helpdesk-support-tickets/controls/settings/settings-notifications.php:4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
5 plugin tags: support tickets, support, agent, help desk, helpdesk
helpdesk-support-tickets/helpdesk-support-tickets.php 85% from 13 tests
Analyzing the main PHP file in "Helpdesk Support Tickets Plugin for WordPress" version 1.1.4
The following require your attention:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Description: The description should be shorter than 140 characters (currently 212 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin23,688 lines of code in 94 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 10 | 845 | 177 | 10,346 |
PHP | 65 | 2,716 | 1,043 | 7,090 |
JavaScript | 17 | 1,001 | 391 | 3,027 |
SVG | 1 | 0 | 0 | 2,671 |
PO File | 1 | 198 | 226 | 554 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.17 |
Average class complexity | 11.63 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 88.00 |
Average method complexity | 4.74 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 21.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 19 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 19 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 54 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 47 | 87.04% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 7 | 12.96% |
Functions | 69 | |
▷ Named functions | 69 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 46 | |
▷ Global constants | 46 | 100.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
9 compressed PNG files occupy 0.09MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/sending_email_32.png | 2.13KB | 1.56KB | ▼ 26.81% |
images/check_32.png | 2.06KB | 1.70KB | ▼ 17.69% |
images/redcross_32.png | 1.63KB | 1.38KB | ▼ 15.05% |
images/warning_32.png | 1.32KB | 1.37KB | 0.00% |
images/add_32.png | 0.65KB | 0.61KB | ▼ 5.41% |