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.06MB] [CPU: ▼2.12ms] Passed 4 tests
This is a short check of server-side resources used by Sanitize DB
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 40.07 ▼1.42 |
Dashboard /wp-admin | 3.37 ▲0.06 | 44.64 ▼2.08 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 46.75 ▼2.89 |
Add New Post /wp-admin/post-new.php | 6.01 ▲0.12 | 94.80 ▲0.43 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 34.64 ▼2.10 |
Sanitize History /wp-admin/admin.php?page=wpsdb-sanitize-history | 3.26 | 32.04 |
History /wp-admin/edit.php?post_type=wpsdb_history | 3.34 | 35.49 |
Add New /wp-admin/post-new.php?post_type=wpsdb_history | 5.99 | 77.05 |
WP Sanitize DB /wp-admin/admin.php?page=wpsdb-dashboard | 3.26 | 33.67 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by Sanitize DB
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,908 ▲173 | 13.87 ▼0.56 | 2.10 ▲0.20 | 42.22 ▼5.12 |
Dashboard /wp-admin | 2,283 ▲95 | 5.30 ▲0.40 | 116.10 ▲11.66 | 43.12 ▲1.12 |
Posts /wp-admin/edit.php | 2,169 ▲80 | 2.50 ▲0.49 | 43.34 ▲4.29 | 35.44 ▲3.36 |
Add New Post /wp-admin/post-new.php | 1,572 ▲53 | 17.62 ▼5.30 | 616.38 ▼0.24 | 53.98 ▼0.26 |
Media Library /wp-admin/upload.php | 1,466 ▲75 | 4.54 ▲0.36 | 97.51 ▼3.56 | 40.55 ▼4.07 |
Sanitize History /wp-admin/admin.php?page=wpsdb-sanitize-history | 1,053 | 2.45 | 49.03 | 31.65 |
History /wp-admin/edit.php?post_type=wpsdb_history | 1,142 | 2.60 | 37.64 | 28.74 |
Add New /wp-admin/post-new.php?post_type=wpsdb_history | 1,543 | 17.08 | 842.89 | 26.67 |
WP Sanitize DB /wp-admin/admin.php?page=wpsdb-dashboard | 911 | 2.09 | 36.71 | 45.00 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
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 take a closer look at the following
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sanitize-db/cpt/wpsdb_history.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sanitize-db/admin/admin.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/sanitize-db/inc/functions.php:34
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please fix the following user-side errors
- 3 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=wpsdb_history
- > Javascript (severe) in unknown
/wp-content/plugins/sanitize-db/assets/loading-bar/loading-bar.min.js?ver=1 0:4236 Uncaught TypeError: Cannot read properties of null (reading 'ldBar')
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
6 plugin tags: sanitize, optimize, speedup, sanitization, database...
sanitize-db/wp-sanitize-db.php 92% from 13 tests
The main file in "Sanitize DB" v. 1.0.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("sanitize-db.php" instead of "wp-sanitize-db.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin1,403 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 21 | 11 | 1,060 |
PHP | 4 | 50 | 40 | 250 |
CSS | 4 | 9 | 1 | 93 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
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 | 9 | |
▷ Named functions | 9 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 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
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/logo.png | 1.30KB | 1.26KB | ▼ 2.56% |