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: ▼11.33ms] Passed 4 tests
An overview of server-side resources used by Woo PayMaya Payment Gateway
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 35.95 ▼8.01 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 45.15 ▼19.76 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 47.67 ▲1.05 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 91.74 ▼14.16 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 33.94 ▼3.39 |
Server storage [IO: ▲0.39MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Woo PayMaya 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.48 ▲0.10 | 1.61 ▼0.10 | 40.96 ▼4.32 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.86 ▼1.00 | 100.78 ▼5.74 | 37.88 ▼7.17 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 1.98 ▼0.07 | 39.87 ▲3.16 | 36.11 ▲4.14 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼5 | 17.49 ▼5.63 | 664.36 ▲4.72 | 66.30 ▲10.90 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.22 ▲0.01 | 97.13 ▼16.78 | 42.45 ▼5.35 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
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
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-paymaya-payment-gateway/wc-paymaya.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: payment gateway, woocommerce, credit card, payment tokenization, paymaya
woo-paymaya-payment-gateway/wc-paymaya.php 85% from 13 tests
This is the main PHP file of "Woo PayMaya Payment Gateway" version 1.6.1, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("woo-paymaya-payment-gateway.php" instead of "wc-paymaya.php")
- Requires at least: Required version must match the one declared in readme.txt ("5.0" instead of "3.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Success! There were no dangerous files found in this plugin1,197 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 380 | 224 | 1,056 |
| JavaScript | 1 | 65 | 19 | 141 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 125.00 |
| ▷ Minimum class complexity | 125.00 |
| ▷ Maximum class complexity | 125.00 |
| Average method complexity | 5.43 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.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 | 28 | |
| ▷ Static methods | 5 | 17.86% |
| ▷ Public methods | 27 | 96.43% |
| ▷ Protected methods | 1 | 3.57% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.15MB with 0.09MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/screenshot-1.png | 152.56KB | 60.47KB | ▼ 60.36% |