Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▼0.95MB] [CPU: ▼34.79ms] Passed 4 tests
A check of server-side resources used by Disable WordPress Dashboard Widgets
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.49 ▲1.08 |
Dashboard /wp-admin | 3.00 ▼0.31 | 24.27 ▼30.83 |
Posts /wp-admin/edit.php | 3.00 ▼0.36 | 26.05 ▼24.54 |
Add New Post /wp-admin/post-new.php | 3.00 ▼2.89 | 20.29 ▼73.37 |
Media Library /wp-admin/upload.php | 3.00 ▼0.23 | 27.34 ▼10.43 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 6 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_widg_dashboard |
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Disable WordPress Dashboard Widgets
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,466 ▼280 | 14.11 ▼0.15 | 1.66 ▼0.14 | 37.46 ▼2.02 |
Dashboard /wp-admin | 1,872 ▼320 | 5.42 ▲0.53 | 92.55 ▼16.50 | 74.39 ▲30.08 |
Posts /wp-admin/edit.php | 2,107 ▲18 | 1.97 ▼0.19 | 38.37 ▲1.43 | 34.04 ▲0.05 |
Add New Post /wp-admin/post-new.php | 1,680 ▲150 | 22.32 ▲4.31 | 606.40 ▼18.75 | 47.81 ▼6.48 |
Media Library /wp-admin/upload.php | 1,403 ▲18 | 4.22 ▼0.03 | 109.10 ▲5.03 | 61.17 ▲11.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/dashboard-widget-control/trunk/disablewidgets.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/dashboard-widget-control/disablewidgets.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 81% from 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
Attributes that need to be fixed:
- Screenshots: Please a description for screenshot #0 in dashboard-widget-control/assets to your readme.txt
- Plugin Name: You should set the name of your plugin on the first line (
=== dashboard-widget-control ===
) - Screenshots: Screenshot #1 (The Hide WordPress Dashboard Widgets Plugin Interface.) image required
dashboard-widget-control/disablewidgets.php 92% from 13 tests
The principal PHP file in "Disable WordPress Dashboard Widgets" v. 1.5 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("dashboard-widget-control.php" instead of "disablewidgets.php")
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 plugin186 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 34 | 27 | 186 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.09 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 10 | |
▷ Named functions | 10 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 10 | |
▷ Global constants | 10 | 100.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
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/icon.png | 1.55KB | 0.96KB | ▼ 38.08% |
trunk/images/icon.png | 1.55KB | 0.96KB | ▼ 38.08% |