Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.18MB] [CPU: ▼3.73ms] Passed 4 tests
A check of server-side resources used by WP Marvelous Debug
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 37.15 ▼1.74 |
Dashboard /wp-admin | 3.54 ▲0.24 | 51.34 ▲1.71 |
Posts /wp-admin/edit.php | 3.59 ▲0.23 | 58.02 ▲17.31 |
Add New Post /wp-admin/post-new.php | 6.09 ▲0.21 | 92.95 ▼21.03 |
Media Library /wp-admin/upload.php | 3.44 ▲0.21 | 42.18 ▲6.13 |
Debugging /wp-admin/options-general.php?page=wpmd_settings | 3.43 | 40.14 |
Log File /wp-admin/tools.php?page=wpmd_log_file | 3.44 | 43.61 |
Server storage [IO: ▲0.70MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
Just a few items left to fix
- You have illegally modified 1 file (4.23KB) outside of "wp-content/plugins/wp-marvelous-debug/" and "wp-content/uploads/"
- (modified) wp-config.php
Filesystem: 171 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
wpmd_general |
db_upgraded |
theysaidso_admin_options |
wpmd_log |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Marvelous Debug
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,987 ▲241 | 14.89 ▲0.08 | 2.03 ▲0.37 | 42.03 ▼0.58 |
Dashboard /wp-admin | 2,371 ▲180 | 6.63 ▲1.76 | 132.79 ▲25.05 | 38.55 ▼6.27 |
Posts /wp-admin/edit.php | 2,279 ▲187 | 3.53 ▲1.52 | 58.97 ▲15.98 | 32.84 ▼2.45 |
Add New Post /wp-admin/post-new.php | 1,689 ▲147 | 22.82 ▲4.45 | 585.62 ▼76.30 | 31.78 ▼21.79 |
Media Library /wp-admin/upload.php | 1,410 ▲25 | 4.30 ▲0.12 | 85.89 ▼12.28 | 42.59 ▼4.21 |
Debugging /wp-admin/options-general.php?page=wpmd_settings | 1,406 | 3.42 | 53.35 | 31.53 |
Log File /wp-admin/tools.php?page=wpmd_log_file | 1,153 | 3.35 | 41.52 | 27.68 |
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
These items require your attention
- Zombie WordPress options were found after uninstall: 8 options
- widget_theysaidso_widget
- wpmd_general
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- wpmd_log
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 99× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/FuelphpInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/AglInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/SMFInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/PlentymarketsInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/ModxInstaller.php:7
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/MODXEvoInstaller.php:7
- > PHP Fatal error
require_once(): Failed opening required 'wp-content/plugins/wp-marvelous-debug/vendor/tareq1988/wordpress-settings-api-class/example/oop-example.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-marvelous-debug/vendor/tareq1988/wordpress-settings-api-class/plugin.php on line 12
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/OntoWikiInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/PimcoreInstaller.php:4
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/wp-marvelous-debug/vendor/composer/installers/src/Composer/Installers/TuskInstaller.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Screenshots: Please add descriptions for these screenshots #1, #2 in wp-marvelous-debug/assets to your readme.txt
wp-marvelous-debug/wp-marvelous-debug.php 92% from 13 tests
"WP Marvelous Debug" version 1.1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Domain Path: The domain path folder does not exist ("/src/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected5,997 lines of code in 148 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 130 | 924 | 2,238 | 4,840 |
JSON | 10 | 0 | 0 | 727 |
Markdown | 6 | 132 | 0 | 360 |
JavaScript | 2 | 4 | 9 | 70 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 4.72 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 69.00 |
Average method complexity | 2.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 7 | |
Interfaces | 6 | |
Traits | 0 | |
Classes | 116 | |
▷ Abstract classes | 1 | 0.86% |
▷ Concrete classes | 115 | 99.14% |
▷ Final classes | 0 | 0.00% |
Methods | 291 | |
▷ Static methods | 6 | 2.06% |
▷ Public methods | 242 | 83.16% |
▷ Protected methods | 36 | 12.37% |
▷ Private methods | 13 | 4.47% |
Functions | 29 | |
▷ Named functions | 4 | 13.79% |
▷ Anonymous functions | 25 | 86.21% |
Constants | 4 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 4 | 100.00% |
▷ Public constants | 4 | 100.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.39MB with 0.25MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/tareq1988/wordpress-settings-api-class/screenshot-1.png | 389.59KB | 115.93KB | ▼ 70.24% |
vendor/thanks-to-it/wp-settings-api/assets/subsection.png | 8.92KB | 3.73KB | ▼ 58.18% |