Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.76ms] Passed 4 tests
Analyzing server-side resources used by Bulk Remove Users
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.64 ▼4.32 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 51.60 ▲0.41 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.34 ▼6.47 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 83.47 ▼19.03 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.59 ▼1.23 |
| Bulk Remove Users /wp-admin/options-general.php?page=juru_options_page_slug | 3.20 | 28.61 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Bulk Remove Users
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲7 | 14.61 ▲0.02 | 2.04 ▲0.10 | 43.80 ▲3.73 |
| Dashboard /wp-admin | 2,199 ▲19 | 5.59 ▼0.06 | 82.87 ▼8.35 | 43.67 ▼4.36 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 1.99 ▼0.01 | 40.59 ▲2.89 | 37.74 ▲0.43 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.57 ▲0.72 | 659.53 ▲22.67 | 55.90 ▲7.66 |
| Media Library /wp-admin/upload.php | 1,407 ▲4 | 4.18 ▼0.00 | 99.83 ▼5.51 | 41.54 ▼1.42 |
| Bulk Remove Users /wp-admin/options-general.php?page=juru_options_page_slug | 774 | 2.15 | 24.12 | 28.19 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/bulk-remove-users/bulk_remove_users.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Please fix the following attributes:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== bulk-remove-users ===) - Screenshots: These screenshots require images: #1 (Settings->Bulk Remove Users), #2 (Response of those profiles have been deleted.)
bulk-remove-users/bulk_remove_users.php 92% from 13 tests
The primary PHP file in "Bulk Remove Users" version 1.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("bulk-remove-users.php" instead of "bulk_remove_users.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
Everything looks great! No dangerous files found in this plugin52 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 7 | 9 | 52 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.50 |
| Average class complexity | 8.00 |
| ▷ Minimum class complexity | 8.00 |
| ▷ Maximum class complexity | 8.00 |
| Average method complexity | 3.33 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.04MB with 0.03MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 18.67KB | 5.89KB | ▼ 68.48% |
| screenshot-2.png | 21.27KB | 6.86KB | ▼ 67.77% |