Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼5.07ms] Passed 4 tests
This is a short check of server-side resources used by Stark
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 40.34 ▼4.98 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 50.06 ▼3.75 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 50.88 ▼5.66 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 87.46 ▼5.88 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 33.92 ▼2.12 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
Just a few items left to fix
- Illegal file modification found: 1 file (4.00KB) outside of "wp-content/plugins/accept-crypto-payments-on-woocommerce/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Stark: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲29 | 13.37 ▼1.00 | 4.37 ▲2.19 | 45.54 ▲1.31 |
| Dashboard /wp-admin | 2,221 ▲18 | 5.82 ▼0.08 | 99.36 ▼16.25 | 37.94 ▼4.30 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 2.00 ▲0.01 | 36.09 ▼4.97 | 35.76 ▼0.22 |
| Add New Post /wp-admin/post-new.php | 1,549 ▲14 | 23.26 ▲0.00 | 674.19 ▲45.14 | 62.81 ▲0.69 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.20 ▼0.12 | 96.07 ▼9.13 | 42.93 ▼2.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests Passed 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 Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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 errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4, #5, #6, #7 in accept-crypto-payments-on-woocommerce/assets to your readme.txt
- Requires at least: Invalid version format
- Requires php: Invalid version format
accept-crypto-payments-on-woocommerce/class-wc-gateway-stark.php 92% from 13 tests
"Stark" version 1.0.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("accept-crypto-payments-on-woocommerce.php" instead of "class-wc-gateway-stark.php")
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
There were no executable files found in this plugin199 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 33 | 67 | 177 |
| Markdown | 1 | 6 | 0 | 22 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 7.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 2.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/icons/stark.png | 7.96KB | 3.15KB | ▼ 60.43% |