Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.96ms] Passed 4 tests
Analyzing server-side resources used by JumiaPay For Woocommerce - Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 35.81 ▼7.26 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 48.53 ▼4.75 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.05 ▲3.11 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 84.14 ▼8.21 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 34.16 ▲0.38 |
Server storage [IO: ▲1.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 31 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by JumiaPay For Woocommerce - Payment Gateway
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲43 | 13.24 ▼1.17 | 1.59 ▼0.98 | 42.76 ▼7.20 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.91 ▲0.02 | 110.54 ▼0.20 | 41.22 ▼1.29 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.01 ▼0.03 | 40.67 ▲2.52 | 35.13 ▲2.60 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲4 | 23.32 ▲5.28 | 671.86 ▲10.30 | 57.23 ▲4.12 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▲0.02 | 100.84 ▲2.52 | 41.19 ▼3.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 93% 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
4 plugin tags: payment request, woocommerce, jumiapay, payment gateway
jumiapay-wc/woocommerce-jumiapay.php 85% from 13 tests
"JumiaPay For Woocommerce - Payment Gateway" version 2.0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 204 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("jumiapay-wc.php" instead of "woocommerce-jumiapay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected728 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 156 | 247 | 708 |
| SVG | 1 | 0 | 0 | 20 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 11.29 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 3.06 |
| ▷ 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 | 34 | |
| ▷ Static methods | 4 | 11.76% |
| ▷ Public methods | 25 | 73.53% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 9 | 26.47% |
| Functions | 5 | |
| ▷ Named functions | 3 | 60.00% |
| ▷ Anonymous functions | 2 | 40.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
15 PNG files occupy 0.96MB with 0.57MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-1544x500.png | 327.58KB | 98.97KB | ▼ 69.79% |
| assets/icon-128x128.png | 5.78KB | 2.30KB | ▼ 60.28% |
| assets/image/secured_payfac_ic.png | 7.14KB | 3.45KB | ▼ 51.73% |
| assets/image/secured_payfac_ng.png | 6.06KB | 3.21KB | ▼ 47.10% |
| wordpress_org_assets/banner-772x250.png | 116.04KB | 37.14KB | ▼ 67.99% |