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.03MB] [CPU: ▼2.45ms] Passed 4 tests
Server-side resources used by Custom Datepicker NMR
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 37.15 ▲0.89 |
Dashboard /wp-admin | 3.34 ▲0.03 | 44.56 ▲0.13 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.56 ▲0.63 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 82.76 ▼8.37 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 32.65 ▼2.20 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Custom Datepicker NMR
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,884 ▲123 | 13.97 ▼0.32 | 10.09 ▲8.41 | 44.97 ▼2.70 |
Dashboard /wp-admin | 2,195 ▲18 | 5.56 ▲0.01 | 80.43 ▼4.96 | 38.69 ▼3.67 |
Posts /wp-admin/edit.php | 2,100 ▲3 | 1.98 ▼0.01 | 38.70 ▲1.56 | 35.85 ▲1.33 |
Add New Post /wp-admin/post-new.php | 1,528 ▼9 | 23.42 ▲5.06 | 696.55 ▲46.59 | 51.62 ▼20.13 |
Media Library /wp-admin/upload.php | 1,394 ▼3 | 4.22 ▲0.04 | 98.44 ▲0.08 | 43.66 ▲1.61 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
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 add_action() in wp-content/plugins/custom-datepicker-nmr/nmr-datepicker.php:13
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 86% 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 to be fixed:
- Tags: There are too many tags (11 tag instead of maximum 10)
custom-datepicker-nmr/nmr-datepicker.php 77% from 13 tests
The entry point to "Custom Datepicker NMR" version 1.0.7 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Domain Path: The domain path points to a folder that does not exist ("/languages/")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("custom-datepicker-nmr.php" instead of "nmr-datepicker.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
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 plugin1,353 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 41 | 48 | 1,222 |
PHP | 1 | 25 | 11 | 112 |
JavaScript | 1 | 0 | 0 | 19 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
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 | 6 | |
▷ Named functions | 6 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
6 PNG files occupy 0.04MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
css/images/ui-icons_777777_256x240.png | 6.94KB | 4.18KB | ▼ 39.78% |
css/images/ui-icons_444444_256x240.png | 6.92KB | 4.18KB | ▼ 39.61% |
css/images/ui-icons_777620_256x240.png | 4.51KB | 4.18KB | ▼ 7.28% |
css/images/ui-icons_555555_256x240.png | 6.91KB | 4.18KB | ▼ 39.47% |
css/images/ui-icons_cc0000_256x240.png | 4.51KB | 4.18KB | ▼ 7.28% |