Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.08MB] [CPU: ▼3.62ms] Passed 4 tests
Analyzing server-side resources used by Scrape and Debug
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 38.61 ▼1.33 |
Dashboard /wp-admin | 3.39 ▲0.09 | 45.34 ▼4.55 |
Posts /wp-admin/edit.php | 3.50 ▲0.15 | 45.69 ▼3.56 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 81.34 ▼5.02 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 34.70 ▲2.89 |
Scrape and Debug /wp-admin/options-general.php?page=dts-debugger | 3.28 | 30.19 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 18 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Scrape and Debug
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,818 ▲72 | 13.20 ▼1.18 | 4.61 ▲2.75 | 43.61 ▲0.58 |
Dashboard /wp-admin | 2,227 ▲36 | 4.88 ▼0.01 | 103.04 ▼16.32 | 41.28 ▼1.67 |
Posts /wp-admin/edit.php | 2,106 ▲17 | 2.05 ▲0.04 | 35.58 ▼4.78 | 34.87 ▲1.80 |
Add New Post /wp-admin/post-new.php | 1,531 ▲12 | 22.67 ▼0.53 | 697.27 ▲24.45 | 52.50 ▲2.67 |
Media Library /wp-admin/upload.php | 1,406 ▲21 | 4.27 ▲0.07 | 100.01 ▼0.45 | 43.18 ▲0.19 |
Scrape and Debug /wp-admin/options-general.php?page=dts-debugger | 1,058 | 1.71 | 23.52 | 30.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 7× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/dts-debugger/dts-settings.php
- > /wp-content/plugins/dts-debugger/include/metabox.php
- > /wp-content/plugins/dts-debugger/include/settings.php
- > /wp-content/plugins/dts-debugger/include/data.php
- > /wp-content/plugins/dts-debugger/dts-debugger.php
- > /wp-content/plugins/dts-debugger/include/enqueue.php
- > /wp-content/plugins/dts-debugger/include/setup.php
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)
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
Please fix the following attributes:
- Screenshots: Please add descriptions for these screenshots #1, #2, #3, #4 in dts-debugger/assets to your readme.txt
dts-debugger/dts-debugger.php 92% from 13 tests
This is the main PHP file of "Scrape and Debug" version 0.5.6, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 197 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected512 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 161 | 71 | 338 |
CSS | 1 | 21 | 1 | 141 |
JavaScript | 1 | 1 | 1 | 20 |
Markdown | 1 | 12 | 0 | 13 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
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 | 22 | |
▷ Named functions | 20 | 90.91% |
▷ Anonymous functions | 2 | 9.09% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
7 compressed PNG files occupy 0.04MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/facebook.png | 5.40KB | 5.71KB | 0.00% |
images/linkedin.png | 2.67KB | 2.77KB | 0.00% |
images/pagespeed.png | 4.26KB | 4.41KB | 0.00% |
images/google-deprecated.png | 5.53KB | 5.67KB | 0.00% |
images/google.png | 5.20KB | 5.38KB | 0.00% |