Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.31MB] [CPU: ▼4.26ms] 75% from 4 tests
Server-side resources used by Email Template Builder
It is recommended to improve the following
- CPU: Total CPU usage should be kept under 500.00ms (currently 504.84ms on /wp-admin/post-new.php?post_type=email_template)
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.76 ▲0.29 | 40.49 ▲0.80 |
| Dashboard /wp-admin | 3.60 ▲0.29 | 52.79 ▼9.58 |
| Posts /wp-admin/edit.php | 3.72 ▲0.36 | 46.82 ▼0.61 |
| Add New Post /wp-admin/post-new.php | 6.26 ▲0.37 | 83.11 ▼7.65 |
| Media Library /wp-admin/upload.php | 3.52 ▲0.29 | 37.40 ▲2.91 |
| Settings /wp-admin/edit.php?post_type=email_template&page=wpbuilder-email-settings | 3.50 | 36.83 |
| Email Templates /wp-admin/edit.php?post_type=email_template | 3.57 | 36.50 |
| Add New /wp-admin/post-new.php?post_type=email_template | 4.11 | 504.84 |
Server storage [IO: ▲1.32MB] [DB: ▲0.05MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 122 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Email Template Builder
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,416 ▲655 | 15.29 ▲0.92 | 1.73 ▼0.19 | 45.24 ▼4.25 |
| Dashboard /wp-admin | 2,804 ▲627 | 5.95 ▲0.28 | 119.47 ▲32.69 | 104.61 ▲60.00 |
| Posts /wp-admin/edit.php | 2,739 ▲636 | 3.50 ▲1.52 | 48.74 ▲8.85 | 80.82 ▲44.10 |
| Add New Post /wp-admin/post-new.php | 2,149 ▲599 | 23.31 ▲4.90 | 645.53 ▲45.34 | 99.93 ▲33.55 |
| Media Library /wp-admin/upload.php | 2,039 ▲636 | 5.27 ▲1.07 | 101.72 ▼0.07 | 104.04 ▲58.80 |
| Settings /wp-admin/edit.php?post_type=email_template&page=wpbuilder-email-settings | 1,465 | 3.25 | 41.15 | 52.05 |
| Email Templates /wp-admin/edit.php?post_type=email_template | 1,714 | 3.41 | 45.33 | 74.31 |
| Add New /wp-admin/post-new.php?post_type=email_template | 3,939 | 7.47 | 163.95 | 115.80 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.05MB] 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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 10× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/woo-checkout-multistep/backend/templates/index.php
- > /wp-content/plugins/woo-checkout-multistep/backend/shortcode.php
- > /wp-content/plugins/woo-checkout-multistep/index.php
- > /wp-content/plugins/woo-checkout-multistep/email-templates/footer.php
- > /wp-content/plugins/woo-checkout-multistep/preview-inner.php
- > /wp-content/plugins/woo-checkout-multistep/frontend/index.php
- > /wp-content/plugins/woo-checkout-multistep/rednumber/check_purchase_code.php
- > /wp-content/plugins/woo-checkout-multistep/backend/ajax.php
- > /wp-content/plugins/woo-checkout-multistep/backend/settings.php
- > /wp-content/plugins/woo-checkout-multistep/backend/index.php
- 16× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Warning
Use of undefined constant BUIDER_EMAIL_PRO_PLUGIN_URL - assumed 'BUIDER_EMAIL_PRO_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/woo-checkout-multistep/preview.php on line 9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/button.php:2
- > PHP Fatal error
Uncaught Error: Class 'Settings_Builder_Email_Backend' not found in wp-content/plugins/woo-checkout-multistep/email-templates/header.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/demo/templates_demo.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/video.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/text.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/image.php:2
- > PHP Warning
Use of undefined constant BUIDER_EMAIL_PRO_PLUGIN_URL - assumed 'BUIDER_EMAIL_PRO_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/woo-checkout-multistep/preview.php on line 10
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/row.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-checkout-multistep/backend/templates/social.php:2
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: Add a description for screenshot #1 in woo-checkout-multistep/assets to your readme.txt
woo-checkout-multistep/index.php 92% from 13 tests
The main file in "Email Template Builder" v. 1.2.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("woo-checkout-multistep.php" instead of "index.php")
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 detected9,300 lines of code in 66 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 17 | 769 | 117 | 5,655 |
| PHP | 24 | 68 | 42 | 1,803 |
| JavaScript | 8 | 203 | 46 | 1,792 |
| SVG | 1 | 22 | 0 | 34 |
| JSON | 16 | 0 | 0 | 16 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| Average class complexity | 7.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 28.00 |
| Average method complexity | 2.24 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 11.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 | 46 | |
| ▷ Static methods | 4 | 8.70% |
| ▷ Public methods | 46 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 21 | |
| ▷ Named functions | 21 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.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
50 PNG files occupy 0.46MB with 0.21MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/social/whatsapp.png | 6.33KB | 2.50KB | ▼ 60.47% |
| images/social/yt_1.png | 2.05KB | 1.38KB | ▼ 33.08% |
| images/youtube-thumb.png | 5.06KB | 1.43KB | ▼ 71.81% |
| images/social/sk_2.png | 2.50KB | 1.49KB | ▼ 40.44% |
| images/smartphone.png | 0.85KB | 0.60KB | ▼ 29.46% |