Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.16ms] Passed 4 tests
An overview of server-side resources used by Woo Total Sales
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 40.95 ▼1.82 |
Dashboard /wp-admin | 3.31 ▲0.00 | 49.04 ▼6.46 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.02 ▼6.34 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 85.24 ▼6.01 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.48 ▲5.24 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 21 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Woo Total Sales
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.28 ▼1.02 | 1.86 ▲0.20 | 47.61 ▲0.11 |
Dashboard /wp-admin | 2,209 ▲21 | 4.85 ▼1.06 | 103.01 ▲1.98 | 39.36 ▼7.24 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▼0.01 | 42.24 ▲2.98 | 33.80 ▲0.18 |
Add New Post /wp-admin/post-new.php | 1,533 ▲10 | 23.23 ▲0.18 | 682.73 ▲36.62 | 52.68 ▼13.14 |
Media Library /wp-admin/upload.php | 1,382 ▼0 | 4.21 ▲0.02 | 97.23 ▼4.81 | 47.35 ▲2.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/woo-total-sales/aankha-woo-total-sales.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
7 plugin tags: reports, woocommerce, total sales, sales overview, shop...
woo-total-sales/aankha-woo-total-sales.php 85% from 13 tests
"Woo Total Sales" version 3.1.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 214 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-total-sales.php" instead of "aankha-woo-total-sales.php")
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
Everything looks great! No dangerous files found in this plugin1,932 lines of code in 15 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 502 | 343 | 1,420 |
CSS | 2 | 129 | 39 | 478 |
JavaScript | 1 | 2 | 0 | 23 |
SVG | 1 | 0 | 0 | 11 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 18.25 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 3.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 54 | |
▷ Static methods | 5 | 9.26% |
▷ Public methods | 50 | 92.59% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 7.41% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 4 | 80.00% |
▷ Class constants | 1 | 20.00% |
▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/empty-clipboard.png | 16.66KB | 6.95KB | ▼ 58.26% |