Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.05ms] Passed 4 tests
An overview of server-side resources used by Who Stole the Text Justify Button ?!
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 38.16 ▼2.06 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.98 ▼10.08 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.55 ▲2.78 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.41 ▼16.21 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.10 ▲0.14 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 13 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Who Stole the Text Justify Button ?!
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.36 ▼0.41 | 1.71 ▼0.03 | 43.51 ▲5.99 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.63 ▲0.01 | 95.35 ▲7.71 | 38.51 ▲1.11 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 1.95 ▼0.05 | 37.76 ▲1.46 | 30.93 ▼4.28 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 23.14 ▲0.15 | 598.59 ▼4.08 | 82.64 ▲29.50 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.17 ▼0.07 | 96.73 ▼2.38 | 41.06 ▼2.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Tags: You are using too many tags: 12 tag instead of maximum 10
who-stole-the-text-justify-button/wstjb.php 85% from 13 tests
The primary PHP file in "Who Stole the Text Justify Button ?!" version 1.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: The principal plugin file should be the same as the plugin slug ("who-stole-the-text-justify-button.php" instead of "wstjb.php")
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
Success! There were no dangerous files found in this plugin63 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 1 | 5 | 5 | 37 |
| PHP | 2 | 3 | 24 | 26 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.62 |
| Average class complexity | 5.00 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 5.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
5 PNG files occupy 0.11MB with 0.07MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-772x250.png | 8.40KB | 3.40KB | ▼ 59.47% |
| assets/icon-128x128.png | 5.05KB | 1.91KB | ▼ 62.16% |
| assets/screenshot-1.png | 75.29KB | 21.09KB | ▼ 71.99% |
| assets/icon-256x256.png | 7.92KB | 3.43KB | ▼ 56.74% |
| assets/banner-1544x500.png | 13.17KB | 4.91KB | ▼ 62.74% |