Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼8.26ms] Passed 4 tests
This is a short check of server-side resources used by Future Ticketing
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.61 ▼6.90 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 47.67 ▼3.42 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 46.25 ▼2.46 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 93.96 ▼20.25 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 38.07 ▲3.40 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 14 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Future Ticketing
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,816 ▲81 | 13.24 ▼1.13 | 1.69 ▼0.43 | 42.59 ▼4.96 |
| Dashboard /wp-admin | 2,225 ▲37 | 5.88 ▲0.96 | 105.25 ▲1.71 | 42.70 ▲0.26 |
| Posts /wp-admin/edit.php | 2,105 ▲16 | 2.05 ▼0.00 | 39.71 ▼0.05 | 34.60 ▼0.59 |
| Add New Post /wp-admin/post-new.php | 1,550 ▲13 | 18.12 ▼0.10 | 598.88 ▲1.63 | 58.17 ▼1.18 |
| Media Library /wp-admin/upload.php | 1,407 ▲16 | 4.31 ▲0.13 | 95.39 ▼0.92 | 42.11 ▼2.68 |
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
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests Passed 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)
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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 SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: rsvp, ticket sales, attendee management, registration, tickets...
future-ticketing/future-ticketing.php 77% from 13 tests
The main PHP script in "Future Ticketing" version 1.0.0-beta... is automatically included on every request by WordPress
You should first fix the following items:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Version: Use periods and digits only for your plugin's version number (ex. "1.0.3" instead of "1.0.0-beta...")
- Description: Please keep the plugin description shorter than 140 characters (currently 322 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
Everything looks great! No dangerous files found in this plugin225 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 69 | 27 | 182 |
| JavaScript | 1 | 5 | 3 | 43 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 11 | |
| ▷ Named functions | 11 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected