Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.66ms] Passed 4 tests
Server-side resources used by Date Time Picker for WPForms
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.74 ▲0.01 | 43.23 ▼1.29 |
| Dashboard /wp-admin | 3.58 ▼0.06 | 51.54 ▼15.28 |
| Posts /wp-admin/edit.php | 3.69 ▲0.01 | 50.91 ▲1.88 |
| Add New Post /wp-admin/post-new.php | 6.16 ▲0.01 | 89.57 ▼18.66 |
| Media Library /wp-admin/upload.php | 3.50 ▲0.01 | 38.04 ▲0.60 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Date Time Picker for WPForms
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,899 ▲113 | 13.86 ▼0.58 | 9.91 ▲8.10 | 41.40 ▲3.11 |
| Dashboard /wp-admin | 2,195 ▲14 | 5.62 ▼0.10 | 91.69 ▼8.56 | 38.62 ▼4.23 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.06 ▲0.06 | 39.69 ▲5.38 | 35.58 ▼4.37 |
| Add New Post /wp-admin/post-new.php | 1,532 ▲6 | 23.27 ▲5.51 | 703.30 ▲13.81 | 54.24 ▼7.48 |
| Media Library /wp-admin/upload.php | 1,403 ▲9 | 4.25 ▲0.02 | 96.33 ▼4.91 | 44.37 ▼2.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
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
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/date-time-picker-for-wpforms/wpforms-datetimepicker.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Screenshots: A description for screenshot #4 is missing in date-time-picker-for-wpforms/assets to your readme.txt
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== date-time-picker-for-wpforms ===)
date-time-picker-for-wpforms/wpforms-datetimepicker.php 77% from 13 tests
The main PHP script in "Date Time Picker for WPForms" version 1.1.0 is automatically included on every request by WordPress
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("date-time-picker-for-wpforms.php" instead of "wpforms-datetimepicker.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 196 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin2,789 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 4 | 279 | 265 | 2,745 |
| PHP | 1 | 10 | 12 | 43 |
| CSS | 1 | 1 | 0 | 1 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.08 |
| 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 | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.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
PNG images were not found in this plugin