Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.16ms] Passed 4 tests
Server-side resources used by Payment with Onepay for Woocommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 51.34 ▲6.21 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 50.88 ▼2.79 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.47 ▼2.27 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.78 ▼6.08 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 40.99 ▲2.52 |
Server storage [IO: ▲2.01MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 24 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Payment with Onepay for Woocommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.07 ▼0.28 | 1.85 ▲0.33 | 43.99 ▲2.95 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.63 ▼0.04 | 91.22 ▲3.37 | 39.32 ▼0.84 |
| Posts /wp-admin/edit.php | 2,103 ▼0 | 1.97 ▼0.13 | 34.75 ▼2.10 | 33.12 ▼2.29 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.05 ▼0.07 | 679.10 ▲3.63 | 63.80 ▲0.84 |
| Media Library /wp-admin/upload.php | 1,403 ▼0 | 4.28 ▲0.09 | 99.81 ▼6.02 | 43.78 ▼2.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/onepay-payment-for-woocommerce/includes/class-wc-payment-gateway-onepay.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/onepay-payment-for-woocommerce/includes/onepay-order-statuses.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/onepay-payment-for-woocommerce/includes/onepay-checkout-description-fields.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
3 plugin tags: woocommerce, onepay, paymentgateway
onepay-payment-for-woocommerce/onepay-for-wc.php 92% from 13 tests
The main PHP file in "Payment with Onepay for Woocommerce" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("onepay-payment-for-woocommerce.php" instead of "onepay-for-wc.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 plugin720 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 150 | 43 | 633 |
| CSS | 1 | 11 | 1 | 52 |
| JavaScript | 1 | 16 | 0 | 35 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 53.00 |
| ▷ Minimum class complexity | 53.00 |
| ▷ Maximum class complexity | 53.00 |
| Average method complexity | 3.48 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.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 | 21 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 14 | 66.67% |
| ▷ Protected methods | 1 | 4.76% |
| ▷ Private methods | 6 | 28.57% |
| Functions | 9 | |
| ▷ Named functions | 9 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 0% from 2 tests
Image compression 0% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
16 PNG files occupy 1.96MB with 1.44MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-9.png | 78.12KB | 25.78KB | ▼ 67.00% |
| (invalid) assets/banner-772x250.png | 76.85KB | 0.00KB | ▼ 100.00% |
| assets/screenshot-5.png | 112.45KB | 35.24KB | ▼ 68.66% |
| assets/screenshot-12.png | 104.57KB | 36.37KB | ▼ 65.22% |
| assets/screenshot-3.png | 66.12KB | 22.66KB | ▼ 65.72% |