Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼8.65ms] Passed 4 tests
Server-side resources used by Bani Payments for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 35.86 ▼2.45 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 42.95 ▼15.41 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.12 ▼5.74 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.92 ▼10.98 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.05 ▲3.32 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Bani Payments for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.23 ▼1.06 | 1.75 ▼0.06 | 42.37 ▲1.66 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.91 ▲0.99 | 106.53 ▼1.80 | 42.58 ▲0.58 |
| Posts /wp-admin/edit.php | 2,086 ▼6 | 2.03 ▲0.01 | 40.36 ▼0.79 | 34.60 ▼3.25 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲23 | 18.65 ▼4.69 | 676.90 ▼4.80 | 59.85 ▲4.64 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.21 ▼0.00 | 92.47 ▼12.32 | 43.84 ▲1.69 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
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
The smoke test was a success, however most plugin functionality was not tested
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 items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/bani-payments-for-woocommerce/includes/class-wc-payment-gateway-bani.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
- Contributors: The plugin contributors field is not present
bani-payments-for-woocommerce/woo-bani.php 92% from 13 tests
The entry point to "Bani Payments for WooCommerce" version 1.0.4 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("bani-payments-for-woocommerce.php" instead of "woo-bani.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected871 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 155 | 168 | 498 |
| JavaScript | 5 | 11 | 8 | 362 |
| SVG | 1 | 0 | 0 | 11 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 57.00 |
| ▷ Minimum class complexity | 57.00 |
| ▷ Maximum class complexity | 57.00 |
| Average method complexity | 4.27 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 23.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 14 | 87.50% |
| ▷ Protected methods | 2 | 12.50% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 5 | |
| ▷ Named functions | 5 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin