Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼9.52ms] Passed 4 tests
An overview of server-side resources used by Publish Date DatePicker
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 33.63 ▼2.71 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 41.73 ▼6.63 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 42.83 ▼6.10 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 83.96 ▼22.64 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.54 ▼0.72 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 15 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Publish Date DatePicker
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.44 ▲0.07 | 1.68 ▲0.14 | 38.19 ▼1.29 |
| Dashboard /wp-admin | 2,203 ▲15 | 5.82 ▲0.93 | 113.77 ▼0.73 | 40.94 ▼2.93 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.06 ▲0.08 | 36.87 ▼5.41 | 30.05 ▼5.31 |
| Add New Post /wp-admin/post-new.php | 1,525 ▼8 | 23.73 ▲0.75 | 675.27 ▲28.33 | 66.52 ▲8.52 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.22 ▲0.10 | 96.27 ▼7.71 | 42.23 ▼2.33 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 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 Passed 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
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
4 plugin tags: post datepicker, datepicker, page datepicker, publish datepicker
publish-date-datepicker/pddp.php 77% from 13 tests
The main PHP file in "Publish Date DatePicker" ver. 3.0 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Description: Keep the plugin description shorter than 140 characters (currently 193 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("publish-date-datepicker.php" instead of "pddp.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected2,400 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 226 | 285 | 1,767 |
| CSS | 1 | 25 | 33 | 594 |
| PHP | 1 | 16 | 38 | 39 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.50 |
| 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 | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
9 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| css/images/ui-icons_222222_256x240.png | 6.76KB | 4.17KB | ▼ 38.24% |
| css/images/ui-bg_glass_55_fbf9ee_1x400.png | 0.33KB | 0.12KB | ▼ 62.09% |
| css/images/ui-bg_glass_65_ffffff_1x400.png | 0.20KB | 0.09KB | ▼ 57.49% |
| css/images/ui-bg_flat_75_ffffff_40x100.png | 0.20KB | 0.08KB | ▼ 58.17% |
| css/images/ui-bg_glass_95_fef1ec_1x400.png | 0.32KB | 0.15KB | ▼ 54.82% |