Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.26ms] Passed 4 tests
Analyzing server-side resources used by wc-upay-manual-payment-gateway
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 39.04 ▼3.73 |
Dashboard /wp-admin | 3.31 ▲0.00 | 43.85 ▼7.13 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.54 ▼4.75 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 95.32 ▲8.47 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.83 ▼1.41 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for wc-upay-manual-payment-gateway
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.77 ▼0.60 | 1.62 ▼0.32 | 38.02 ▼7.34 |
Dashboard /wp-admin | 2,206 ▲18 | 5.91 ▲0.85 | 100.18 ▼14.94 | 36.39 ▼8.09 |
Posts /wp-admin/edit.php | 2,086 ▼3 | 2.01 ▼0.03 | 35.33 ▼3.69 | 33.80 ▼3.40 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.32 ▲0.23 | 737.19 ▲61.84 | 57.06 ▲2.81 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.21 ▲0.01 | 93.81 ▼18.77 | 42.51 ▼3.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- 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
Good news, no errors were detected
SRP 50% from 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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wc-upay-manual-payment-gateway/upay.php:19
- > PHP Fatal error
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 86% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
5 plugin tags: upay, payment gateway, payment, wp, woocommerce
wc-upay-manual-payment-gateway/upay.php 69% from 13 tests
The primary PHP file in "wc-upay-manual-payment-gateway" version 2.0 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("wc-upay-manual-payment-gateway.php" instead of "upay.php")
- Domain Path: The domain path points to an invalid folder, "/languages" does not exist
- Description: The description should be shorter than 140 characters (currently 350 characters long)
- 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 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin299 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 82 | 63 | 294 |
JavaScript | 1 | 0 | 0 | 5 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 8.00 |
▷ Minimum class complexity | 8.00 |
▷ Maximum class complexity | 8.00 |
Average method complexity | 2.17 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.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 | 6 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 6 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/upay.png | 13.44KB | 3.74KB | ▼ 72.13% |