Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼5.85ms] Passed 4 tests
Server-side resources used by Ecomail
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 39.48 ▼2.10 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 49.79 ▼4.15 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 48.25 ▼6.63 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 85.97 ▼10.52 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 36.43 ▼1.33 |
Server storage [IO: ▲1.89MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 323 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
Ecomail: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,820 ▲34 | 14.34 ▼0.01 | 1.93 ▼0.26 | 43.87 ▼1.66 |
| Dashboard /wp-admin | 2,201 ▲27 | 5.62 ▼0.00 | 94.36 ▼3.63 | 42.68 ▼6.71 |
| Posts /wp-admin/edit.php | 2,107 ▲10 | 1.99 ▼0.03 | 36.23 ▼3.82 | 34.48 ▼6.02 |
| Add New Post /wp-admin/post-new.php | 1,532 ▲6 | 23.13 ▼0.51 | 652.82 ▲5.27 | 55.67 ▼3.11 |
| Media Library /wp-admin/upload.php | 1,409 ▲15 | 4.22 ▲0.02 | 93.80 ▼13.00 | 43.06 ▼4.19 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
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)
Good news, no errors were detected
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
Please fix the following
- 167× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'EcomailDeps\\Wpify\\CustomFields\\Implementations\\AbstractPostImplementation' not found in wp-content/plugins/ecomail/deps/wpify/custom-fields/src/Implementations/Metabox.php:12
- > PHP Fatal error
Uncaught Error: Class 'EcomailDeps\\Wpify\\Model\\Abstracts\\AbstractRepository' not found in wp-content/plugins/ecomail/deps/wpify/model/src/Abstracts/AbstractDbTableRepository.php:6
- > PHP Fatal error
Uncaught Error: Class 'EcomailDeps\\Wpify\\Model\\Abstracts\\AbstractTermRepository' not found in wp-content/plugins/ecomail/deps/wpify/model/src/MenuRepository.php:12
- > PHP Fatal error
Uncaught Error: Interface 'EcomailDeps\\Invoker\\InvokerInterface' not found in wp-content/plugins/ecomail/deps/php-di/invoker/src/Invoker.php:19
- > PHP Fatal error
Uncaught Error: Interface 'EcomailDeps\\PHPStan\\PhpDocParser\\Ast\\Type\\TypeNode' not found in wp-content/plugins/ecomail/deps/phpstan/phpdoc-parser/src/Ast/Type/ArrayShapeItemNode.php:9
- > PHP Fatal error
Uncaught Error: Class 'EcomailDeps\\Wpify\\Model\\Abstracts\\AbstractPostRepository' not found in wp-content/plugins/ecomail/deps/wpify/model/src/PageRepository.php:18
- > PHP Fatal error
Uncaught Error: Interface 'EcomailDeps\\PHPStan\\PhpDocParser\\Ast\\PhpDoc\\PhpDocTagValueNode' not found in wp-content/plugins/ecomail/deps/phpstan/phpdoc-parser/src/Ast/PhpDoc/InvalidTagValueNode.php:7
- > PHP Fatal error
Uncaught Error: Class 'EcomailDeps\\DI\\Definition\\Helper\\CreateDefinitionHelper' not found in wp-content/plugins/ecomail/deps/php-di/php-di/src/Definition/Helper/AutowireDefinitionHelper.php:12
- > PHP Fatal error
Uncaught Error: Interface 'EcomailDeps\\DI\\Definition\\Definition' not found in wp-content/plugins/ecomail/deps/php-di/php-di/src/Definition/InstanceDefinition.php:12
- > PHP Fatal error
Uncaught Error: Interface 'EcomailDeps\\DI\\Definition\\Definition' not found in wp-content/plugins/ecomail/deps/php-di/php-di/src/Definition/ArrayDefinition.php:12
- > 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)
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
6 plugin tags: email, woocommerce, newsletter, emailing, marketing...
ecomail/ecomail.php 85% from 13 tests
This is the main PHP file of "Ecomail" version 2.1.6, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Requires PHP: Required version must match the one declared in readme.txt ("7.4" instead of "7.4.0")
- Requires at least: Required version must match the one declared in readme.txt ("5.3" instead of "5.3.0")
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
No dangerous file extensions were detected16,769 lines of code in 302 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 265 | 872 | 5,708 | 14,145 |
| Markdown | 16 | 596 | 0 | 1,388 |
| JSON | 13 | 0 | 0 | 955 |
| PO File | 1 | 65 | 76 | 203 |
| JavaScript | 4 | 6 | 0 | 60 |
| YAML | 1 | 1 | 0 | 12 |
| SVG | 1 | 0 | 0 | 4 |
| CSS | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 8.71 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 318.00 |
| Average method complexity | 2.49 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 63.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 52 | |
| Interfaces | 32 | |
| Traits | 1 | |
| Classes | 214 | |
| ▷ Abstract classes | 14 | 6.54% |
| ▷ Concrete classes | 200 | 93.46% |
| ▷ Final classes | 17 | 8.50% |
| Methods | 1,216 | |
| ▷ Static methods | 72 | 5.92% |
| ▷ Public methods | 1,059 | 87.09% |
| ▷ Protected methods | 50 | 4.11% |
| ▷ Private methods | 107 | 8.80% |
| Functions | 77 | |
| ▷ Named functions | 20 | 25.97% |
| ▷ Anonymous functions | 57 | 74.03% |
| Constants | 61 | |
| ▷ Global constants | 5 | 8.20% |
| ▷ Class constants | 56 | 91.80% |
| ▷ Public constants | 53 | 94.64% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.23MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| deps/wpify/custom-fields/build/images/flags.007b2705.png | 69.20KB | 23.42KB | ▼ 66.16% |
| deps/wpify/custom-fields/build/images/flags@2x.9d5328fb.png | 170.28KB | 68.04KB | ▼ 60.04% |