Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼138.76ms] Passed 4 tests
This is a short check of server-side resources used by Autoketing for Woocommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.89 ▲0.05 | 35.13 ▲9.29 |
Dashboard /wp-admin | 3.12 ▲0.06 | 51.83 ▲8.41 |
Posts /wp-admin/edit.php | 3.23 ▲0.12 | 48.79 ▲2.40 |
Add New Post /wp-admin/post-new.php | 5.48 ▲0.04 | 89.01 ▼566.29 |
Media Library /wp-admin/upload.php | 3.06 ▲0.06 | 33.26 ▲0.45 |
Server storage [IO: ▲1.13MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 79 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Autoketing for Woocommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,835 ▲239 | 16.34 ▲0.67 | 13.54 ▲2.86 | 50.05 ▼3.70 |
Dashboard /wp-admin | 2,988 ▲57 | 6.12 ▲0.08 | 136.36 ▼7.68 | 137.03 ▲20.82 |
Posts /wp-admin/edit.php | 2,779 ▲40 | 2.73 ▲0.02 | 60.30 ▼3.42 | 90.87 ▼2.48 |
Add New Post /wp-admin/post-new.php | 1,702 ▲19 | 21.22 ▲2.57 | 366.52 ▼10.94 | 103.48 ▼11.78 |
Media Library /wp-admin/upload.php | 1,773 ▼34 | 5.03 ▲0.00 | 136.73 ▼8.05 | 139.11 ▲18.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 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
Almost there! Just fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/bootstrap.php
- 11× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/OptionsTest.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/ClientTest.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_get_current_user() in wp-content/plugins/autoketing-for-woocommerce/templates/autoketing_admin_template.php:2
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/ResponseTest.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/BasicAuthTest.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/RequestTest.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/OAuthTest.php:7
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/autoketing-for-woocommerce/vendor/automattic/woocommerce/tests/WooCommerce/Tests/HttpClient/HttpClientExceptionTest.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/autoketing-for-woocommerce/templates/autoketing-get-config.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/autoketing-for-woocommerce/templates/autoketing-setup-woo-template.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Donate link: Invalid URI ("")
- Screenshots: A description for screenshot #2 is required in autoketing-for-woocommerce/assets to your readme.txt
autoketing-for-woocommerce/autoketing-for-woocommerce.php 85% from 13 tests
"Autoketing for Woocommerce" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: Please keep the plugin description shorter than 140 characters (currently 148 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin4,783 lines of code in 55 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 2 | 403 | 13 | 2,559 |
PHP | 42 | 459 | 886 | 1,929 |
Markdown | 1 | 40 | 0 | 118 |
JSON | 3 | 0 | 0 | 99 |
JavaScript | 3 | 2 | 2 | 31 |
XML | 2 | 1 | 0 | 26 |
YAML | 2 | 6 | 0 | 21 |
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.28 |
Average class complexity | 5.46 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 44.00 |
Average method complexity | 1.82 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 9 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 26 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 26 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 144 | |
▷ Static methods | 19 | 13.19% |
▷ Public methods | 123 | 85.42% |
▷ Protected methods | 20 | 13.89% |
▷ Private methods | 1 | 0.69% |
Functions | 21 | |
▷ Named functions | 16 | 76.19% |
▷ Anonymous functions | 5 | 23.81% |
Constants | 17 | |
▷ Global constants | 11 | 64.71% |
▷ Class constants | 6 | 35.29% |
▷ Public constants | 6 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
15 PNG files occupy 0.95MB with 0.51MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/icons/icon-woo.png | 10.10KB | 6.08KB | ▼ 39.81% |
assets/images/logo/logo.png | 3.81KB | 2.28KB | ▼ 40.04% |
screenshot-2.png | 200.48KB | 48.93KB | ▼ 75.59% |
screenshot-1.png | 654.29KB | 179.92KB | ▼ 72.50% |
assets/images/icons/boots-sale.png | 2.83KB | 1.66KB | ▼ 41.24% |