Benchmarks

Plugin footprint 82% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices

This plugin's installer ran successfully

Server metrics [RAM: ▲0.01MB] [CPU: ▼8.03ms] Passed 4 tests

Analyzing server-side resources used by Custom Status for WooCommerce Orders

Server-side resource usage in normal parameters

Page	Memory (MB)	CPU Time (ms)
Home /	3.48 ▲0.02	36.56 ▼3.64
Dashboard /wp-admin	3.33 ▼0.02	46.94 ▼18.35
Posts /wp-admin/edit.php	3.38 ▲0.02	52.28 ▼1.82
Add New Post /wp-admin/post-new.php	5.91 ▲0.02	89.51 ▼8.32
Media Library /wp-admin/upload.php	3.25 ▲0.02	35.44 ▲1.54
Add custom status /wp-admin/admin.php?page=WCS_add_menu_page	3.22	35.15

Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] 67% from 3 tests

Analyzing filesystem and database footprints of this plugin

Just a few items left to fix

Illegal file modification detected: 1 file (4.00KB) outside of "wp-content/plugins/custom-status-for-wc-orders/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository

Filesystem: 10 new files

Database: no new tables, 6 new options

New WordPress options
widget_theysaidso_widget
theysaidso_admin_options
db_upgraded
can_compress_scripts
widget_recent-posts
widget_recent-comments

Browser metrics Passed 4 tests

This is an overview of browser requirements for Custom Status for WooCommerce Orders

There were no issues detected in relation to browser resource usage

Page	Nodes	Memory (MB)	Script (ms)	Layout (ms)
Home /	2,840 ▲94	13.24 ▼0.90	1.87 ▲0.11	40.15 ▼3.51
Dashboard /wp-admin	2,221 ▲18	5.90 ▼0.14	108.90 ▲8.90	41.08 ▼4.84
Posts /wp-admin/edit.php	2,100 ▼0	2.01 ▲0.02	40.26 ▼0.29	36.80 ▲3.59
Add New Post /wp-admin/post-new.php	1,554 ▼0	18.36 ▲0.32	672.69 ▲18.52	50.04 ▼18.50
Media Library /wp-admin/upload.php	1,400 ▼0	4.23 ▲0.02	101.61 ▼1.23	44.06 ▲0.22
Add custom status /wp-admin/admin.php?page=WCS_add_menu_page	816	2.02	25.26	26.85

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests

🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces

The following items require your attention

Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded

Smoke tests 75% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | This is a short smoke test looking 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

Almost there! Just fix the following items

1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
  Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/custom-status-for-wc-orders/index.php:16

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

The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin

3 plugin tags: woocommerce orders, orders status, custom status

custom-status-for-wc-orders/index.php 85% from 13 tests

The entry point to "Custom Status for WooCommerce Orders" version 1.0 is a PHP file that has certain tags in its header comment area

The following require your attention:

Main file name: It is recommended to name the main PHP file as the plugin slug ("custom-status-for-wc-orders.php" instead of "index.php")
Requires at least: Required version does not match the one declared in readme.txt ("5.5" instead of "5.0")

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files

Everything looks great! No dangerous files found in this plugin302 lines of code in 6 files:

Language	Files	Blank lines	Comment lines	Lines of code
PHP	4	37	18	144
CSS	1	20	0	142
JavaScript	1	4	0	16

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.55
Average class complexity	9.00
▷ Minimum class complexity	7.00
▷ Maximum class complexity	11.00
Average method complexity	2.60
▷ Minimum method complexity	1.00
▷ Maximum method complexity	5.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	10
▷ Static methods	0	0.00%
▷ Public methods	10	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	2
▷ Global constants	2	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

3 PNG files occupy 0.15MB with 0.08MB in potential savings

Potential savings

Compression of 3 random PNG files using pngquant
File	Size - original	Size - compressed	Savings
assets/screenshot-3.png	50.28KB	25.38KB	▼ 49.53%
assets/screenshot-2.png	64.24KB	31.08KB	▼ 51.62%
assets/screenshot-1.png	38.89KB	17.99KB	▼ 53.75%

Code Review | Custom Status for WooCommerce Orders

About plugin

Code review

User reviews

Install metrics