Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.11MB] [CPU: ▼4.51ms] Passed 4 tests
Analyzing server-side resources used by UniPAY Payment Gateway For WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.11 | 43.90 ▼3.28 |
| Dashboard /wp-admin | 3.41 ▲0.11 | 55.50 ▲6.34 |
| Posts /wp-admin/edit.php | 3.52 ▲0.17 | 47.04 ▼8.20 |
| Add New Post /wp-admin/post-new.php | 5.99 ▲0.11 | 91.09 ▼8.63 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 36.53 ▲2.07 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 76 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
UniPAY Payment Gateway For WooCommerce: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.42 ▲0.07 | 1.84 ▼0.54 | 46.57 ▲4.62 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.64 ▲0.02 | 94.53 ▲6.24 | 41.90 ▲2.87 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▲0.04 | 36.53 ▼2.65 | 32.72 ▼4.67 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.12 ▼0.62 | 667.20 ▲14.58 | 56.92 ▼19.17 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.12 ▲0.02 | 116.49 ▲12.80 | 45.47 ▼1.61 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% 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
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- db_upgraded
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
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
No browser issues were found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Tags: There are too many tags (12 tag instead of maximum 10)
unipay-payment-gateway-for-woocommerce/woocommerce-unipay.php 77% from 13 tests
The main file in "UniPAY Payment Gateway For WooCommerce" v. 2.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Domain Path: The domain path folder does not exist ("/languages")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("unipay-payment-gateway-for-woocommerce.php" instead of "woocommerce-unipay.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
Everything looks great! No dangerous files found in this plugin808 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 187 | 335 | 735 |
| JavaScript | 1 | 20 | 7 | 73 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 19.33 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 3.39 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 23 | |
| ▷ Static methods | 1 | 4.35% |
| ▷ Public methods | 14 | 60.87% |
| ▷ Protected methods | 9 | 39.13% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 5 | |
| ▷ Named functions | 5 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
70 PNG files occupy 0.15MB with 0.05MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/icons/amex_logo_black_large.png | 1.19KB | 1.47KB | 0.00% |
| assets/images/logo-medium-black-no-amex.png | 1.81KB | 1.03KB | ▼ 42.94% |
| assets/images/logo-small-white-no-amex.png | 1.80KB | 0.95KB | ▼ 47.15% |
| assets/images/icons/qrcode_logo_black_small.png | 0.48KB | 0.37KB | ▼ 22.29% |
| assets/images/logo-large-white-no-amex.png | 3.23KB | 1.55KB | ▼ 51.90% |