Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼10.13ms] Passed 4 tests
An overview of server-side resources used by Windzfare: Woocommerce based fundraising plugin
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.08 | 37.07 ▼0.79 |
Dashboard /wp-admin | 3.38 ▲0.04 | 45.97 ▼14.43 |
Posts /wp-admin/edit.php | 3.50 ▲0.14 | 44.87 ▼6.49 |
Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 79.82 ▼18.82 |
Media Library /wp-admin/upload.php | 3.31 ▲0.07 | 37.43 ▲1.70 |
Server storage [IO: ▲3.32MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 79 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
windzfare_installed |
can_compress_scripts |
windzfare_version |
Browser metrics Passed 4 tests
Windzfare: Woocommerce based fundraising plugin: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲45 | 14.33 ▲0.04 | 1.62 ▼0.03 | 44.12 ▲6.49 |
Dashboard /wp-admin | 2,206 ▲26 | 5.56 ▼0.05 | 87.94 ▼1.39 | 40.64 ▼6.91 |
Posts /wp-admin/edit.php | 2,117 ▲17 | 1.95 ▼0.03 | 36.74 ▼5.40 | 29.60 ▼9.31 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 23.26 ▲0.15 | 634.67 ▼51.43 | 53.32 ▼8.90 |
Media Library /wp-admin/upload.php | 1,417 ▲17 | 4.25 ▲0.09 | 99.98 ▼5.72 | 42.61 ▼0.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- windzfare_version
- windzfare_installed
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however 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× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/windzfare/includes/Cptui/Init.php
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Tags: Please delete some tags, you are using 26 tag instead of maximum 10
windzfare/windzfare.php Passed 13 tests
Analyzing the main PHP file in "Windzfare: Woocommerce based fundraising plugin" version 1.0.6
50 characters long description:
Windzfare is woocommerce based fundraising plugin.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected40,748 lines of code in 57 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
Sass | 20 | 2,007 | 58 | 15,478 |
CSS | 4 | 2,325 | 118 | 13,827 |
JavaScript | 6 | 1,635 | 2,894 | 6,478 |
SVG | 2 | 0 | 3 | 2,772 |
PHP | 23 | 462 | 232 | 2,171 |
JSON | 2 | 1 | 0 | 22 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 14.47 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 53.00 |
Average method complexity | 3.08 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 8 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 17 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 17 | 100.00% |
▷ Final classes | 1 | 5.88% |
Methods | 111 | |
▷ Static methods | 52 | 46.85% |
▷ Public methods | 108 | 97.30% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 2.70% |
Functions | 4 | |
▷ Named functions | 2 | 50.00% |
▷ Anonymous functions | 2 | 50.00% |
Constants | 18 | |
▷ Global constants | 16 | 88.89% |
▷ Class constants | 2 | 11.11% |
▷ Public constants | 2 | 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
3 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/fav.png | 0.44KB | 0.44KB | 0.00% |
assets/images/logo-full.png | 5.00KB | 2.69KB | ▼ 46.20% |
assets/images/logo.png | 8.83KB | 3.46KB | ▼ 60.77% |