Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Please fix the following installer errors
- This plugin did not install gracefully
- > Deprecated in wp-content/plugins/blog-post-calendar-widget/wp-calendar.php+122
Methods with the same name as their class will not be constructors in a future version of PHP; WP_Calander_Widget has a deprecated constructor
Server metrics [RAM: ▼2.02MB] [CPU: ▼58.60ms] Passed 4 tests
Server-side resources used by Blog Post Calendar Widget
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.25 ▼1.49 | 5.23 ▼39.80 |
| Dashboard /wp-admin | 2.27 ▼1.30 | 7.22 ▼46.80 |
| Posts /wp-admin/edit.php | 2.27 ▼1.41 | 5.88 ▼47.74 |
| Add New Post /wp-admin/post-new.php | 2.27 ▼3.88 | 5.83 ▼100.05 |
| Media Library /wp-admin/upload.php | 2.27 ▼1.22 | 7.50 ▼34.34 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
It is recommended to fix the following issues
- Illegal file modification found: 1 file (12.76KB) outside of "wp-content/plugins/blog-post-calendar-widget/" and "wp-content/uploads/"
- (new file) wp-content/themes/twentytwentyone/wp_calendar.css
Filesystem: 25 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_wp_calander_widget |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Blog Post Calendar Widget
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,884 ▲123 | 14.73 ▲0.35 | 6.81 ▲4.96 | 42.00 ▼0.84 |
| Dashboard /wp-admin | 2,197 ▲20 | 5.65 ▲0.01 | 96.97 ▲6.14 | 42.96 ▼1.37 |
| Posts /wp-admin/edit.php | 2,105 ▲5 | 2.04 ▲0.04 | 35.97 ▼0.88 | 33.78 ▲2.29 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲5 | 22.13 ▼1.14 | 626.29 ▼71.82 | 62.91 ▲0.31 |
| Media Library /wp-admin/upload.php | 1,408 ▲14 | 4.22 ▲0.00 | 102.58 ▲3.18 | 44.16 ▼8.50 |
Uninstaller [IO: ▲0.01MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > Deprecated in wp-content/plugins/blog-post-calendar-widget/wp-calendar.php+122
Methods with the same name as their class will not be constructors in a future version of PHP; WP_Calander_Widget has a deprecated constructor
- Zombie WordPress options detected upon uninstall: 7 options
- can_compress_scripts
- widget_recent-posts
- widget_wp_calander_widget
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Warning
Use of undefined constant WP_PLUGIN_URL - assumed 'WP_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/blog-post-calendar-widget/wp-calendar.php on line 27
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/blog-post-calendar-widget/wp-calendar.php:27
- > PHP Warning
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 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
6 plugin tags: future posts, post types, events calendar, posts, widget...
blog-post-calendar-widget/wp-calendar.php 92% from 13 tests
The primary PHP file in "Blog Post Calendar Widget" version 1.1 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("blog-post-calendar-widget.php" instead of "wp-calendar.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin3,087 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 6 | 201 | 261 | 1,884 |
| PHP | 1 | 57 | 71 | 524 |
| CSS | 1 | 51 | 2 | 387 |
| PO File | 4 | 117 | 122 | 292 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 30.00 |
| ▷ Minimum class complexity | 30.00 |
| ▷ Maximum class complexity | 30.00 |
| Average method complexity | 8.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 21.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 | 10 | |
| ▷ Named functions | 10 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 6 | |
| ▷ Global constants | 6 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
5 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/macFFBgHack.png | 0.20KB | 0.09KB | ▼ 53.14% |
| images/arrow-next-hover.png | 2.84KB | 0.18KB | ▼ 93.75% |
| images/arrow-new.png | 2.84KB | 0.18KB | ▼ 93.71% |
| images/arrow-prev-hover.png | 2.83KB | 0.18KB | ▼ 93.70% |
| images/arrow-new2.png | 2.83KB | 0.18KB | ▼ 93.73% |