Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼136.75ms] Passed 4 tests
Analyzing server-side resources used by WP-DB-Table-Editor
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.85 ▲0.13 | 34.15 ▲10.92 |
| Dashboard /wp-admin | 3.07 ▲0.02 | 43.75 ▼2.58 |
| Posts /wp-admin/edit.php | 3.13 ▲0.02 | 49.89 ▲4.87 |
| Add New Post /wp-admin/post-new.php | 5.43 ▼0.00 | 93.15 ▼551.35 |
| Media Library /wp-admin/upload.php | 3.02 ▲0.02 | 32.86 ▲2.07 |
Server storage [IO: ▲4.65MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 383 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
WP-DB-Table-Editor: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,703 ▲107 | 15.93 ▲0.43 | 10.35 ▲1.97 | 42.67 ▼13.57 |
| Dashboard /wp-admin | 2,967 ▲36 | 5.94 ▼0.07 | 142.84 ▼10.25 | 111.45 ▲2.70 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.68 ▼0.01 | 69.82 ▲5.54 | 90.81 ▼5.00 |
| Add New Post /wp-admin/post-new.php | 1,676 ▼2,011 | 19.03 ▲0.64 | 378.96 ▼75.09 | 111.31 ▲2.61 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.04 ▲0.01 | 148.93 ▼11.83 | 114.96 ▼5.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
This plugin's uninstaller ran successfully
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
Even though everything seems fine, this is not an exhaustive test
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
Please fix the following
- 154× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'PHPSQLParser\\processors\\AbstractProcessor' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/processors/LimitProcessor.php:51
- > PHP Fatal error
Uncaught Error: Interface 'PHPSQLParser\\builders\\Builder' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/builders/PositionBuilder.php:53
- > PHP Fatal error
Uncaught Error: Class 'PHPSQLParser\\processors\\AbstractProcessor' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/processors/IntoProcessor.php:42
- > PHP Fatal error
Uncaught Error: Interface 'PHPSQLParser\\builders\\Builder' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/builders/IndexKeyBuilder.php:54
- > PHP Fatal error
Uncaught Error: Interface 'PHPSQLParser\\builders\\Builder' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/builders/ReservedBuilder.php:53
- > PHP Fatal error
Uncaught Error: Class 'PHPSQLParser\\processors\\AbstractProcessor' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/processors/SQLChunkProcessor.php:51
- > PHP Fatal error
Uncaught Error: Class 'PHPSQLParser\\processors\\AbstractProcessor' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/processors/ReferenceDefinitionProcessor.php:42
- > PHP Fatal error
Uncaught Error: Class 'PHPSQLParser\\processors\\AbstractProcessor' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/processors/UnionProcessor.php:51
- > PHP Fatal error
Uncaught Error: Interface 'PHPSQLParser\\builders\\Builder' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/builders/TruncateBuilder.php:52
- > PHP Fatal error
Uncaught Error: Interface 'PHPSQLParser\\builders\\Builder' not found in wp-content/plugins/wp-db-table-editor/php-sql-parser/src/PHPSQLParser/builders/BracketStatementBuilder.php:53
- > 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Contributors: The plugin contributors field is not present
- Screenshots: Screenshot #1 (Here's a screenshot of it in action) image missing
wp-db-table-editor/db-table-editor.php 92% from 13 tests
The main PHP file in "WP-DB-Table-Editor" ver. 1.8.4 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-db-table-editor.php" instead of "db-table-editor.php")
Code Analysis 97% from 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
Everything looks great! No dangerous files found in this plugin97,072 lines of code in 313 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 61 | 15,219 | 11,942 | 70,243 |
| PHP | 176 | 2,082 | 8,447 | 9,545 |
| CSS | 14 | 245 | 178 | 9,112 |
| HTML | 53 | 1,061 | 2 | 7,537 |
| Markdown | 3 | 115 | 0 | 354 |
| PO File | 2 | 30 | 30 | 125 |
| JSON | 2 | 0 | 0 | 79 |
| diff | 1 | 6 | 32 | 72 |
| Bourne Again Shell | 1 | 0 | 0 | 5 |
PHP code 50% from 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
These items need your attention
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 160)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 10.21 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 160.00 |
| Average method complexity | 3.55 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 160.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 7 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 172 | |
| ▷ Abstract classes | 1 | 0.58% |
| ▷ Concrete classes | 171 | 99.42% |
| ▷ Final classes | 1 | 0.58% |
| Methods | 626 | |
| ▷ Static methods | 2 | 0.32% |
| ▷ Public methods | 242 | 38.66% |
| ▷ Protected methods | 379 | 60.54% |
| ▷ Private methods | 5 | 0.80% |
| Functions | 30 | |
| ▷ Named functions | 30 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 85 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 85 | 100.00% |
| ▷ Public constants | 85 | 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
41 compressed PNG files occupy 0.07MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/calendar.png | 0.78KB | 0.83KB | 0.00% |
| assets/images/accept.png | 0.76KB | 0.81KB | 0.00% |
| assets/SlickGrid/images/arrow_right_spearmint.png | 0.13KB | 0.17KB | 0.00% |
| assets/SlickGrid/images/arrow_redo.png | 0.56KB | 0.67KB | 0.00% |
| assets/SlickGrid/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png | 0.20KB | 0.09KB | ▼ 57.49% |