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.01MB] [CPU: ▼2.59ms] Passed 4 tests
Analyzing server-side resources used by Debug Printr
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 36.32 ▼4.78 |
Dashboard /wp-admin | 3.31 ▲0.01 | 47.21 ▲0.02 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.89 ▼2.57 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 94.52 ▼3.02 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.92 ▲1.50 |
Debug PrintR /wp-admin/options-general.php?page=debug-printr | 3.20 | 29.46 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
debug_users |
debug_ips |
can_compress_scripts |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Debug Printr: 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,804 ▲69 | 14.48 ▲0.10 | 1.70 ▼0.08 | 41.56 ▼3.29 |
Dashboard /wp-admin | 2,204 ▲13 | 5.84 ▲0.93 | 108.88 ▼4.30 | 40.18 ▼2.21 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.17 ▼0.01 | 38.66 ▼1.81 | 35.25 ▼2.42 |
Add New Post /wp-admin/post-new.php | 1,547 ▲12 | 22.98 ▼0.21 | 598.52 ▼90.82 | 53.40 ▼11.67 |
Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.23 ▼0.00 | 101.44 ▲1.48 | 44.21 ▼0.93 |
Debug PrintR /wp-admin/options-general.php?page=debug-printr | 831 | 2.02 | 24.20 | 25.29 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 8 options in the database
- debug_ips
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- debug_users
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means 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
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/debug-printr/plugin.php:33
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need your attention:
- Screenshots: Add images for these screenshots: #1 (Example of: global $post; debug::print_r($post);), #2 (Add each IP or Hostname on its' own line.)
debug-printr/plugin.php 92% from 13 tests
Analyzing the main PHP file in "Debug Printr" version 1.4.2
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("debug-printr.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected109 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 16 | 35 | 109 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.60 |
Average class complexity | 27.00 |
▷ Minimum class complexity | 27.00 |
▷ Maximum class complexity | 27.00 |
Average method complexity | 4.25 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.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 | 8 | |
▷ Static methods | 2 | 25.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 2 | 100.00% |
▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 19.51KB | 8.50KB | ▼ 56.41% |
assets/screenshot-2.png | 7.07KB | 4.38KB | ▼ 38.04% |