Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.02MB] [CPU: ▼308.12ms] Passed 4 tests
Server-side resources used by PeproDev Delivery Stages for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.01 | 54.86 ▼0.69 |
| Dashboard /wp-admin | 3.41 ▲0.00 | 31.13 ▲0.04 |
| Posts /wp-admin/edit.php | 3.65 ▲0.00 | 34.40 ▼2.84 |
| Add New Post /wp-admin/post-new.php | 6.88 ▼0.09 | 102.25 ▼1,228.99 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.00 | 29.09 ▲3.49 |
Server storage [IO: ▲0.43MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 42 new files
Database: no new tables, 2 new options
| New WordPress options |
|---|
| ppwcss-data |
| ppwcss-clearunistall |
Browser metrics Passed 4 tests
This is an overview of browser requirements for PeproDev Delivery Stages for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,763 ▲9 | 15.30 ▼0.82 | 5.67 ▼0.49 | 2.27 ▼0.35 |
| Dashboard /wp-admin | 2,892 ▲34 | 6.21 ▲0.09 | 133.36 ▲3.51 | 223.60 ▼23.19 |
| Posts /wp-admin/edit.php | 2,691 ▼0 | 3.23 ▼0.00 | 61.77 ▼3.92 | 207.61 ▲63.36 |
| Add New Post /wp-admin/post-new.php | 1,668 ▼40 | 18.09 ▼2.21 | 419.99 ▼42.77 | 156.78 ▼57.44 |
| Media Library /wp-admin/upload.php | 1,701 ▲12 | 5.55 ▲0.01 | 138.43 ▲2.16 | 199.36 ▼63.55 |
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
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 2 options in the database
- ppwcss-data
- ppwcss-clearunistall
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
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/pepro-delivery-stages-for-woocommerce/pepro-wc-delivery-stages.php
- > /wp-content/plugins/pepro-delivery-stages-for-woocommerce/include/class-setting.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% 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
9 plugin tags: tracking, delivery status, delivery, shipping tracking, shipping...
pepro-delivery-stages-for-woocommerce/pepro-wc-delivery-stages.php 92% from 13 tests
The main file in "PeproDev Delivery Stages for WooCommerce" v. 1.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("pepro-delivery-stages-for-woocommerce.php" instead of "pepro-wc-delivery-stages.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 plugin4,054 lines of code in 28 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 171 | 131 | 1,465 |
| CSS | 4 | 196 | 10 | 1,137 |
| PHP | 2 | 37 | 251 | 965 |
| PO File | 1 | 137 | 141 | 419 |
| SVG | 17 | 4 | 0 | 63 |
| Markdown | 1 | 2 | 0 | 4 |
| HTML | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 48.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 90.00 |
| Average method complexity | 4.03 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 35.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 | 32 | |
| ▷ Static methods | 5 | 15.62% |
| ▷ Public methods | 31 | 96.88% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 3.12% |
| Functions | 5 | |
| ▷ Named functions | 1 | 20.00% |
| ▷ Anonymous functions | 4 | 80.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