Benchmarks
Plugin footprint 82% 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.10MB] [CPU: ▲211.70ms] 75% from 4 tests
A check of server-side resources used by ticketing online
It is recommended to improve the following
- Extra CPU: Extra CPU usage must be kept under 200.00ms (currently 211.70ms on /wp-admin/options-general.php?page=wp-ticketing)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 41.93 ▼3.92 |
| Dashboard /wp-admin | 3.46 ▲0.15 | 323.42 ▲268.70 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 343.32 ▲293.63 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 395.92 ▲296.15 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 326.67 ▲288.38 |
| ticketing Online /wp-admin/options-general.php?page=wp-ticketing | 3.29 | 326.65 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 35 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| wpticketing-password |
| can_compress_scripts |
| widget_recent-posts |
| wpticketing-email |
Browser metrics Passed 4 tests
Checking browser requirements for ticketing online
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,906 ▲117 | 13.63 ▲0.34 | 5.20 ▲3.23 | 42.89 ▼5.16 |
| Dashboard /wp-admin | 2,226 ▲20 | 4.86 ▼1.01 | 110.06 ▼1.96 | 47.39 ▲4.99 |
| Posts /wp-admin/edit.php | 2,112 ▲23 | 1.99 ▼0.00 | 40.31 ▲3.78 | 35.10 ▲1.47 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲6 | 22.92 ▲4.66 | 673.76 ▲60.44 | 60.71 ▲9.58 |
| Media Library /wp-admin/upload.php | 1,411 ▲26 | 4.24 ▲0.02 | 97.95 ▼3.71 | 44.74 ▼1.32 |
| ticketing Online /wp-admin/options-general.php?page=wp-ticketing | 844 | 2.03 | 25.92 | 32.19 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 8 options
- wpticketing-password
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- wpticketing-email
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
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 items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/ticketing-system/public/partials/wp-ticketing-public-display.php
- > /wp-content/plugins/ticketing-system/public/partials/wp-reservas-public-display.php
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_load_alloptions() in wp-content/plugins/ticketing-system/admin/partials/wp-ticketing-admin-display.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_load_alloptions() in wp-content/plugins/ticketing-system/admin/partials/wp-reservas-admin-display.php:17
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please fix the following user-side errors
- > GET request to /wp-admin/options-general.php?page=wp-ticketing
- > Network (severe)
wp-content/plugins/ticketing-system/admin/css/wp-ticketing-admin.css?ver=1.0.0 - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/options-general.php?page=wp-ticketing
- > Network (severe)
wp-content/plugins/ticketing-system/admin/js/wp-ticketing-admin.js?ver=1.0.0 - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 76% from 29 tests
readme.txt 75% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Requires php: Version format is invalid
- Screenshots: Add images for these screenshots: #1 (https://www.ticketself.com/static/integrations/wordpress/screenshots/1.png), #2 (https://www.ticketself.com/static/integrations/wordpress/screenshots/2.png)
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
- Contributors: Plugin contributors field is missing
ticketing-system/wp-ticketing.php 77% from 13 tests
"ticketing online" version 1.4's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 163 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("ticketing-system.php" instead of "wp-ticketing.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
There were no executable files found in this plugin568 lines of code in 24 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 20 | 236 | 1,020 | 562 |
| JavaScript | 2 | 4 | 54 | 6 |
| CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 2.31 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 5.00 |
| Average method complexity | 1.31 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 13 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 55 | |
| ▷ Static methods | 3 | 5.45% |
| ▷ Public methods | 45 | 81.82% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 10 | 18.18% |
| Functions | 5 | |
| ▷ Named functions | 5 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
5 PNG files occupy 0.21MB with 0.08MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-772x250.png | 141.06KB | 99.39KB | ▼ 29.54% |
| assets/icon-128x128.png | 15.54KB | 10.29KB | ▼ 33.75% |
| admin/partials/assets/default/img/logo.png | 5.89KB | 2.88KB | ▼ 51.06% |
| assets/icon-256x256.png | 50.77KB | 36.59KB | ▼ 27.92% |
| assets/default/img/logo.png | 5.89KB | 2.88KB | ▼ 51.06% |