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
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.56ms] Passed 4 tests
An overview of server-side resources used by Emercury Add-on for Elementor PRO
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.97 ▼3.10 |
Dashboard /wp-admin | 3.31 ▲0.00 | 46.37 ▼4.12 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.28 ▼2.55 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.11 ▼8.45 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.53 ▲1.34 |
Server storage [IO: ▲0.27MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
Emercury Add-on for Elementor PRO: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.26 ▼1.09 | 1.66 ▼0.68 | 40.45 ▼11.63 |
Dashboard /wp-admin | 2,203 ▲15 | 5.95 ▲1.05 | 100.91 ▼5.15 | 41.88 ▼2.30 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.04 | 34.14 ▼1.50 | 36.89 ▲3.13 |
Add New Post /wp-admin/post-new.php | 1,519 ▼18 | 23.24 ▲0.08 | 648.28 ▼15.38 | 57.84 ▲7.72 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.21 ▲0.04 | 96.06 ▲0.79 | 42.48 ▼0.66 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/emercury-add-on-for-elementor-pro/controller/emercury_module.php:9
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that require attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Elementor -> Settings -> Integrations.), #2 (You can't use Emercury without filled in API keys.), #3 (Create widget form.), #4 (Select Action after Submit "Emercury".), #5 (Mapping Emercury fields to Form.)
emercury-add-on-for-elementor-pro/elementor-emercury-add-on.php 85% from 13 tests
The main PHP file in "Emercury Add-on for Elementor PRO" ver. 1.0.4 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("emercury-add-on-for-elementor-pro.php" instead of "elementor-emercury-add-on.php")
- Description: The description should be shorter than 140 characters (currently 169 characters long)
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
Good job! No executable or dangerous file extensions detected361 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 81 | 50 | 361 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 7.33 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 14.00 |
Average method complexity | 2.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 1 | 33.33% |
▷ Concrete classes | 2 | 66.67% |
▷ Final classes | 0 | 0.00% |
Methods | 21 | |
▷ Static methods | 1 | 4.76% |
▷ Public methods | 15 | 71.43% |
▷ Protected methods | 3 | 14.29% |
▷ Private methods | 3 | 14.29% |
Functions | 7 | |
▷ Named functions | 5 | 71.43% |
▷ Anonymous functions | 2 | 28.57% |
Constants | 5 | |
▷ Global constants | 2 | 40.00% |
▷ Class constants | 3 | 60.00% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
5 PNG files occupy 0.25MB with 0.18MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 80.74KB | 27.12KB | ▼ 66.41% |
screenshot-5.png | 65.49KB | 16.89KB | ▼ 74.20% |
screenshot-4.png | 23.45KB | 7.36KB | ▼ 68.59% |
screenshot-3.png | 59.40KB | 14.21KB | ▼ 76.08% |
screenshot-2.png | 29.64KB | 9.68KB | ▼ 67.32% |