Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.44ms] Passed 4 tests
Server-side resources used by EngageBay WooCommerce integration
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.48 ▼7.53 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 47.90 ▼0.95 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 43.42 ▼2.90 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.02 ▼2.39 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.86 ▲1.13 |
Server storage [IO: ▲0.36MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 24 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
EngageBay WooCommerce integration: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.37 ▲0.02 | 1.90 ▼0.01 | 45.08 ▲2.75 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.57 ▲0.04 | 95.72 ▼7.64 | 51.59 ▲8.35 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 1.99 ▼0.04 | 35.58 ▼0.86 | 32.47 ▼5.64 |
| Add New Post /wp-admin/post-new.php | 1,528 ▼1 | 23.11 ▼0.19 | 657.72 ▼12.86 | 50.32 ▼2.17 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.26 ▲0.11 | 100.74 ▲1.28 | 43.87 ▲0.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
Smoke tests 75% 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 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/engagebay-woocommerce-addon/engagebay-woocommerce.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: Add an image for screenshot #1 (EngageBay login)
engagebay-woocommerce-addon/engagebay-woocommerce.php 77% from 13 tests
The main PHP file in "EngageBay WooCommerce integration" ver. 4.1.4 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Requires at least: Required version must be the same as the one declared in readme.txt ("3.7" instead of "2.2")
- Main file name: The principal plugin file should be the same as the plugin slug ("engagebay-woocommerce-addon.php" instead of "engagebay-woocommerce.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin2,491 lines of code in 20 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 16 | 298 | 782 | 1,883 |
| CSS | 2 | 33 | 10 | 551 |
| JavaScript | 2 | 5 | 0 | 57 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 15.69 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 2.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 13 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 104 | |
| ▷ Static methods | 30 | 28.85% |
| ▷ Public methods | 104 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 5 | |
| ▷ Named functions | 4 | 80.00% |
| ▷ Anonymous functions | 1 | 20.00% |
| Constants | 4 | |
| ▷ Global constants | 1 | 25.00% |
| ▷ Class constants | 3 | 75.00% |
| ▷ Public constants | 3 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.19MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/engagebay.png | 13.12KB | 4.67KB | ▼ 64.38% |
| (invalid) assets/images/info.png | 177.68KB | 0.00KB | ▼ 100.00% |