Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼9.04ms] Passed 4 tests
Analyzing server-side resources used by OnePipe Payment Gateway for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 42.95 ▼2.18 |
| Dashboard /wp-admin | 3.38 ▲0.07 | 45.95 ▼3.10 |
| Posts /wp-admin/edit.php | 3.43 ▲0.07 | 44.89 ▼11.86 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 86.82 ▼19.00 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 40.23 ▲2.61 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
It is recommended to fix the following issues
- The plugin illegally modified 1 file (0.00KB) outside of "wp-content/plugins/onepipe-payment-gateway-for-woocommerce/" and "wp-content/uploads/"
- (new file) "wp-content/plugins/onepipe-payment-gateway-for-woocommerce/assets/icon-128\303\227128.png"
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
OnePipe Payment Gateway for WooCommerce: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲29 | 13.59 ▼0.79 | 1.98 ▼0.20 | 42.02 ▼1.99 |
| Dashboard /wp-admin | 2,221 ▲18 | 5.90 ▼0.12 | 105.03 ▼1.92 | 41.08 ▼0.16 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.04 ▲0.06 | 37.70 ▼3.12 | 33.43 ▼2.98 |
| Add New Post /wp-admin/post-new.php | 1,551 ▲6 | 23.44 ▲0.29 | 660.52 ▲4.31 | 52.57 ▼6.19 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.17 ▼0.14 | 111.41 ▲7.14 | 47.80 ▲3.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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
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 smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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
Attributes that require attention:
- Tags: You are using too many tags: 12 tag instead of maximum 10
onepipe-payment-gateway-for-woocommerce/woo-onepipe.php 92% from 13 tests
Analyzing the main PHP file in "OnePipe Payment Gateway for WooCommerce" version 1.0.0
The following require your attention:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("onepipe-payment-gateway-for-woocommerce.php" instead of "woo-onepipe.php")
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 plugin441 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 65 | 26 | 441 |
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.30 |
| Average class complexity | 46.00 |
| ▷ Minimum class complexity | 46.00 |
| ▷ Maximum class complexity | 46.00 |
| Average method complexity | 6.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 30.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 | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 77.78% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 22.22% |
| 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.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-128×128.png | 7.65KB | 4.07KB | ▼ 46.85% |
| assets/images/logo.png | 1.68KB | 1.78KB | 0.00% |