Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.54ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce - PayU Latam Gateway
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.02 ▼2.42 |
Dashboard /wp-admin | 3.31 ▲0.00 | 48.32 ▼1.52 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.07 ▼1.59 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.74 ▼4.64 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.14 ▲1.17 |
Server storage [IO: ▲0.78MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for WooCommerce - PayU Latam Gateway
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲11 | 13.29 ▲0.07 | 1.74 ▲0.10 | 38.62 ▼7.10 |
Dashboard /wp-admin | 2,209 ▼0 | 4.88 ▼0.98 | 97.23 ▼11.61 | 39.80 ▼4.70 |
Posts /wp-admin/edit.php | 2,089 ▲3 | 2.02 ▲0.02 | 33.49 ▼2.09 | 33.25 ▲0.68 |
Add New Post /wp-admin/post-new.php | 1,537 ▲9 | 23.37 ▼0.06 | 622.69 ▼43.61 | 58.92 ▼17.92 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.17 ▼0.10 | 93.24 ▼18.83 | 41.52 ▼7.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
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woocommerce-payu-latam-gateway/woocommerce-gateway-payulatam.php:13
- > PHP Fatal error
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 describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== woocommerce-payu-latam-gateway ===
)
woocommerce-payu-latam-gateway/woocommerce-gateway-payulatam.php 85% from 13 tests
Analyzing the main PHP file in "WooCommerce - PayU Latam Gateway" version 1.2.3
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("woocommerce-payu-latam-gateway.php" instead of "woocommerce-gateway-payulatam.php")
- Description: Keep the plugin description shorter than 140 characters (currently 212 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin1,203 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 114 | 168 | 606 |
PO File | 3 | 176 | 268 | 468 |
Markdown | 1 | 63 | 0 | 129 |
PHP code Passed 2 tests
Analyzing 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.37 |
Average class complexity | 83.00 |
▷ Minimum class complexity | 83.00 |
▷ Maximum class complexity | 83.00 |
Average method complexity | 5.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 21.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 | 18 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 18 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 6 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
12 PNG files occupy 0.48MB with 0.28MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/payulogo.png | 6.30KB | 2.39KB | ▼ 61.97% |
assets/img/payulogoAR.png | 34.08KB | 12.91KB | ▼ 62.11% |
assets/screenshot-1.png | 137.31KB | 50.21KB | ▼ 63.44% |
assets/img/logo.png | 4.84KB | 3.07KB | ▼ 36.71% |
assets/screenshot-3.png | 93.15KB | 33.54KB | ▼ 63.99% |