Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼3.47ms] Passed 4 tests
A check of server-side resources used by Promaker Dashboard
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.56 ▲1.31 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 44.09 ▼16.23 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.48 ▼1.71 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 91.95 ▲3.53 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.89 ▲2.75 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Promaker Dashboard
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,826 ▲80 | 13.56 ▼0.81 | 1.53 ▼0.12 | 41.53 ▼0.19 |
| Dashboard /wp-admin | 2,226 ▲34 | 5.83 ▲0.86 | 99.20 ▼7.75 | 74.19 ▲33.94 |
| Posts /wp-admin/edit.php | 2,124 ▲35 | 2.02 ▲0.02 | 38.59 ▼1.33 | 39.87 ▲7.82 |
| Add New Post /wp-admin/post-new.php | 1,576 ▲57 | 23.24 ▼0.03 | 653.05 ▼21.32 | 67.01 ▲14.30 |
| Media Library /wp-admin/upload.php | 1,411 ▲23 | 4.18 ▲0.01 | 94.06 ▼6.24 | 76.93 ▲30.21 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% 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)
The smoke test was a success, however most plugin functionality was not tested
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 items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/promaker-dashboard/promaker.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
2 plugin tags: promaker ui, promaker
promaker-dashboard/promaker.php 92% from 13 tests
"Promaker Dashboard" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("promaker-dashboard.php" instead of "promaker.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected340 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| Sass | 1 | 0 | 0 | 214 |
| SVG | 1 | 0 | 1 | 84 |
| PHP | 1 | 0 | 18 | 41 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.00 |
| 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 | 7 | |
| ▷ Named functions | 7 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to 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 |
| img/logo.png | 0.93KB | 0.86KB | ▼ 7.66% |