Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.07ms] Passed 4 tests
Server-side resources used by Product Sales Report for WooCommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.86 ▲1.69 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.16 ▼4.52 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 45.42 ▼5.36 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 89.34 ▼18.58 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 35.31 ▲0.19 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 27 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
Product Sales Report for WooCommerce: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲43 | 13.24 ▼1.14 | 1.75 ▼0.16 | 46.98 ▲0.80 |
Dashboard /wp-admin | 2,209 ▲18 | 5.90 ▼0.00 | 96.48 ▼7.50 | 37.78 ▼0.11 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.00 ▲0.02 | 33.77 ▼7.43 | 33.46 ▼2.10 |
Add New Post /wp-admin/post-new.php | 1,514 ▼8 | 17.54 ▼5.69 | 675.61 ▲65.21 | 55.90 ▼6.67 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.26 ▲0.04 | 103.65 ▲6.09 | 44.58 ▼0.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 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 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
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function load_theme_textdomain() in wp-content/plugins/product-sales-report-for-woocommerce/hm-product-sales-report.php:48
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: A description for screenshot #3 is required in product-sales-report-for-woocommerce/assets to your readme.txt
product-sales-report-for-woocommerce/hm-product-sales-report.php 92% from 13 tests
The principal PHP file in "Product Sales Report for WooCommerce" v. 1.5.6 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("product-sales-report-for-woocommerce.php" instead of "hm-product-sales-report.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected2,971 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 218 | 104 | 1,173 |
CSS | 3 | 72 | 33 | 881 |
JavaScript | 3 | 153 | 109 | 881 |
SVG | 6 | 0 | 2 | 36 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.60 |
Average class complexity | 43.00 |
▷ Minimum class complexity | 11.00 |
▷ Maximum class complexity | 75.00 |
Average method complexity | 17.80 |
▷ Minimum method complexity | 4.00 |
▷ Maximum method complexity | 71.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 5 | |
▷ Static methods | 4 | 80.00% |
▷ Public methods | 5 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 17 | |
▷ Named functions | 17 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 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
3 PNG files occupy 0.14MB with 0.03MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/scheduled-email-reports.png | 61.36KB | 31.50KB | ▼ 48.67% |
images/frontend-report-for-woocommerce.png | 34.89KB | 36.29KB | 0.00% |
images/product_sales_report_pro.png | 43.02KB | 31.27KB | ▼ 27.31% |