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
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.26ms] Passed 4 tests
Server-side resources used by TSF Multistep Checkout for WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.26 ▼0.51 |
Dashboard /wp-admin | 3.31 ▲0.00 | 46.21 ▼5.11 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.92 ▼4.60 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 90.72 ▼6.80 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.57 ▲0.30 |
Server storage [IO: ▲0.40MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 38 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by TSF Multistep Checkout for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲43 | 14.41 ▲0.04 | 1.60 ▼0.27 | 41.04 ▲0.01 |
Dashboard /wp-admin | 2,209 ▲18 | 4.87 ▼0.07 | 97.69 ▼2.06 | 54.53 ▲12.13 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.00 ▲0.01 | 38.92 ▼4.70 | 35.31 ▲0.09 |
Add New Post /wp-admin/post-new.php | 1,547 ▲14 | 18.18 ▼5.03 | 598.49 ▼35.11 | 74.11 ▲20.67 |
Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.13 ▼0.07 | 94.92 ▼3.41 | 41.94 ▼1.53 |
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
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 79% from 29 tests
readme.txt 88% 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
Attributes that require attention:
- Tags: Please delete some tags, you are using 15 tag instead of maximum 10
- Screenshots: These screenshots need descriptions #1, #1, #10, #11, #12, #13, #14, #2, #2, #3, #3, #4, #4, #5, #5, #6, #7, #8, #9 in tsf-multistep-checkout-for-woocommerce/assets to your readme.txt
tsf-multistep-checkout-for-woocommerce/multistep-checkout-for-woo.php 69% from 13 tests
The principal PHP file in "TSF Multistep Checkout for WooCommerce" v. 1.0 is loaded by WordPress automatically on each request
You should first fix the following items:
- Domain Path: The domain path folder does not exist ("/languages/")
- Description: Keep the plugin description shorter than 140 characters (currently 174 characters long)
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: Name the main plugin file the same as the plugin slug ("tsf-multistep-checkout-for-woocommerce.php" instead of "multistep-checkout-for-woo.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
Good job! No executable or dangerous file extensions detected2,865 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 159 | 15 | 1,151 |
PHP | 6 | 211 | 70 | 973 |
JavaScript | 5 | 149 | 83 | 741 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 23 | |
▷ Named functions | 23 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 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
22 PNG files occupy 0.21MB with 0.10MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/examples/style7_borderBottom.PNG | 9.97KB | 5.75KB | ▼ 42.31% |
assets/images/examples/style5_circle.PNG | 12.65KB | 6.76KB | ▼ 46.60% |
assets/images/examples/style8.PNG | 11.07KB | 6.21KB | ▼ 43.88% |
assets/images/examples/style7_borderTop.PNG | 10.09KB | 5.79KB | ▼ 42.56% |
assets/images/banner.png | 11.25KB | 4.29KB | ▼ 61.92% |