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.00MB] [CPU: ▼4.13ms] Passed 4 tests
A check of server-side resources used by Date Time Picker for Contact Form 7
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 37.06 ▼8.35 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.04 ▼5.05 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.00 ▲0.32 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 90.85 ▼3.44 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.15 ▲0.79 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Date Time Picker for Contact Form 7
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,885 ▲150 | 13.64 ▼0.98 | 6.30 ▲4.35 | 38.74 ▼6.18 |
| Dashboard /wp-admin | 2,203 ▲14 | 4.86 ▼0.12 | 127.32 ▲6.99 | 38.86 ▼6.51 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 1.99 ▼0.06 | 39.82 ▲4.24 | 35.08 ▲3.71 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲25 | 23.32 ▲5.85 | 646.51 ▼10.00 | 53.24 ▲3.30 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.28 ▲0.08 | 93.24 ▼10.51 | 46.42 ▲0.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 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 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/date-time-picker-for-contact-form-7/cf7-datetimepicker.php:16
- > 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 86% from 29 tests
readme.txt 94% 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
Attributes that require attention:
- Plugin Name: Please specify the plugin name on the first line (
=== date-time-picker-for-contact-form-7 ===)
date-time-picker-for-contact-form-7/cf7-datetimepicker.php 77% from 13 tests
The main file in "Date Time Picker for Contact Form 7" v. 1.1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 210 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("date-time-picker-for-contact-form-7.php" instead of "cf7-datetimepicker.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
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
Good job! No executable or dangerous file extensions detected2,790 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 4 | 282 | 265 | 2,745 |
| PHP | 1 | 11 | 12 | 44 |
| CSS | 1 | 1 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| 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 | 5 | |
| ▷ Global constants | 5 | 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