Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼0.81ms] Passed 4 tests
A check of server-side resources used by Bulk Post Status Update
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.09 | 41.46 ▲3.98 |
Dashboard /wp-admin | 3.39 ▲0.09 | 46.02 ▼7.90 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 50.22 ▲2.56 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.11 | 92.65 ▼1.88 |
Media Library /wp-admin/upload.php | 3.31 ▲0.09 | 40.03 ▲7.80 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 22 new files
Database: no new tables, 8 new options
New WordPress options |
---|
wp-bulk-post-status-support-types |
widget_recent-posts |
widget_theysaidso_widget |
wpbpus_remove_on_uninstall |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Bulk Post Status Update
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,903 ▲157 | 13.60 ▼0.78 | 4.94 ▲2.97 | 40.41 ▼7.41 |
Dashboard /wp-admin | 2,226 ▲35 | 5.88 ▲1.01 | 109.18 ▲1.79 | 42.67 ▲2.15 |
Posts /wp-admin/edit.php | 2,132 ▲40 | 2.01 ▲0.01 | 42.10 ▲6.36 | 34.23 ▲0.40 |
Add New Post /wp-admin/post-new.php | 1,531 ▼2 | 23.24 ▼0.02 | 612.58 ▼82.91 | 62.00 ▲9.63 |
Media Library /wp-admin/upload.php | 1,411 ▲23 | 4.21 ▲0.02 | 96.96 ▼2.44 | 41.98 ▲0.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 8 options in the database
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- wp-bulk-post-status-support-types
- wpbpus_remove_on_uninstall
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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 take a closer look at the following
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/bulk-post-status-update/public/partials/wp-bulk-post-status-update-public-display.php
- > /wp-content/plugins/bulk-post-status-update/admin/partials/wp-bulk-post-status-update-admin-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
6 plugin tags: custom post type, post, publish, update status, bulk...
bulk-post-status-update/wp-bulk-post-status-update.php 85% from 13 tests
The entry point to "Bulk Post Status Update" version 1.0.0 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("bulk-post-status-update.php" instead of "wp-bulk-post-status-update.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
There were no executable files found in this plugin407 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 134 | 598 | 360 |
CSS | 2 | 3 | 12 | 41 |
JavaScript | 2 | 4 | 54 | 6 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 5.43 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 26.00 |
Average method complexity | 2.03 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 30 | |
▷ Static methods | 2 | 6.67% |
▷ Public methods | 25 | 83.33% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 16.67% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin