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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.09ms] Passed 4 tests
An overview of server-side resources used by Add SweetAlert to Elementor Form
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.94 ▼0.24 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 49.57 ▼0.66 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.13 ▼3.43 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.25 ▼14.69 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.69 ▼5.58 |
Server storage [IO: ▲0.27MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Add SweetAlert to Elementor Form
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,828 ▲67 | 13.35 ▼1.03 | 6.38 ▲4.34 | 42.25 ▲0.51 |
| Dashboard /wp-admin | 2,221 ▲21 | 5.87 ▲0.05 | 110.60 ▲7.69 | 45.34 ▲3.44 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 1.97 ▼0.02 | 35.21 ▼3.16 | 35.30 ▼1.41 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲8 | 18.44 ▼4.76 | 645.64 ▼58.76 | 51.43 ▼8.92 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.23 ▲0.06 | 99.33 ▼1.55 | 46.56 ▲1.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
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/add-sweetalert-to-elementor-form/add-sweetalert-to-elementor-form.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration Passed 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
10 plugin tags: elementor addon, elements, addons, elementor extensions, elementor...
add-sweetalert-to-elementor-form/add-sweetalert-to-elementor-form.php Passed 13 tests
The main file in "Add SweetAlert to Elementor Form" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
98 characters long description:
Replaces the default Elementor Form message display after submission with the SweetAlert2 default.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected60 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 2 | 0 | 27 |
| CSS | 2 | 0 | 0 | 25 |
| PHP | 1 | 4 | 11 | 8 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
1 PNG file occupies 0.18MB with 0.07MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 185.30KB | 111.06KB | ▼ 40.07% |