Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼7.54ms] Passed 4 tests
A check of server-side resources used by Woo-Divi
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 40.90 ▼2.57 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 49.09 ▼18.34 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.63 ▼0.34 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 89.75 ▼6.88 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.17 ▼2.35 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 24 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
Woo-Divi: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲69 | 13.27 ▼1.41 | 4.79 ▲2.95 | 45.90 ▲2.11 |
| Dashboard /wp-admin | 2,224 ▲21 | 4.84 ▼0.23 | 106.72 ▼7.68 | 42.27 ▲3.71 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.01 | 38.85 ▼1.30 | 35.24 ▼2.73 |
| Add New Post /wp-admin/post-new.php | 1,532 ▼8 | 21.13 ▲2.94 | 722.05 ▲83.45 | 70.06 ▲16.64 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.28 ▼0.03 | 101.19 ▼1.07 | 44.91 ▼2.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- 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
Everything seems fine, however 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
The following issues need your attention
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/woo-divi/public/partials/woodivi-public-display.php
- > /wp-content/plugins/woo-divi/admin/partials/woodivi-admin-display.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'ET_Builder_Module' not found in wp-content/plugins/woo-divi/admin/class-woodivi-custom-module.php:2
- > PHP Fatal error
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 87% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need to be fixed:
- Requires at least: Invalid version format
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== woo-divi ===)
woo-divi/woodivi.php 85% from 13 tests
"Woo-Divi" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("woo-divi.php" instead of "woodivi.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin855 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 13 | 126 | 535 | 447 |
| CSS | 2 | 1 | 8 | 384 |
| JavaScript | 2 | 4 | 54 | 22 |
| Markdown | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 19.00 |
| Average method complexity | 2.33 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 30 | |
| ▷ Static methods | 2 | 6.67% |
| ▷ Public methods | 25 | 83.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 16.67% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
There are no PNG files in this plugin