Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼10.16MB] [CPU: ▼2,091,054.91ms] Passed 4 tests
Analyzing server-side resources used by CM Commerce for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.02 | 43.61 ▼1.06 |
Dashboard /wp-admin | 3.38 ▼40.73 | 48.60 ▼8,364,201.95 |
Posts /wp-admin/edit.php | 3.49 ▲0.09 | 54.73 ▲2.29 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.02 | 87.60 ▼17.30 |
Media Library /wp-admin/upload.php | 3.30 ▲0.02 | 39.70 ▲0.66 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 26 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for CM Commerce for WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲43 | 14.33 ▲0.06 | 1.75 ▼0.07 | 41.17 ▼6.16 |
Dashboard /wp-admin | 2,198 ▲21 | 5.58 ▼0.02 | 91.19 ▼3.41 | 38.24 ▼6.62 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 1.97 ▼0.05 | 39.17 ▼0.07 | 35.63 ▼0.07 |
Add New Post /wp-admin/post-new.php | 1,535 ▲5 | 18.28 ▼5.07 | 640.39 ▼52.76 | 66.98 ▲15.66 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.22 ▲0.03 | 97.29 ▼11.79 | 42.81 ▼2.75 |
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
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/receiptful-for-woocommerce/includes/emails/class-receiptful-email-customer-new-order.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% 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 need to be fixed:
- Tags: Too many tags (14 tag instead of maximum 10); only the first 5 tags are used in your directory listing
receiptful-for-woocommerce/receiptful-woocommerce.php 77% from 13 tests
The primary PHP file in "CM Commerce for WooCommerce" version 1.6.7 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("receiptful-for-woocommerce.php" instead of "receiptful-woocommerce.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.0.0" instead of "3.4.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Success! There were no dangerous files found in this plugin2,611 lines of code in 24 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 19 | 929 | 1,444 | 2,330 |
Sass | 1 | 24 | 43 | 113 |
PO File | 1 | 26 | 26 | 96 |
JavaScript | 2 | 20 | 9 | 71 |
CSS | 1 | 0 | 0 | 1 |
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.44 |
Average class complexity | 22.31 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 63.00 |
Average method complexity | 3.66 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 20.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 13 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 13 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 103 | |
▷ Static methods | 2 | 1.94% |
▷ Public methods | 97 | 94.17% |
▷ Protected methods | 4 | 3.88% |
▷ Private methods | 2 | 1.94% |
Functions | 27 | |
▷ Named functions | 24 | 88.89% |
▷ Anonymous functions | 3 | 11.11% |
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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
PNG images were not found in this plugin