Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.73ms] Passed 4 tests
Analyzing server-side resources used by Engage for WooCommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.59 ▼2.14 |
Dashboard /wp-admin | 3.31 ▲0.00 | 47.43 ▼2.35 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.36 ▼3.55 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 96.60 ▼2.67 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 31.85 ▼2.33 |
Server storage [IO: ▲2.73MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 41 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Engage for WooCommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲43 | 14.48 ▲0.19 | 1.82 ▼0.50 | 43.81 ▲0.69 |
Dashboard /wp-admin | 2,200 ▲15 | 5.84 ▼0.02 | 105.01 ▼0.17 | 38.76 ▼1.32 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.07 | 40.59 ▼0.68 | 35.44 ▼3.90 |
Add New Post /wp-admin/post-new.php | 1,534 ▼0 | 22.99 ▼0.17 | 666.72 ▲13.07 | 58.60 ▼17.13 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.18 ▼0.08 | 107.26 ▲8.10 | 47.13 ▲0.33 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- 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
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
Almost there! Just fix the following items
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/engage-by-zubi/views/settings.php:4
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/engage-by-zubi/views/dashboard-notices.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/engage-by-zubi/views/sidebar.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% 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
These attributes need your attention:
- Tags: Please delete some tags, you are using 26 tag instead of maximum 10
engage-by-zubi/ebz.php 85% from 13 tests
The main PHP file in "Engage for WooCommerce" ver. 2023.9.2 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 179 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("engage-by-zubi.php" instead of "ebz.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
There were no executable files found in this plugin4,779 lines of code in 24 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 627 | 483 | 4,131 |
CSS | 4 | 74 | 16 | 450 |
Markdown | 1 | 76 | 0 | 134 |
SVG | 14 | 0 | 0 | 64 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.47 |
Average class complexity | 203.00 |
▷ Minimum class complexity | 48.00 |
▷ Maximum class complexity | 358.00 |
Average method complexity | 7.93 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 61.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 59 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 55 | 93.22% |
▷ Protected methods | 4 | 6.78% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
12 PNG files occupy 2.29MB with 1.14MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-3.png | 253.68KB | 142.77KB | ▼ 43.72% |
views/engage_logo.png | 42.90KB | 20.21KB | ▼ 52.89% |
screenshot-2.png | 299.69KB | 157.07KB | ▼ 47.59% |
screenshot-5.png | 504.79KB | 295.79KB | ▼ 41.40% |
banner-1544x500.png | 450.06KB | 166.38KB | ▼ 63.03% |