Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.78ms] Passed 4 tests
Server-side resources used by Blog Posts Order
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 41.33 ▼2.24 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.49 ▼7.23 |
| Posts /wp-admin/edit.php | 3.37 ▲0.00 | 47.98 ▼5.35 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 85.07 ▼8.31 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 36.81 ▼1.37 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Blog Posts Order: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.35 ▼0.27 | 1.87 ▲0.26 | 44.24 ▼1.74 |
| Dashboard /wp-admin | 2,198 ▲24 | 5.55 ▲0.01 | 92.37 ▼9.94 | 40.05 ▼3.92 |
| Posts /wp-admin/edit.php | 2,114 ▲14 | 2.00 ▲0.02 | 36.13 ▼1.07 | 34.71 ▲0.67 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 23.39 ▼0.18 | 706.01 ▲62.27 | 56.45 ▲4.81 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.25 ▲0.05 | 103.94 ▼10.18 | 42.54 ▼7.34 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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 fix the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_post_type_support() in wp-content/plugins/blog-posts-order/blogpostsorder.php:16
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Please add an image for screenshot #1 (You can apply a numerical value to each of the posts to change their order of appearance on a blog page.)
blog-posts-order/blogpostsorder.php 85% from 13 tests
The entry point to "Blog Posts Order" version 1.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("blog-posts-order.php" instead of "blogpostsorder.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 397 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
Everything looks great! No dangerous files found in this plugin8 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 6 | 19 | 8 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| 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 | 1 | |
| ▷ Named functions | 1 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 2.98KB | 1.86KB | ▼ 37.57% |