Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.12MB] [CPU: ▼8.15ms] Passed 4 tests
Server-side resources used by Woocommerce Gateway Payger
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.11 | 28.61 ▼16.25 |
| Dashboard /wp-admin | 3.43 ▲0.12 | 52.67 ▼2.24 |
| Posts /wp-admin/edit.php | 3.54 ▲0.18 | 47.29 ▼1.49 |
| Add New Post /wp-admin/post-new.php | 6.01 ▲0.12 | 83.58 ▼12.62 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 35.34 ▼0.38 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 34 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| payger_warning_message |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
Browser metrics Passed 4 tests
Woocommerce Gateway Payger: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,463 ▼298 | 14.25 ▼0.15 | 0.67 ▼1.32 | 19.26 ▼24.68 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.52 ▼0.16 | 91.85 ▼10.17 | 41.27 ▼0.91 |
| Posts /wp-admin/edit.php | 2,110 ▲13 | 2.07 ▲0.06 | 36.20 ▼0.61 | 32.98 ▼2.58 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲11 | 23.21 ▼0.32 | 667.14 ▲11.19 | 71.12 ▲21.08 |
| Media Library /wp-admin/upload.php | 1,412 ▲12 | 4.16 ▼0.04 | 96.63 ▼7.09 | 45.97 ▼2.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- The plugin did not uninstall gracefully
- > Warning in wp-content/plugins/woo-gateway-payger/uninstall.php+39
rmdir(wp-content/uploads/payger_tmp/): No such file or directory
- Zombie WordPress options detected upon uninstall: 7 options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- payger_warning_message
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 0% from 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
Almost there! Just fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/woo-gateway-payger/public/partials/pay-modal.php
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Notice
Undefined variable: order_id in wp-content/plugins/woo-gateway-payger/public/partials/pay-modal.php on line 18
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/woo-gateway-payger/includes/class-woocommerce-payger-gateway.php:30
- > PHP Notice
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 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== woo-gateway-payger ===)
woo-gateway-payger/woocommerce-gateway-payger.php 85% from 13 tests
This is the main PHP file of "Woocommerce Gateway Payger" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woo-gateway-payger.php" instead of "woocommerce-gateway-payger.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 check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin2,303 lines of code in 24 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 16 | 455 | 878 | 1,225 |
| JavaScript | 2 | 130 | 68 | 503 |
| CSS | 1 | 61 | 7 | 356 |
| PO File | 1 | 71 | 88 | 151 |
| SVG | 3 | 0 | 3 | 45 |
| JSON | 1 | 1 | 0 | 23 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 12.67 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 48.00 |
| Average method complexity | 2.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 62 | |
| ▷ Static methods | 16 | 25.81% |
| ▷ Public methods | 58 | 93.55% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 6.45% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.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
2 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| public/assets/images/logo_green.png | 4.48KB | 2.45KB | ▼ 45.35% |
| public/assets/images/logo.png | 9.48KB | 6.10KB | ▼ 35.61% |