Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.21ms] Passed 4 tests
A check of server-side resources used by Entries Date Range Filter for Gravity Forms
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 47.04 ▲1.27 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 48.61 ▼11.84 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.88 ▼1.29 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 95.10 ▲7.35 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.20 ▲3.02 |
Server storage [IO: ▲7.64MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 74 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Entries Date Range Filter for Gravity Forms: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,792 ▲31 | 14.45 ▲0.05 | 1.64 ▼0.19 | 40.10 ▼4.14 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.62 ▼0.03 | 91.16 ▲1.20 | 38.13 ▼5.90 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.99 ▼0.02 | 38.51 ▼0.12 | 36.81 ▼0.64 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.21 ▲0.34 | 661.11 ▼11.12 | 55.43 ▼4.25 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.17 ▲0.06 | 102.42 ▼0.29 | 50.00 ▲2.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not 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
Please fix the following items
- 5× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Trait 'GFEDRF\\Traits\\Singleton' not found in wp-content/plugins/gf-entries-date-range-filter/inc/scripts.php on line 5
- > PHP Fatal error
Trait 'GFEDRF\\Traits\\Singleton' not found in wp-content/plugins/gf-entries-date-range-filter/inc/bootstrap.php on line 5
- > PHP Fatal error
Trait 'GFEDRF\\Traits\\Singleton' not found in wp-content/plugins/gf-entries-date-range-filter/inc/gravityformshooks.php on line 5
- > PHP Fatal error
Trait 'GFEDRF\\Traits\\Singleton' not found in wp-content/plugins/gf-entries-date-range-filter/inc/requirements.php on line 5
- > PHP Fatal error
Trait 'GFEDRF\\Traits\\Helpers' not found in wp-content/plugins/gf-entries-date-range-filter/inc/traits/singleton.php on line 30
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
9 plugin tags: gravityforms, gravity forms, entries, gravityforms entries date range filter, date range filter...
gf-entries-date-range-filter/gf-entries-date-range-filter.php 92% from 13 tests
The main file in "Entries Date Range Filter for Gravity Forms" v. 1.0 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:
- Text Domain: The text domain name should consist of only dashes and lowercase characters
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
Success! There were no dangerous files found in this plugin52,568 lines of code in 48 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 19 | 8,111 | 139 | 34,189 |
| JavaScript | 11 | 4,445 | 1,971 | 17,636 |
| PHP | 16 | 235 | 279 | 718 |
| JSON | 2 | 0 | 0 | 25 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 9.60 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 2.72 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 2 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 51 | |
| ▷ Static methods | 15 | 29.41% |
| ▷ Public methods | 48 | 94.12% |
| ▷ Protected methods | 2 | 3.92% |
| ▷ Private methods | 1 | 1.96% |
| Functions | 3 | |
| ▷ Named functions | 2 | 66.67% |
| ▷ Anonymous functions | 1 | 33.33% |
| Constants | 11 | |
| ▷ Global constants | 11 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected