Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.71ms] Passed 4 tests
An overview of server-side resources used by Plug Pagamentos
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 39.27 ▼1.44 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 48.94 ▲0.19 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 48.84 ▼1.99 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 95.45 ▼5.93 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.77 ▼1.47 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 34 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Plug Pagamentos
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲77 | 13.61 ▼0.74 | 1.75 ▲0.03 | 44.06 ▲3.90 |
| Dashboard /wp-admin | 2,221 ▲30 | 4.86 ▼0.01 | 102.35 ▲0.09 | 40.04 ▼2.00 |
| Posts /wp-admin/edit.php | 2,101 ▲12 | 2.02 ▼0.00 | 34.34 ▼10.33 | 35.10 ▼2.08 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲35 | 18.38 ▼4.89 | 590.06 ▼89.00 | 51.38 ▼3.80 |
| Media Library /wp-admin/upload.php | 1,400 ▲12 | 4.25 ▲0.05 | 94.60 ▲1.09 | 40.52 ▼1.88 |
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
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/plug-payments-gateway/templates/payment-types/pix.php
- > /wp-content/plugins/plug-payments-gateway/templates/payment-types/boleto.php
- 10× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/plug-payments-gateway/templates/receipt/boleto.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/plug-payments-gateway/templates/payment-types/credit.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/plug-payments-gateway/templates/admin-page.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/plug-payments-gateway/includes/poedit.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/plug-payments-gateway/templates/notice/missing-ecfb.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/plug-payments-gateway/templates/notice/missing-clientId.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/plug-payments-gateway/includes/configs/boleto.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/plug-payments-gateway/templates/notice/missing-token.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/plug-payments-gateway/templates/receipt/pix.php:28
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/plug-payments-gateway/templates/notice/missing-merchant.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots lack descriptions #1, #2 in plug-payments-gateway/assets to your readme.txt
plug-payments-gateway/woocommerce-plug-payments.php 92% from 13 tests
The main PHP file in "Plug Pagamentos" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("plug-payments-gateway.php" instead of "woocommerce-plug-payments.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected1,118 lines of code in 27 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 20 | 133 | 24 | 831 |
| PO File | 1 | 71 | 80 | 168 |
| Markdown | 2 | 35 | 0 | 61 |
| LESS | 1 | 1 | 0 | 41 |
| JavaScript | 2 | 3 | 0 | 16 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 12.20 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 2.70 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 5 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 5 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 33 | |
| ▷ Static methods | 5 | 15.15% |
| ▷ Public methods | 29 | 87.88% |
| ▷ Protected methods | 1 | 3.03% |
| ▷ Private methods | 3 | 9.09% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/plug-50x23.png | 1.17KB | 0.57KB | ▼ 50.92% |
| assets/images/poweredbyplug.png | 2.19KB | 1.13KB | ▼ 48.64% |
| assets/images/transparent-checkout-icons.png | 14.57KB | 7.22KB | ▼ 50.42% |