Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼5.82ms] Passed 4 tests
Server-side resources used by Hello Event
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.12 | 41.47 ▼3.59 |
| Dashboard /wp-admin | 3.43 ▲0.12 | 46.24 ▼0.28 |
| Posts /wp-admin/edit.php | 3.48 ▲0.12 | 46.61 ▼3.06 |
| Add New Post /wp-admin/post-new.php | 6.03 ▲0.14 | 82.43 ▼16.36 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 34.54 ▲0.51 |
| Test Settings /wp-admin/admin.php?page=hello-bsr | 3.31 | 37.51 |
| Add New /wp-admin/post-new.php?post_type=hello_event | 3.48 | 47.85 |
| All Events /wp-admin/edit.php?post_type=hello_event | 3.40 | 37.26 |
| Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=hello_event | 3.34 | 35.16 |
Server storage [IO: ▲8.57MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 456 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| hello_event |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Hello Event
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,046 ▲300 | 14.75 ▲0.46 | 12.84 ▲11.05 | 40.30 ▼2.78 |
| Dashboard /wp-admin | 2,256 ▲71 | 5.10 ▼0.92 | 107.61 ▲5.84 | 39.42 ▼4.85 |
| Posts /wp-admin/edit.php | 2,139 ▲50 | 2.42 ▲0.40 | 40.15 ▼1.25 | 34.73 ▼1.15 |
| Add New Post /wp-admin/post-new.php | 1,561 ▲24 | 23.55 ▲0.59 | 655.38 ▲65.40 | 35.08 ▼18.55 |
| Media Library /wp-admin/upload.php | 1,432 ▲41 | 4.49 ▲0.29 | 99.16 ▲0.51 | 42.47 ▼1.99 |
| Hello Event /wp-admin/options-general.php?page=Hello Event_options | 1,279 | 1.86 | 28.62 | 36.30 |
| Test Settings /wp-admin/admin.php?page=hello-bsr | 808 | 1.87 | 26.00 | 20.98 |
| Add New /wp-admin/post-new.php?post_type=hello_event | 3,484 | 10.22 | 206.48 | 68.52 |
| All Events /wp-admin/edit.php?post_type=hello_event | 1,192 | 2.40 | 33.01 | 29.87 |
| Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=hello_event | 1,357 | 2.04 | 30.27 | 29.55 |
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
- This plugin does not fully uninstall, leaving 7 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- hello_event
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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 take a closer look at the following
- 2× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/hello-event/includes/fullcalendar.2.7.1/demos/php/get-timezones.php
- > /wp-content/plugins/hello-event/includes/fullcalendar.2.7.1/demos/php/get-events.php
- 6× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\add_action() in wp-content/plugins/hello-event/includes/hello-event-google-map.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\add_action() in wp-content/plugins/hello-event/includes/hello-event-calendar.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\add_action() in wp-content/plugins/hello-event/includes/hello-event-openstreet-map.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\add_action() in wp-content/plugins/hello-event/includes/hello-event-settings.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\trailingslashit() in wp-content/plugins/hello-event/includes/hello-event-map.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function Tekomatik\\HelloEvent\\add_action() in wp-content/plugins/hello-event/includes/hello-event-list-events.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
7 plugin tags: google map, events, calendar, tickets, ical...
hello-event/hello_event.php 92% from 13 tests
The main file in "Hello Event" v. 1.3.11 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("hello-event.php" instead of "hello_event.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected90,166 lines of code in 359 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 279 | 11,839 | 11,858 | 72,894 |
| JSON | 6 | 0 | 0 | 5,692 |
| CSS | 24 | 603 | 501 | 4,333 |
| HTML | 29 | 417 | 7 | 3,106 |
| PHP | 11 | 376 | 565 | 2,836 |
| PO File | 3 | 375 | 506 | 1,025 |
| Markdown | 4 | 57 | 0 | 134 |
| Sass | 1 | 17 | 0 | 133 |
| YAML | 1 | 0 | 0 | 7 |
| Ruby | 1 | 3 | 4 | 6 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 35.44 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 191.00 |
| Average method complexity | 3.35 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 28.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 120 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 116 | 96.67% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 3.33% |
| Functions | 7 | |
| ▷ Named functions | 2 | 28.57% |
| ▷ Anonymous functions | 5 | 71.43% |
| Constants | 8 | |
| ▷ Global constants | 2 | 25.00% |
| ▷ Class constants | 6 | 75.00% |
| ▷ Public constants | 6 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
51 PNG files occupy 1.47MB with 0.47MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| includes/css/images/ui-icons_888888_256x240.png | 6.83KB | 4.17KB | ▼ 38.92% |
| includes/fullcalendar.2.7.1/lib/cupertino/images/ui-bg_glass_80_d7ebf9_1x400.png | 0.34KB | 0.16KB | ▼ 53.76% |
| js/datetimepicker/screen/4.png | 12.29KB | 5.50KB | ▼ 55.26% |
| includes/js/jquery-ui-1.12.1-2.custom-dialog/images/ui-icons_cc0000_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |
| includes/fullcalendar.2.7.1/lib/cupertino/images/ui-icons_2e83ff_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |