Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.73ms] Passed 4 tests
A check of server-side resources used by Swiss Knife for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.78 ▼3.22 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.72 ▼4.30 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.69 ▲0.15 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 88.94 ▲1.10 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.62 ▼7.55 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 23 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
Browser metrics Passed 4 tests
Swiss Knife for WooCommerce: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,831 ▲74 | 13.30 ▼1.08 | 1.95 ▼0.17 | 40.92 ▼2.43 |
| Dashboard /wp-admin | 2,212 ▲21 | 5.82 ▼0.10 | 100.97 ▼11.22 | 40.22 ▼1.64 |
| Posts /wp-admin/edit.php | 2,095 ▲6 | 2.02 ▲0.02 | 39.38 ▲6.08 | 38.10 ▲3.89 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲12 | 18.44 ▼4.90 | 618.45 ▼44.23 | 62.88 ▲2.85 |
| Media Library /wp-admin/upload.php | 1,394 ▲6 | 4.18 ▼0.13 | 96.92 ▼3.92 | 45.05 ▲0.28 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- 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
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
Please take a closer look at the following
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WPV_SKW\\Base\\Settings' not found in wp-content/plugins/swiss-knife-for-woocommerce/includes/modules/cancel-order/settings.php:10
- > PHP Fatal error
Uncaught Error: Class 'WC_Settings_Page' not found in wp-content/plugins/swiss-knife-for-woocommerce/includes/core/settings.php:10
- > PHP Fatal error
Uncaught Error: Class 'WPV_SKW\\Base\\Settings' not found in wp-content/plugins/swiss-knife-for-woocommerce/includes/modules/repeat-order/settings.php:10
- > PHP Fatal error
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 76% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Screenshots: A description for screenshot #0 is missing in swiss-knife-for-woocommerce/assets to your readme.txt
- Requires php: Invalid version format
swiss-knife-for-woocommerce/swiss-knife-woo.php 62% from 13 tests
Analyzing the main PHP file in "Swiss Knife for WooCommerce" version 0.2
Please make the necessary changes and fix the following:
- Domain Path: The domain path points to a folder that does not exist ("/i18n/languages/")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Requires PHP: Required version number formatted incorrectly (ex. "7.0" instead of "5.6 or higher")
- Requires at least: Required version must be the same as the one declared in readme.txt ("5.0" instead of "5.4")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("swiss-knife-for-woocommerce.php" instead of "swiss-knife-woo.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin1,204 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 18 | 326 | 243 | 1,005 |
| CSS | 1 | 20 | 7 | 101 |
| JavaScript | 1 | 30 | 1 | 51 |
| SVG | 1 | 0 | 1 | 47 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 7.79 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 2.30 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 8 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 14 | |
| ▷ Abstract classes | 1 | 7.14% |
| ▷ Concrete classes | 13 | 92.86% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 75 | |
| ▷ Static methods | 8 | 10.67% |
| ▷ Public methods | 65 | 86.67% |
| ▷ Protected methods | 2 | 2.67% |
| ▷ Private methods | 8 | 10.67% |
| Functions | 3 | |
| ▷ Named functions | 1 | 33.33% |
| ▷ Anonymous functions | 2 | 66.67% |
| Constants | 9 | |
| ▷ Global constants | 9 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected