Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.83ms] Passed 4 tests
This is a short check of server-side resources used by WooCommerce Backorder Report
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.16 ▼1.39 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 44.83 ▲0.14 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 43.90 ▲0.67 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 79.92 ▼20.22 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.16 ▼1.85 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
WooCommerce Backorder Report: 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,800 ▲54 | 13.19 ▼1.39 | 1.69 ▼0.03 | 41.76 ▼2.42 |
| Dashboard /wp-admin | 2,209 ▲24 | 5.85 ▼0.03 | 100.02 ▼9.83 | 41.59 ▲0.54 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▲0.01 | 34.16 ▲1.21 | 33.60 ▼4.11 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.42 ▲0.13 | 664.48 ▼9.29 | 55.84 ▼3.22 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.23 ▲0.04 | 96.32 ▼21.59 | 45.03 ▼3.84 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 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
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/woocommerce-backorders-report/woocommerce-backorders-report.php:60
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: stock, reports, woocommerce, management, backoders
woocommerce-backorders-report/woocommerce-backorders-report.php Passed 13 tests
The main PHP script in "WooCommerce Backorder Report" version 1.0.1 is automatically included on every request by WordPress
56 characters long description:
Show a of backordered items in the WooCommerce Dashboard
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected179 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 63 | 71 | 179 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 12.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 2.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 13 | |
| ▷ Static methods | 1 | 7.69% |
| ▷ Public methods | 9 | 69.23% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 30.77% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.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
PNG images were not found in this plugin