Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▲0.61ms] Passed 4 tests
Server-side resources used by WI Contact Form 7 for Elementor
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.63 ▼5.35 |
Dashboard /wp-admin | 3.31 ▲0.01 | 52.88 ▲3.34 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 50.79 ▼0.03 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 93.53 ▲4.46 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 40.69 ▲5.25 |
Server storage [IO: ▲0.18MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 17 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
WI Contact Form 7 for Elementor: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 14.48 ▲0.10 | 2.07 ▼0.14 | 42.82 ▲0.51 |
Dashboard /wp-admin | 2,206 ▲18 | 5.85 ▲0.98 | 107.63 ▼6.52 | 41.51 ▼3.55 |
Posts /wp-admin/edit.php | 2,086 ▼6 | 2.03 ▼0.00 | 39.33 ▼1.50 | 34.28 ▼2.62 |
Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 23.39 ▲5.81 | 660.97 ▼38.15 | 57.50 ▲6.18 |
Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.24 ▲0.07 | 113.74 ▲7.20 | 50.64 ▲7.63 |
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
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function Elementor\\add_action() in wp-content/plugins/wi-contact-form-7-for-elementor/inc/elementor-helper.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 83% 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
Attributes that need to be fixed:
- Screenshots: Please a description for screenshot #4 in wi-contact-form-7-for-elementor/assets to your readme.txt
- Tags: You are using too many tags: 11 tag instead of maximum 10
wi-contact-form-7-for-elementor/webinside-elementor-contact-form-7-addon.php 77% from 13 tests
The main file in "WI Contact Form 7 for Elementor" v. 1... serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Version: Use periods and digits only for your plugin's version number (ex. "1.0.3" instead of "1...")
- Text Domain: The text domain name should consist of only dashes and lowercase characters
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wi-contact-form-7-for-elementor.php" instead of "webinside-elementor-contact-form-7-addon.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin558 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 57 | 16 | 467 |
PO File | 1 | 40 | 45 | 91 |
CSS | 1 | 0 | 3 | 0 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
Average class complexity | 3.00 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 3.00 |
Average method complexity | 1.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 7 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 4 | 57.14% |
▷ Protected methods | 3 | 42.86% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
5 PNG files occupy 0.09MB with 0.06MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/icon-128x128.png | 3.74KB | 2.25KB | ▼ 39.76% |
assets/screenshot-2.png | 5.71KB | 2.12KB | ▼ 62.93% |
assets/screenshot-3.png | 17.70KB | 5.32KB | ▼ 69.92% |
assets/screenshot-4.png | 11.02KB | 3.45KB | ▼ 68.74% |
assets/screenshot-1.png | 52.38KB | 14.83KB | ▼ 71.68% |