Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.69ms] Passed 4 tests
This is a short check of server-side resources used by RayPay Payment Gateway for Woocommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.01 | 37.96 ▼6.65 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.38 ▼7.92 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.03 ▼4.14 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 92.45 ▼4.04 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.68 ▼1.70 |
Server storage [IO: ▲0.05MB] [DB: ▲0.07MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 10 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for RayPay Payment Gateway for Woocommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲90 | 13.17 ▼1.21 | 1.85 ▲0.07 | 40.58 ▼4.45 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.86 ▲0.94 | 108.50 ▼5.66 | 39.51 ▼2.60 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.01 ▲0.02 | 39.63 ▲0.69 | 36.66 ▲1.64 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲1 | 23.10 ▼0.05 | 626.05 ▼31.67 | 60.55 ▲2.92 |
| Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.23 ▼0.03 | 93.25 ▼0.32 | 42.41 ▲1.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
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)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Everything seems fine, however this is by no means an exhaustive test
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 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
4 plugin tags: woocommerce, payment, gateway, raypay
raypay-payment-gateway-for-woocommerce/woo-raypay-gateway.php 85% from 13 tests
The main PHP file in "RayPay Payment Gateway for Woocommerce" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("raypay-payment-gateway-for-woocommerce.php" instead of "woo-raypay-gateway.php")
- 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 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin509 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 124 | 177 | 385 |
| PO File | 1 | 39 | 46 | 124 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 23.00 |
| ▷ Minimum class complexity | 23.00 |
| ▷ Maximum class complexity | 23.00 |
| Average method complexity | 3.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 63.64% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 36.36% |
| Functions | 7 | |
| ▷ Named functions | 7 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/logo.png | 7.20KB | 3.59KB | ▼ 50.13% |