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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.23MB] [CPU: ▼4.64ms] Passed 4 tests
Analyzing server-side resources used by iContact for Gravity Forms
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.71 ▲0.24 | 37.34 ▼1.25 |
| Dashboard /wp-admin | 3.55 ▲0.20 | 45.07 ▼11.92 |
| Posts /wp-admin/edit.php | 3.66 ▲0.30 | 47.82 ▼1.39 |
| Add New Post /wp-admin/post-new.php | 6.13 ▲0.24 | 91.30 ▼3.99 |
| Media Library /wp-admin/upload.php | 3.47 ▲0.24 | 35.07 ▼1.12 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 18 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by iContact for Gravity Forms
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.15 ▼1.23 | 1.51 ▼0.15 | 40.78 ▲0.55 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.90 ▲1.00 | 95.91 ▼14.13 | 38.07 ▼8.09 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.01 ▲0.03 | 39.14 ▼1.71 | 36.96 ▲1.65 |
| Add New Post /wp-admin/post-new.php | 1,543 ▲24 | 18.29 ▼5.11 | 609.57 ▼137.75 | 52.14 ▼25.35 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.15 ▼0.02 | 95.91 ▼3.67 | 43.07 ▼0.24 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/gravity-forms-icontact/icontact.php:28
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Screenshots: Screenshot #1 (The Gravity Forms iContact Add-on settings page) image missing
- Tags: Too many tags (13 tag instead of maximum 10); only the first 5 tags are used in your directory listing
gravity-forms-icontact/icontact.php 92% from 13 tests
"iContact for Gravity Forms" version 1.3.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("gravity-forms-icontact.php" instead of "icontact.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected1,615 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 343 | 195 | 1,615 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.49 |
| Average class complexity | 72.50 |
| ▷ Minimum class complexity | 9.00 |
| ▷ Maximum class complexity | 198.00 |
| Average method complexity | 4.76 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 54.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 76 | |
| ▷ Static methods | 54 | 71.05% |
| ▷ Public methods | 54 | 71.05% |
| ▷ Protected methods | 4 | 5.26% |
| ▷ Private methods | 18 | 23.68% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.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
7 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icontact_wordpress_icon_32.png | 2.58KB | 1.88KB | ▼ 27.10% |
| images/active0.png | 0.65KB | 0.61KB | ▼ 5.56% |
| images/active1.png | 0.71KB | 0.63KB | ▼ 11.28% |
| images/remove.png | 3.32KB | 0.62KB | ▼ 81.33% |
| images/stop.png | 0.68KB | 0.78KB | 0.00% |