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: ▲0.04MB] [CPU: ▼3.31ms] Passed 4 tests
An overview of server-side resources used by Bransfer Payment Gateway
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 36.67 ▲1.26 |
| Dashboard /wp-admin | 3.35 ▲0.04 | 46.51 ▼3.19 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 47.66 ▼1.72 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 79.43 ▼8.11 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 34.19 ▼0.20 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Bransfer Payment Gateway
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.31 ▼0.98 | 4.22 ▲2.54 | 39.33 ▼2.97 |
| Dashboard /wp-admin | 2,203 ▲18 | 5.84 ▼0.02 | 96.97 ▼3.99 | 38.36 ▼4.31 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.01 | 39.37 ▼1.93 | 35.04 ▼5.54 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲8 | 23.40 ▼0.02 | 684.21 ▲32.78 | 64.23 ▲14.12 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.28 ▲0.12 | 99.24 ▲5.16 | 41.09 ▼2.95 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 86% 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:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== bransfer-crypto-payments-for-woocommerce ===)
bransfer-crypto-payments-for-woocommerce/bransfer-gateway.php 77% from 13 tests
The entry point to "Bransfer Payment Gateway" version 1.0.1 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Domain Path: The domain path points to an invalid folder, "/languages" does not exist
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("bransfer-crypto-payments-for-woocommerce.php" instead of "bransfer-gateway.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
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
There were no executable files found in this plugin320 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 84 | 223 | 320 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 16.00 |
| ▷ Minimum class complexity | 13.00 |
| ▷ Maximum class complexity | 19.00 |
| Average method complexity | 2.15 |
| ▷ 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 | 26 | |
| ▷ Static methods | 1 | 3.85% |
| ▷ Public methods | 12 | 46.15% |
| ▷ Protected methods | 14 | 53.85% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/logo.png | 3.23KB | 1.72KB | ▼ 46.68% |
| assets/logo.png | 3.23KB | 1.72KB | ▼ 46.68% |