Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.16MB] [CPU: ▲1.26ms] Passed 4 tests
Analyzing server-side resources used by Next Event Calendar
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.63 ▲0.17 | 48.91 ▲2.86 |
| Dashboard /wp-admin | 3.46 ▲0.15 | 51.22 ▲2.25 |
| Posts /wp-admin/edit.php | 3.57 ▲0.21 | 54.72 ▲4.86 |
| Add New Post /wp-admin/post-new.php | 6.04 ▲0.16 | 96.70 ▼4.94 |
| Media Library /wp-admin/upload.php | 3.38 ▲0.15 | 41.04 ▲5.85 |
| All Events /wp-admin/edit.php?post_type=nec_events | 3.42 | 42.02 |
| Event Categories /wp-admin/edit-tags.php?taxonomy=nec_cat_events&post_type=nec_events | 3.37 | 43.78 |
| Add New /wp-admin/post-new.php?post_type=nec_events | 3.54 | 55.61 |
Server storage [IO: ▲0.55MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 19 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_cl_widget |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Next Event Calendar
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,929 ▲168 | 13.50 ▼0.87 | 9.89 ▲7.74 | 43.79 ▼0.53 |
| Dashboard /wp-admin | 2,233 ▲53 | 5.82 ▲0.13 | 89.17 ▼2.16 | 83.72 ▲39.64 |
| Posts /wp-admin/edit.php | 2,159 ▲62 | 2.26 ▲0.25 | 41.45 ▲2.25 | 36.06 ▲0.44 |
| Add New Post /wp-admin/post-new.php | 1,580 ▲46 | 23.24 ▼0.09 | 776.83 ▲105.51 | 55.23 ▲2.48 |
| Media Library /wp-admin/upload.php | 1,447 ▲47 | 4.37 ▲0.11 | 100.59 ▼1.12 | 81.79 ▲36.39 |
| All Events /wp-admin/edit.php?post_type=nec_events | 1,126 | 2.05 | 36.63 | 31.95 |
| Event Categories /wp-admin/edit-tags.php?taxonomy=nec_cat_events&post_type=nec_events | 1,327 | 2.25 | 27.32 | 32.78 |
| Add New /wp-admin/post-new.php?post_type=nec_events | 2,959 | 8.22 | 181.23 | 126.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_cl_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
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
Please take a closer look at the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/next-event-calendar/loop-events.php
- 4× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/next-event-calendar/widget.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/next-event-calendar/admin.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/next-event-calendar/next-event-calendar.php:42
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/next-event-calendar/single.php:83
- > 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 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
- Screenshots: Add a description for screenshot #2 in next-event-calendar/assets to your readme.txt
next-event-calendar/next-event-calendar.php 92% from 13 tests
Analyzing the main PHP file in "Next Event Calendar" version 1.2
You should first fix the following items:
- Description: The description should be shorter than 140 characters (currently 353 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected2,340 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 155 | 39 | 1,177 |
| PHP | 5 | 315 | 149 | 581 |
| CSS | 2 | 39 | 4 | 331 |
| PO File | 2 | 106 | 107 | 251 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 17.00 |
| ▷ Minimum class complexity | 17.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 5.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 17 | |
| ▷ Named functions | 17 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.43MB with 0.34MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 287.80KB | 93.73KB | ▼ 67.43% |
| img/calendar.png | 1.06KB | 0.15KB | ▼ 86.19% |
| img/clock.png | 17.13KB | 1.79KB | ▼ 89.53% |
| screenshot-1.png | 127.48KB | 45.90KB | ▼ 64.00% |
| img/calendar_2.png | 5.68KB | 0.56KB | ▼ 90.08% |