Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.41ms] Passed 4 tests
An overview of server-side resources used by Blaze Checkout for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.53 ▼5.23 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.77 ▼0.73 |
| Posts /wp-admin/edit.php | 3.42 ▲0.07 | 43.53 ▼4.28 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 94.00 ▼3.26 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 33.54 ▼0.85 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Blaze Checkout for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.24 ▼1.14 | 1.72 ▼1.05 | 44.34 ▼4.79 |
| Dashboard /wp-admin | 2,204 ▲19 | 5.83 ▲0.96 | 100.96 ▼15.36 | 41.89 ▼4.53 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.06 ▲0.04 | 35.90 ▲0.61 | 31.23 ▼6.14 |
| Add New Post /wp-admin/post-new.php | 1,537 ▼5 | 23.36 ▲4.88 | 626.30 ▼32.66 | 57.44 ▼17.26 |
| Media Library /wp-admin/upload.php | 1,395 ▲16 | 4.22 ▼0.02 | 100.02 ▼1.32 | 42.42 ▼3.10 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- 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
Good news, no errors were detected
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
- 7× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'blazeCheckout' not found in wp-content/plugins/blaze-checkout/includes/frontend/frontendScript.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/admin/orderExport.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/admin/customer-settings.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/frontend/cart.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/frontend/singleProduct.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/admin/menu.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/blaze-checkout/includes/admin/order.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Tags: There are too many tags (19 tag instead of maximum 10)
blaze-checkout/blaze-Checkout.php 85% from 13 tests
Analyzing the main PHP file in "Blaze Checkout for WooCommerce" version 1.0.1
You should first fix the following items:
- Description: Please keep the plugin description shorter than 140 characters (currently 317 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("blaze-checkout.php" instead of "blaze-Checkout.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin920 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 166 | 276 | 871 |
| JavaScript | 2 | 5 | 0 | 34 |
| JSON | 1 | 0 | 0 | 12 |
| CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 6.00 |
| Average method complexity | 1.28 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.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 | 18 | |
| ▷ Static methods | 2 | 11.11% |
| ▷ Public methods | 18 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 32 | |
| ▷ Named functions | 32 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.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
There were not PNG files found in your plugin