Benchmarks
Plugin footprint 65% 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.09MB] [CPU: ▼0.29ms] Passed 4 tests
An overview of server-side resources used by Bulk Postmeta Editor
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.10 | 41.11 ▲0.82 |
Dashboard /wp-admin | 3.40 ▲0.09 | 47.36 ▲1.60 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 47.36 ▲1.60 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 81.00 ▼5.16 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 37.42 ▲3.61 |
Bulk Edit /wp-admin/admin.php?page=bulk_edit_list_editables | 3.29 | 30.28 |
Settings /wp-admin/admin.php?page=bulk_edit_admin_settings | 3.29 | 32.55 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 15 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_bulk_edit |
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Bulk Postmeta Editor
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲68 | 13.37 ▼1.43 | 1.77 ▼0.17 | 42.92 ▼1.24 |
Dashboard /wp-admin | 2,234 ▲45 | 4.81 ▼0.13 | 106.83 ▼13.16 | 38.30 ▼8.97 |
Posts /wp-admin/edit.php | 2,117 ▲28 | 2.04 ▼0.01 | 40.73 ▲3.83 | 35.43 ▲1.52 |
Add New Post /wp-admin/post-new.php | 1,558 ▲44 | 18.11 ▲0.21 | 639.36 ▼108.99 | 61.67 ▼1.07 |
Media Library /wp-admin/upload.php | 1,413 ▲28 | 4.20 ▼0.00 | 100.96 ▼9.54 | 43.75 ▼4.12 |
Bulk Edit /wp-admin/admin.php?page=bulk_edit_list_editables | 782 | 2.02 | 23.16 | 24.08 |
Settings /wp-admin/admin.php?page=bulk_edit_admin_settings | 949 | 2.02 | 21.78 | 30.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 1 table in the database
- wp_bulk_edit
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means 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
The SRP test was a success
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 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
Please fix the following attributes:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== bulk-postmeta-editor ===
)
bulk-postmeta-editor/bulk-postmeta-edior.php 85% from 13 tests
The entry point to "Bulk Postmeta Editor" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- 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 ("bulk-postmeta-editor.php" instead of "bulk-postmeta-edior.php")
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 plugin705 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 122 | 384 | 628 |
CSS | 1 | 1 | 0 | 77 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 7.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 39.00 |
Average method complexity | 2.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 34 | |
▷ Static methods | 2 | 5.88% |
▷ Public methods | 19 | 55.88% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 15 | 44.12% |
Functions | 4 | |
▷ Named functions | 4 | 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
PNG images were not found in this plugin