Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.10MB] [CPU: ▼8.26ms] Passed 4 tests
An overview of server-side resources used by Constructor for SiteOrigin
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 44.84 ▲4.38 |
| Dashboard /wp-admin | 3.40 ▲0.09 | 44.97 ▼4.99 |
| Posts /wp-admin/edit.php | 3.51 ▲0.15 | 49.02 ▼0.55 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.11 | 81.87 ▼26.23 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 32.11 ▼1.25 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 23 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_constructor-siteorigin-panels-post-content |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Constructor for SiteOrigin
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,887 ▲152 | 13.91 ▼0.48 | 8.07 ▲6.40 | 44.41 ▼5.07 |
| Dashboard /wp-admin | 2,213 ▲24 | 5.83 ▼0.08 | 106.66 ▼7.64 | 39.53 ▼0.91 |
| Posts /wp-admin/edit.php | 2,093 ▲1 | 2.06 ▲0.00 | 41.67 ▼13.03 | 34.67 ▼4.56 |
| Add New Post /wp-admin/post-new.php | 1,518 ▼2 | 23.09 ▼0.11 | 648.98 ▲49.05 | 63.03 ▲15.94 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.24 ▲0.03 | 109.42 ▲14.57 | 45.18 ▲3.62 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_constructor-siteorigin-panels-post-content
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
Please take a closer look at the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/constructor-for-siteorigin/public/partials/constructor-siteorigin-public-display.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/constructor-for-siteorigin/includes/class-constructor-siteorigin-widget.php:6
- > 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 87% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Plugin Name: Please specify the plugin name on the first line (
=== constructor-for-siteorigin ===) - Screenshots: A description for screenshot #1 is missing in constructor-for-siteorigin/assets to your readme.txt
constructor-for-siteorigin/constructor-siteorigin.php 85% from 13 tests
"Constructor for SiteOrigin" version 1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("constructor-for-siteorigin.php" instead of "constructor-siteorigin.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 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected321 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 130 | 482 | 315 |
| 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
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 4.38 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 26.00 |
| Average method complexity | 1.93 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 21.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 | 29 | |
| ▷ Static methods | 2 | 6.90% |
| ▷ Public methods | 24 | 82.76% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 17.24% |
| 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected