Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.95ms] Passed 4 tests
Analyzing server-side resources used by Filter orders by status
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 40.14 ▼4.48 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 49.54 ▼0.98 |
| Posts /wp-admin/edit.php | 3.38 ▲0.01 | 52.87 ▼4.04 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 99.00 ▲5.38 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.01 | 37.03 ▼2.29 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Filter orders by status
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.39 ▼0.02 | 1.69 ▼0.13 | 37.67 ▼5.75 |
| Dashboard /wp-admin | 2,192 ▲15 | 5.61 ▼0.04 | 87.99 ▼14.23 | 39.33 ▼5.08 |
| Posts /wp-admin/edit.php | 2,097 ▼6 | 2.01 ▲0.02 | 39.10 ▼2.72 | 38.83 ▲1.97 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼8 | 23.42 ▲5.30 | 670.84 ▲3.03 | 62.94 ▼1.14 |
| Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.19 ▼0.04 | 106.50 ▼5.38 | 43.52 ▼1.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== filter-orders-by-status ===)
filter-orders-by-status/orders-by-status.php 85% from 13 tests
The main PHP script in "Filter orders by status" version 1.0 is automatically included on every request by WordPress
You should first fix the following items:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("filter-orders-by-status.php" instead of "orders-by-status.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
No dangerous file extensions were detected69 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 15 | 25 | 69 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.55 |
| Average class complexity | 1.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 1.00 |
| Average method complexity | 1.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 1.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 | 5 | |
| ▷ Static methods | 3 | 60.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.05MB with 0.03MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot.png | 53.61KB | 19.57KB | ▼ 63.49% |