Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.08ms] Passed 4 tests
An overview of server-side resources used by EngageBay Add-on For Contact Form 7
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.35 ▼2.81 |
Dashboard /wp-admin | 3.31 ▲0.00 | 42.79 ▼5.00 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.25 ▲0.93 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 91.30 ▼9.44 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.17 ▲1.86 |
Server storage [IO: ▲1.41MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 192 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for EngageBay Add-on For Contact Form 7
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲68 | 13.23 ▼1.52 | 1.95 ▼0.02 | 39.85 ▼7.10 |
Dashboard /wp-admin | 2,206 ▲18 | 6.06 ▲1.18 | 96.32 ▼21.26 | 40.01 ▼3.71 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.02 | 37.70 ▲2.88 | 34.80 ▼0.72 |
Add New Post /wp-admin/post-new.php | 1,542 ▲20 | 23.07 ▼0.20 | 603.49 ▼21.93 | 51.83 ▲1.30 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.19 ▼0.05 | 93.08 ▼9.46 | 41.21 ▼2.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- 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
Even though no errors were found, this is by no means an exhaustive test
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
Almost there! Just fix the following items
- 62× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/psr7/src/BufferStream.php:14
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UriInterface' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/psr7/src/Uri.php:13
- > PHP Fatal error
Trait 'League\\OAuth2\\Client\\Tool\\RequiredParameterTrait' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/league/oauth2-client/src/Grant/AbstractGrant.php on line 31
- > PHP Fatal error
Uncaught Error: Class 'League\\OAuth2\\Client\\Grant\\AbstractGrant' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/league/oauth2-client/src/Grant/RefreshToken.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/psr7/src/MultipartStream.php:10
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/guzzle/src/Cookie/SessionCookieJar.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function is_plugin_active() in wp-content/plugins/engagebay-add-on-for-contact-form-7/engagebay-cf7-forms.php:18
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/guzzle/src/Exception/BadResponseException.php:10
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Promise\\RejectionException' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/promises/src/CancellationException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/engagebay-add-on-for-contact-form-7/vendor/guzzlehttp/promises/src/FulfilledPromise.php:10
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
These attributes need to be fixed:
- Tags: You are using too many tags: 19 tag instead of maximum 10
engagebay-add-on-for-contact-form-7/engagebay-cf7-forms.php 92% from 13 tests
"EngageBay Add-on For Contact Form 7" version 1.8.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("engagebay-add-on-for-contact-form-7.php" instead of "engagebay-cf7-forms.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 detected19,049 lines of code in 174 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 137 | 2,407 | 6,404 | 13,756 |
Markdown | 18 | 1,295 | 0 | 3,775 |
JSON | 12 | 1 | 0 | 981 |
CSS | 1 | 21 | 4 | 492 |
XML | 1 | 0 | 0 | 19 |
Dockerfile | 1 | 8 | 0 | 10 |
make | 1 | 4 | 0 | 9 |
Bourne Shell | 1 | 2 | 0 | 3 |
JavaScript | 1 | 0 | 0 | 3 |
SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 13.04 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 153.00 |
Average method complexity | 2.69 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 27.00 |
Code structure | ||
---|---|---|
Namespaces | 18 | |
Interfaces | 19 | |
Traits | 9 | |
Classes | 83 | |
▷ Abstract classes | 2 | 2.41% |
▷ Concrete classes | 81 | 97.59% |
▷ Final classes | 13 | 16.05% |
Methods | 827 | |
▷ Static methods | 127 | 15.36% |
▷ Public methods | 638 | 77.15% |
▷ Protected methods | 58 | 7.01% |
▷ Private methods | 131 | 15.84% |
Functions | 214 | |
▷ Named functions | 125 | 58.41% |
▷ Anonymous functions | 89 | 41.59% |
Constants | 107 | |
▷ Global constants | 46 | 42.99% |
▷ Class constants | 61 | 57.01% |
▷ Public constants | 61 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/engagebay.png | 13.12KB | 4.67KB | ▼ 64.38% |