Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼1.68ms] Passed 4 tests
Server-side resources used by WooCommerce Payment Gateway
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 39.36 ▼2.76 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 49.45 ▼3.92 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.04 ▼2.06 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 98.54 ▲2.96 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.26 ▲2.01 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by WooCommerce Payment Gateway
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.42 ▼0.33 | 1.86 ▼0.02 | 45.89 ▲2.67 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.85 ▲0.93 | 112.52 ▲3.03 | 40.52 ▲1.35 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.00 ▲0.02 | 42.34 ▲3.28 | 36.04 ▼2.86 |
| Add New Post /wp-admin/post-new.php | 1,532 ▲12 | 23.46 ▼0.20 | 632.45 ▼17.58 | 51.06 ▼4.51 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.20 ▼0.04 | 105.16 ▼2.47 | 45.46 ▼3.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 8× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wc-jibit-payment-gateway/filters.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/wc-jibit-payment-gateway/templates/payment-form.php:60
- > PHP Warning
Use of undefined constant WC_JIBIT_PAYMENT_GATEWAY_DIR - assumed 'WC_JIBIT_PAYMENT_GATEWAY_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/wc-jibit-payment-gateway/init.php on line 2
- > PHP Warning
require(WC_JIBIT_PAYMENT_GATEWAY_DIR/actions.php): failed to open stream: No such file or directory in wp-content/plugins/wc-jibit-payment-gateway/init.php on line 2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wc-jibit-payment-gateway/actions.php:3
- > PHP Notice
Undefined variable: autoRedirect in wp-content/plugins/wc-jibit-payment-gateway/templates/payment-form.php on line 60
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/wc-jibit-payment-gateway/class-jibit-woocommerce-payment-gateway.php:13
- > PHP Fatal error
require(): Failed opening required 'WC_JIBIT_PAYMENT_GATEWAY_DIR/actions.php' (include_path='.:/usr/share/php') in wp-content/plugins/wc-jibit-payment-gateway/init.php on line 2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: payment gateway, woocommerce, payment
wc-jibit-payment-gateway/wc-jibit-payment-gateway.php 92% from 13 tests
The main file in "WooCommerce Payment Gateway" v. 1.3.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- 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 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected1,038 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 144 | 133 | 904 |
| PO File | 1 | 54 | 56 | 134 |
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.39 |
| Average class complexity | 26.00 |
| ▷ Minimum class complexity | 22.00 |
| ▷ Maximum class complexity | 30.00 |
| Average method complexity | 4.33 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.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 | 15 | |
| ▷ Static methods | 8 | 53.33% |
| ▷ Public methods | 15 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 15 | |
| ▷ Named functions | 14 | 93.33% |
| ▷ Anonymous functions | 1 | 6.67% |
| Constants | 9 | |
| ▷ Global constants | 9 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/logo.png | 3.46KB | 1.82KB | ▼ 47.30% |