Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.86ms] Passed 4 tests
A check of server-side resources used by OPay Payment for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 38.37 ▼10.10 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 47.22 ▼2.25 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.91 ▲2.89 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 84.79 ▼5.96 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.80 ▲3.23 |
Server storage [IO: ▲0.67MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for OPay Payment for WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 13.24 ▼1.14 | 1.74 ▼0.60 | 41.16 ▼2.47 |
| Dashboard /wp-admin | 2,212 ▲24 | 5.90 ▼0.01 | 113.59 ▼5.59 | 45.69 ▲0.05 |
| Posts /wp-admin/edit.php | 2,097 ▲11 | 1.99 ▲0.00 | 41.19 ▲1.64 | 37.56 ▲2.80 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲10 | 23.37 ▲5.05 | 610.52 ▼7.47 | 56.15 ▼18.41 |
| Media Library /wp-admin/upload.php | 1,397 ▲12 | 4.31 ▲0.11 | 100.23 ▼2.45 | 45.09 ▲1.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
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
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/woo-opay-payment/lib/class-wc-gateway-opay.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 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
Please fix the following attributes:
- Requires php: The plugin version is formatted incorrectly
- Tags: You are using too many tags: 11 tag instead of maximum 10
woo-opay-payment/integration_plugin.php 85% from 13 tests
The primary PHP file in "OPay Payment for WooCommerce" version 1.3.190829 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("woo-opay-payment.php" instead of "integration_plugin.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin3,361 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 614 | 1,013 | 2,922 |
| SVG | 1 | 14 | 1 | 292 |
| PO File | 1 | 63 | 0 | 147 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 7.58 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 97.00 |
| Average method complexity | 3.07 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 68.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 50 | |
| ▷ Abstract classes | 17 | 34.00% |
| ▷ Concrete classes | 33 | 66.00% |
| ▷ Final classes | 8 | 24.24% |
| Methods | 159 | |
| ▷ Static methods | 24 | 15.09% |
| ▷ Public methods | 119 | 74.84% |
| ▷ Protected methods | 11 | 6.92% |
| ▷ Private methods | 29 | 18.24% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 80 | |
| ▷ Global constants | 4 | 5.00% |
| ▷ Class constants | 76 | 95.00% |
| ▷ Public constants | 76 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon.png | 1.56KB | 1.65KB | 0.00% |