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.07MB] [CPU: ▼6.47ms] Passed 4 tests
An overview of server-side resources used by TriPay Payment Gateway
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 40.08 ▲0.31 |
| Dashboard /wp-admin | 3.39 ▲0.05 | 48.04 ▼13.57 |
| Posts /wp-admin/edit.php | 3.44 ▲0.08 | 45.85 ▲2.04 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 83.75 ▼13.30 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 35.55 ▲0.70 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 47 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for TriPay Payment Gateway
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.33 ▼1.05 | 1.71 ▼0.20 | 43.92 ▼1.59 |
| Dashboard /wp-admin | 2,203 ▲11 | 5.80 ▼0.12 | 99.29 ▼17.37 | 40.45 ▼1.72 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▼0.00 | 36.62 ▲0.09 | 32.89 ▼3.35 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 22.93 ▲5.45 | 670.28 ▲18.70 | 55.99 ▲3.09 |
| Media Library /wp-admin/upload.php | 1,388 ▲6 | 4.21 ▲0.03 | 94.83 ▼2.16 | 41.54 ▼1.62 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Tags: There are too many tags (19 tag instead of maximum 10)
tripay-payment-gateway/woocommerce-gateway-tripay.php 69% from 13 tests
The main PHP file in "TriPay Payment Gateway" ver. 3.2.7 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Domain Path: The domain path points to a folder that does not exist ("/languages")
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.7" instead of "3.1.0")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("tripay-payment-gateway.php" instead of "woocommerce-gateway-tripay.php")
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
Good job! No executable or dangerous file extensions detected3,158 lines of code in 25 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 25 | 368 | 24 | 3,158 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 8.60 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 74.00 |
| Average method complexity | 3.53 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 33.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 25 | |
| ▷ Abstract classes | 1 | 4.00% |
| ▷ Concrete classes | 24 | 96.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 75 | |
| ▷ Static methods | 21 | 28.00% |
| ▷ Public methods | 74 | 98.67% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 1.33% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
21 PNG files occupy 0.06MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| includes/assets/permata-va.png | 2.64KB | 1.80KB | ▼ 31.84% |
| includes/assets/cc.png | 2.56KB | 1.70KB | ▼ 33.50% |
| (invalid) includes/assets/sampoerna-va.png | 3.30KB | 0.00KB | ▼ 100.00% |
| includes/assets/bni-va.png | 3.08KB | 1.96KB | ▼ 36.39% |
| includes/assets/shopeepay.png | 1.54KB | 1.39KB | ▼ 10.00% |