Benchmarks
Plugin footprint 83% 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 gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.48ms] Passed 4 tests
A check of server-side resources used by OPay Payment Gateway for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 39.76 ▼3.03 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 43.37 ▼1.31 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.51 ▲0.96 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.11 ▼14.83 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.35 ▼2.73 |
Server storage [IO: ▲0.37MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 19 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for OPay Payment Gateway for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲90 | 13.22 ▼1.14 | 2.10 ▲0.27 | 42.13 ▼6.01 |
| Dashboard /wp-admin | 2,206 ▲18 | 5.91 ▲0.01 | 101.16 ▼1.35 | 39.54 ▲0.59 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.02 ▼0.03 | 39.37 ▼0.52 | 36.49 ▲2.07 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.47 ▲0.31 | 655.49 ▲8.97 | 61.22 ▼2.66 |
| Media Library /wp-admin/upload.php | 1,385 ▲6 | 4.17 ▼0.02 | 99.55 ▼6.32 | 43.10 ▼4.63 |
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
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
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)
Good news, no errors were detected
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
4 plugin tags: payment, woocommerce, opay, payment gateway
opay-payment-gateway-for-woocommerce/opay_woocommerce.php 92% from 13 tests
The main PHP file in "OPay Payment Gateway for WooCommerce" ver. 2.5.5 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("opay-payment-gateway-for-woocommerce.php" instead of "opay_woocommerce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected1,742 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 119 | 18 | 1,742 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 16.14 |
| ▷ Minimum class complexity | 16.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 3.16 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 49 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 42 | 85.71% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 7 | 14.29% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
10 PNG files occupy 0.30MB with 0.18MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/SHAHRY.png | 33.46KB | 10.55KB | ▼ 68.47% |
| img/BANK_CARD.png | 10.88KB | 4.14KB | ▼ 61.97% |
| img/BANK_CARD_1.png | 8.21KB | 3.46KB | ▼ 57.91% |
| img/RC_CODE.png | 11.38KB | 4.42KB | ▼ 61.19% |
| img/VALU.png | 4.58KB | 2.50KB | ▼ 45.41% |