Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.81ms] Passed 4 tests
This is a short check of server-side resources used by Date/Time Fields for Gravity Forms
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 40.05 ▼1.90 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 51.99 ▼1.47 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 53.12 ▼1.61 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 103.94 ▼9.29 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.12 ▼2.44 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 13 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Date/Time Fields for Gravity Forms
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.71 ▲0.55 | 2.20 ▲0.58 | 43.03 ▼0.83 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.61 ▼0.06 | 91.03 ▲1.77 | 37.71 ▼11.74 |
| Posts /wp-admin/edit.php | 2,097 ▼6 | 1.99 ▼0.02 | 38.56 ▼1.05 | 36.18 ▼1.71 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.53 ▲2.32 | 607.73 ▼70.72 | 48.14 ▼16.28 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.22 ▲0.00 | 99.31 ▼1.34 | 43.40 ▼7.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/datetime-fields-for-gravityforms/datetimefield.php:13
- > PHP Fatal error
Uncaught Error: Class 'GFForms' not found in wp-content/plugins/datetime-fields-for-gravityforms/class-gfdatetimefield.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (You can easily find "Date/Time" field in Advanced Fields), #2 (View of the Forms that included in "Date/Time" field.), #3 (View of Form Entries's List), #4 (View of Form Entries's Item), #5 (Date/Time Field)
datetime-fields-for-gravityforms/datetimefield.php 92% from 13 tests
The primary PHP file in "Date/Time Fields for Gravity Forms" version 1.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("datetime-fields-for-gravityforms.php" instead of "datetimefield.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected3,071 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 345 | 294 | 2,654 |
| CSS | 1 | 54 | 31 | 254 |
| PHP | 3 | 53 | 90 | 163 |
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.26 |
| Average class complexity | 5.67 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 14 | |
| ▷ Static methods | 2 | 14.29% |
| ▷ Public methods | 14 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.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
5 PNG files occupy 0.06MB with 0.03MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-4.png | 7.59KB | 5.15KB | ▼ 32.16% |
| screenshot-3.png | 21.65KB | 13.51KB | ▼ 37.61% |
| screenshot-5.png | 21.00KB | 8.46KB | ▼ 59.73% |
| screenshot-1.png | 7.39KB | 4.00KB | ▼ 45.91% |
| screenshot-2.png | 5.64KB | 3.62KB | ▼ 35.84% |