Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼7.35ms] Passed 4 tests
A check of server-side resources used by WordPress Move Comments
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.03 | 39.44 ▼2.34 |
| Dashboard /wp-admin | 3.38 ▼0.01 | 50.97 ▼21.25 |
| Posts /wp-admin/edit.php | 3.49 ▲0.10 | 51.16 ▲1.50 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.04 | 107.32 ▼2.78 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.03 | 34.54 ▼3.03 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WordPress Move Comments
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.37 ▲0.04 | 1.64 ▼0.01 | 40.58 ▼6.34 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.62 ▲0.01 | 90.93 ▼9.27 | 41.26 ▼6.34 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.97 ▼0.00 | 39.41 ▲3.64 | 37.95 ▲1.92 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 18.09 ▼4.90 | 611.09 ▼71.03 | 59.61 ▲7.56 |
| Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.24 ▲0.08 | 103.55 ▼14.74 | 45.26 ▼5.74 |
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
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
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 output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/vb-wp-move-comments/vb-wp-move-comments.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Extra fields added to the standard WordPress comment editing screen. screenshot-1.png), #2 (Extra fields added to the Quick Edit form on the main comments page. screenshot2.png)
- Tags: There are too many tags (13 tag instead of maximum 10)
vb-wp-move-comments/vb-wp-move-comments.php 92% from 13 tests
The entry point to "WordPress Move Comments" version 1.0 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 393 characters long)
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 detected210 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 39 | 23 | 210 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| 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 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 25.07KB | 11.94KB | ▼ 52.37% |
| screenshot-1.png | 3.62KB | 1.67KB | ▼ 53.95% |