Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.13ms] Passed 4 tests
Server-side resources used by pipwave Gravity Forms
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 43.88 ▲1.13 |
Dashboard /wp-admin | 3.31 ▲0.01 | 57.68 ▲4.01 |
Posts /wp-admin/edit.php | 3.37 ▲0.00 | 48.17 ▼2.53 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.00 | 87.78 ▼9.04 |
Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 34.30 ▼2.08 |
Server storage [IO: ▲1.29MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 32 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for pipwave Gravity Forms
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.35 ▼0.24 | 1.84 ▼0.02 | 42.82 ▼5.35 |
Dashboard /wp-admin | 2,198 ▲21 | 5.62 ▼0.07 | 94.94 ▲5.39 | 41.95 ▲1.46 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.00 ▼0.12 | 35.13 ▼3.17 | 36.89 ▼0.41 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.10 ▼0.18 | 639.69 ▼27.93 | 72.71 ▲18.79 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▼0.12 | 102.96 ▼14.94 | 45.01 ▼3.03 |
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
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, 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
Please take a closer look at the following
- 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/pipwave-gravity-forms/class-gf-pipwave.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pipwave-gravity-forms/pipwave.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% 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 your attention:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4, #5 in pipwave-gravity-forms/assets to your readme.txt
- Tags: Please reduce the number of tags, currently 13 tag instead of maximum 10
pipwave-gravity-forms/pipwave.php 92% from 13 tests
"pipwave Gravity Forms" version 1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("pipwave-gravity-forms.php" instead of "pipwave.php")
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
Everything looks great! No dangerous files found in this plugin602 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 103 | 137 | 602 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 42.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 82.00 |
Average method complexity | 4.57 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 37.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 23 | |
▷ Static methods | 3 | 13.04% |
▷ Public methods | 23 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.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 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
29 PNG files occupy 1.26MB with 0.70MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/multiple_payment/multiple_payment_2.png | 66.16KB | 29.22KB | ▼ 55.83% |
images/configure/configure4.png | 36.66KB | 15.71KB | ▼ 57.15% |
images/multiple_payment/multiple_payment_10.png | 53.10KB | 24.20KB | ▼ 54.42% |
images/multiple_payment/multiple_payment_8.png | 52.26KB | 23.40KB | ▼ 55.22% |
images/install/1height.png | 36.93KB | 16.31KB | ▼ 55.83% |