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.00MB] [CPU: ▼2.26ms] Passed 4 tests
Analyzing server-side resources used by Mail Baby SMTP
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 38.76 ▼6.21 |
Dashboard /wp-admin | 3.31 ▲0.00 | 63.94 ▲13.05 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.26 ▲7.15 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 89.96 ▼9.79 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.13 ▼0.20 |
Server storage [IO: ▲20.95MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 730 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by Mail Baby SMTP
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲28 | 14.27 ▼0.07 | 2.01 ▲0.11 | 42.26 ▼0.51 |
Dashboard /wp-admin | 2,195 ▲15 | 5.57 ▼0.08 | 93.06 ▼10.08 | 43.87 ▼1.96 |
Posts /wp-admin/edit.php | 2,097 ▼0 | 2.02 ▲0.07 | 36.57 ▼0.52 | 31.38 ▼1.90 |
Add New Post /wp-admin/post-new.php | 1,535 ▲5 | 18.31 ▼4.78 | 596.95 ▼92.75 | 64.24 ▲7.80 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.28 ▲0.05 | 95.87 ▼9.58 | 40.69 ▼4.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
- 6× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/mail-baby-smtp/inc/vendor/sendgrid/php-http-client/lib/SendGrid/Client.php
- > /wp-content/plugins/mail-baby-smtp/inc/assets/css/customstyle.php
- > /wp-content/plugins/mail-baby-smtp/inc/templates/Mailgun/wp-mail-smtp.php
- > /wp-content/plugins/mail-baby-smtp/inc/templates/Sendin_blue/mailin.php
- > /wp-content/plugins/mail-baby-smtp/inc/vendor/sendgrid/sendgrid/scripts/generate_upload_policy.php
- > /wp-content/plugins/mail-baby-smtp/inc/templates/Sendin_blue/sendinblue.php
- 333× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\UriInterface' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/guzzlehttp/psr7/src/Uri.php:25
- > PHP Fatal error
Uncaught Error: Class 'WPMailPlus\\Logs' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Sendgrid/views/Logs.php:3
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Formatter\ormalizerFormatter' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/monolog/monolog/src/Monolog/Formatter/LogstashFormatter.php:43
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\TestCase' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/monolog/monolog/tests/Monolog/Handler/TestHandlerTest.php:39
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\TestCase' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/monolog/monolog/tests/Monolog/Handler/ElasticSearchHandlerTest.php:43
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/monolog/monolog/src/Monolog/Handler/IFTTTHandler.php:53
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\TestCase' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/monolog/monolog/tests/Monolog/Handler/PsrHandlerTest.php:39
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/google/auth/tests/BaseTest.php:13
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/guzzlehttp/promises/src/EachPromise.php:15
- > PHP Fatal error
Uncaught Error: Class 'Google\\Auth\\CredentialsLoader' not found in wp-content/plugins/mail-baby-smtp/inc/templates/Gmail/google-api-php-client/vendor/google/auth/src/Credentials/AppIdentityCredentials.php:103
- > 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 issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Contributors: Plugin contributors field is missing
- Tags: Too many tags (18 tag instead of maximum 10); only the first 5 tags are used in your directory listing
mail-baby-smtp/mail-baby-smtp.php 92% from 13 tests
This is the main PHP file of "Mail Baby SMTP" version 2.6, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Description: The description should be shorter than 140 characters (currently 436 characters long)
Code Analysis 97% from 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
Success! There were no dangerous files found in this plugin132,490 lines of code in 601 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 447 | 17,415 | 29,168 | 62,091 |
CSS | 28 | 4,106 | 173 | 42,637 |
JavaScript | 22 | 4,234 | 1,913 | 14,307 |
Markdown | 34 | 3,059 | 0 | 8,445 |
JSON | 17 | 1 | 0 | 1,201 |
Sass | 13 | 19 | 22 | 1,158 |
LESS | 13 | 19 | 31 | 1,149 |
SVG | 12 | 0 | 0 | 743 |
HTML | 6 | 4 | 0 | 555 |
YAML | 3 | 6 | 0 | 91 |
Bourne Shell | 2 | 13 | 3 | 63 |
XML | 3 | 3 | 0 | 41 |
make | 1 | 4 | 0 | 9 |
PHP code 50% from 2 tests
Analyzing cyclomatic complexity and code structure
Please tend to the following items
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 104)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.29 |
Average class complexity | 15.39 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 592.00 |
Average method complexity | 2.86 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 104.00 |
Code structure | ||
---|---|---|
Namespaces | 42 | |
Interfaces | 26 | |
Traits | 5 | |
Classes | 416 | |
▷ Abstract classes | 10 | 2.40% |
▷ Concrete classes | 406 | 97.60% |
▷ Final classes | 9 | 2.22% |
Methods | 3,584 | |
▷ Static methods | 212 | 5.92% |
▷ Public methods | 3,100 | 86.50% |
▷ Protected methods | 226 | 6.31% |
▷ Private methods | 258 | 7.20% |
Functions | 286 | |
▷ Named functions | 109 | 38.11% |
▷ Anonymous functions | 177 | 61.89% |
Constants | 375 | |
▷ Global constants | 42 | 11.20% |
▷ Class constants | 333 | 88.80% |
▷ Public constants | 333 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
5 PNG files occupy 0.02MB with 0.00MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
inc/assets/img/mailbaby.png | 9.33KB | 4.64KB | ▼ 50.24% |
inc/images/not-connected.png | 2.87KB | 1.89KB | ▼ 34.10% |
inc/assets/css/chosen-sprite@2x.png | 0.72KB | 0.83KB | 0.00% |
inc/assets/css/chosen-sprite.png | 0.53KB | 0.88KB | 0.00% |
inc/images/connected.png | 2.81KB | 1.86KB | ▼ 33.91% |