Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼0.67ms] Passed 4 tests
Server-side resources used by PagSeguro International Payment Gateway for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 48.41 ▲6.11 |
Dashboard /wp-admin | 3.31 ▲0.01 | 45.85 ▼4.79 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 45.87 ▲0.54 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.44 ▼1.35 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 36.24 ▲2.92 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 49 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for PagSeguro International Payment Gateway for WooCommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,811 ▲76 | 13.25 ▼1.15 | 5.29 ▲3.28 | 41.76 ▼3.10 |
Dashboard /wp-admin | 2,217 ▲26 | 5.82 ▲0.93 | 95.88 ▼10.10 | 43.94 ▼2.19 |
Posts /wp-admin/edit.php | 2,100 ▲11 | 2.02 ▲0.00 | 39.36 ▼0.28 | 37.43 ▲2.34 |
Add New Post /wp-admin/post-new.php | 1,544 ▲12 | 23.32 ▲0.35 | 607.06 ▼53.09 | 51.25 ▼3.38 |
Media Library /wp-admin/upload.php | 1,399 ▲11 | 4.20 ▼0.18 | 94.47 ▼7.05 | 43.36 ▼1.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
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)
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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Screenshots: Add descriptions for screenshots #1, #2, #3, #4 in pagseguro-internacional-payment-gateway-for-woocommerce/assets to your readme.txt
pagseguro-internacional-payment-gateway-for-woocommerce/pagseguro-internacional-payment-gateway-for-woocommerce.php 77% from 13 tests
The primary PHP file in "PagSeguro International Payment Gateway for WooCommerce" version 1.0.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Requires at least: Required version must match the one declared in readme.txt ("6.0" instead of "3.0.0")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 252 characters long)
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected3,723 lines of code in 43 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 31 | 1,270 | 979 | 2,271 |
PO File | 2 | 276 | 546 | 707 |
JavaScript | 6 | 159 | 104 | 589 |
Markdown | 1 | 66 | 0 | 79 |
CSS | 3 | 15 | 1 | 77 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 24.10 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 136.00 |
Average method complexity | 3.26 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 102 | |
▷ Static methods | 4 | 3.92% |
▷ Public methods | 93 | 91.18% |
▷ Protected methods | 8 | 7.84% |
▷ Private methods | 1 | 0.98% |
Functions | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 1 | 33.33% |
▷ Class constants | 2 | 66.67% |
▷ Public constants | 2 | 100.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/img/pagseguro.png | 4.16KB | 2.16KB | ▼ 48.11% |
assets/img/paypal.png | 3.69KB | 1.77KB | ▼ 52.08% |