Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼4.95ms] Passed 4 tests
A check of server-side resources used by BayEngage: Email Marketing
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.39 ▼0.07 | 25.91 ▼9.21 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.06 ▲0.69 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.30 ▼4.70 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 89.12 ▼6.44 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.62 ▲0.57 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 23 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for BayEngage: Email Marketing
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,468 ▼294 | 14.29 ▲0.32 | 0.85 ▼0.70 | 15.05 ▼25.36 |
Dashboard /wp-admin | 2,195 ▲27 | 5.62 ▼0.04 | 91.50 ▼4.47 | 43.17 ▲0.34 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 1.96 ▲0.02 | 39.67 ▼0.28 | 37.06 ▲0.63 |
Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 23.48 ▼0.17 | 617.59 ▼30.30 | 57.95 ▲4.05 |
Media Library /wp-admin/upload.php | 1,394 ▼9 | 4.17 ▼0.01 | 97.35 ▼0.31 | 44.90 ▲1.42 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not 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
Please fix the following items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/bayengage-email-marketing/public/partials/email-campaign-automation-public-display.php
- > /wp-content/plugins/bayengage-email-marketing/admin/partials/email-campaign-automation-admin-display.php
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 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
3 plugin tags: ecommerce, email campaign, email automation
bayengage-email-marketing/bayengage-email-campaign-automation.php 92% from 13 tests
The entry point to "BayEngage: Email Marketing" version 1.6.9 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("bayengage-email-marketing.php" instead of "bayengage-email-campaign-automation.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin828 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 292 | 678 | 822 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.18 |
Average class complexity | 6.56 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 39.00 |
Average method complexity | 2.06 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 13.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 9 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 47 | |
▷ Static methods | 1 | 2.13% |
▷ Public methods | 40 | 85.11% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 7 | 14.89% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 10 | |
▷ Global constants | 8 | 80.00% |
▷ Class constants | 2 | 20.00% |
▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin