Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.88ms] Passed 4 tests
A check of server-side resources used by Easy Date and Time Picker
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 41.19 ▲1.05 |
Dashboard /wp-admin | 3.31 ▲0.01 | 52.70 ▼4.60 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 50.08 ▼0.95 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 102.49 ▲5.75 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.43 ▲0.98 |
Server storage [IO: ▲0.75MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Easy Date and Time Picker
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,912 ▲151 | 14.33 ▼0.02 | 26.46 ▲24.89 | 42.70 ▲0.44 |
Dashboard /wp-admin | 2,199 ▲18 | 5.65 ▼0.07 | 94.41 ▼11.34 | 38.13 ▼4.77 |
Posts /wp-admin/edit.php | 2,104 ▲22 | 2.03 ▼0.01 | 36.80 ▼1.85 | 37.16 ▲1.83 |
Add New Post /wp-admin/post-new.php | 1,530 ▼1 | 23.53 ▲0.36 | 701.45 ▼40.25 | 54.70 ▼10.74 |
Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.20 ▲0.02 | 102.61 ▼0.18 | 45.43 ▼2.58 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- 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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/datetime-picker/Datetime-Picker.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 79% from 29 tests
readme.txt 81% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Please add descriptions for these screenshots #0, #0 in datetime-picker/assets to your readme.txt
- Screenshots: Add an image for screenshot #1 (screenshots.png)
- Stable tag: No string
datetime-picker/Datetime-Picker.php 77% from 13 tests
The main PHP file in "Easy Date and Time Picker" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 213 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("datetime-picker.php" instead of "Datetime-Picker.php")
- Text Domain: The text domain name must use dashes instead of underscores, and it must be lowercase
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
Everything looks great! No dangerous files found in this plugin836 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 0 | 414 |
JavaScript | 2 | 28 | 9 | 352 |
CSS | 2 | 0 | 3 | 36 |
PHP | 1 | 20 | 12 | 34 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
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 | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/icon.png | 1.28KB | 0.45KB | ▼ 64.40% |