Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.06ms] Passed 4 tests
Server-side resources used by Frontend Dashboard Extra
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 36.91 ▼4.38 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.98 ▼2.83 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.69 ▼8.28 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 99.63 ▼0.73 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.10 ▲2.37 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 17 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Frontend Dashboard Extra
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,826 ▲65 | 14.34 ▼0.01 | 2.43 ▲0.67 | 43.01 ▲1.40 |
| Dashboard /wp-admin | 2,204 ▲27 | 5.51 ▼0.07 | 86.39 ▼5.82 | 42.90 ▼0.87 |
| Posts /wp-admin/edit.php | 2,116 ▲16 | 2.00 ▲0.01 | 39.77 ▼2.29 | 38.10 ▼3.46 |
| Add New Post /wp-admin/post-new.php | 1,540 ▲14 | 23.12 ▼0.49 | 603.09 ▼53.23 | 44.06 ▼12.21 |
| Media Library /wp-admin/upload.php | 1,415 ▲21 | 4.22 ▲0.05 | 101.05 ▼6.31 | 49.22 ▲2.08 |
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
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% 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
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/frontend-dashboard-extra/functions.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
8 plugin tags: file upload, date, color, frontend dashboard extra, dashboard...
frontend-dashboard-extra/frontend-dashboard-extra.php 92% from 13 tests
The principal PHP file in "Frontend Dashboard Extra" v. 1.5.10 is loaded by WordPress automatically on each request
You should first fix the following items:
- 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
There were no executable files found in this plugin966 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 113 | 147 | 949 |
| JavaScript | 1 | 0 | 0 | 17 |
| CSS | 1 | 1 | 0 | 0 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 25.00 |
| ▷ Minimum class complexity | 25.00 |
| ▷ Maximum class complexity | 25.00 |
| Average method complexity | 3.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 10 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 90.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 10.00% |
| Functions | 12 | |
| ▷ Named functions | 11 | 91.67% |
| ▷ Anonymous functions | 1 | 8.33% |
| Constants | 6 | |
| ▷ Global constants | 6 | 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
5 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/inputs/wp_editor.png | 0.60KB | 0.12KB | ▼ 80.75% |
| assets/images/inputs/color.png | 3.46KB | 1.24KB | ▼ 64.17% |
| assets/images/inputs/date.png | 3.64KB | 1.36KB | ▼ 62.76% |
| assets/images/inputs/label.png | 0.95KB | 0.59KB | ▼ 37.65% |
| assets/images/inputs/file.png | 3.42KB | 1.21KB | ▼ 64.78% |