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
Installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼6.34ms] Passed 4 tests
An overview of server-side resources used by WP PagSeguro Payments
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 36.13 ▼3.56 |
| Dashboard /wp-admin | 3.37 ▲0.07 | 43.75 ▼7.73 |
| Posts /wp-admin/edit.php | 3.41 ▲0.05 | 46.57 ▼1.74 |
| Add New Post /wp-admin/post-new.php | 6.05 ▲0.16 | 83.16 ▼10.22 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.09 | 29.96 ▼3.86 |
| Pagamentos via PagSeguro /wp-admin/options-general.php?page=wp-pagseguro-payments/wp-pagseguro-payment.php | 3.27 | 32.30 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 57 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for WP PagSeguro Payments
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 14.78 ▲0.75 | 1.70 ▲0.02 | 44.21 ▼0.18 |
| Dashboard /wp-admin | 2,210 ▲22 | 5.89 ▲0.07 | 105.95 ▼10.90 | 42.69 ▼4.43 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.03 ▲0.03 | 40.45 ▲4.22 | 35.16 ▲0.00 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲3 | 22.96 ▲4.52 | 627.90 ▼1.78 | 60.30 ▲7.34 |
| Media Library /wp-admin/upload.php | 1,389 ▲1 | 4.16 ▼0.07 | 94.45 ▼6.42 | 40.87 ▼4.18 |
| Pagamentos via PagSeguro /wp-admin/options-general.php?page=wp-pagseguro-payments/wp-pagseguro-payment.php | 902 | 2.05 | 21.83 | 30.93 |
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
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
SRP 50% from 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
Almost there! Just fix the following items
- 5× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'PagSeguroCredentials' not found in wp-content/plugins/wp-pagseguro-payments/PagSeguroLibrary/domain/PagSeguroAccountCredentials.class.php:25
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-pagseguro-payments/wp-pagseguro-payment.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/wp-pagseguro-payments/settings.php:39
- > PHP Fatal error
Uncaught Error: Class 'PagSeguroServiceParser' not found in wp-content/plugins/wp-pagseguro-payments/PagSeguroLibrary/parser/PagSeguroPaymentParser.class.php:24
- > PHP Fatal error
Uncaught Error: Class 'PagSeguroServiceParser' not found in wp-content/plugins/wp-pagseguro-payments/PagSeguroLibrary/parser/PagSeguroTransactionParser.class.php:24
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% 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
Attributes that need to be fixed:
- Screenshots: Add images for these screenshots: #1 (Tela de configurações.), #2 (Uso do atalho em uma página de edição de post.)
wp-pagseguro-payments/wp-pagseguro-payment.php 92% from 13 tests
The main PHP script in "WP PagSeguro Payments" version 1.0 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("wp-pagseguro-payments.php" instead of "wp-pagseguro-payment.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected3,758 lines of code in 52 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 50 | 1,016 | 2,746 | 3,721 |
| Markdown | 1 | 17 | 0 | 36 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 10.24 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 74.00 |
| Average method complexity | 2.12 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 53.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 46 | |
| ▷ Abstract classes | 1 | 2.17% |
| ▷ Concrete classes | 45 | 97.83% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 382 | |
| ▷ Static methods | 85 | 22.25% |
| ▷ Public methods | 360 | 94.24% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 22 | 5.76% |
| Functions | 7 | |
| ▷ Named functions | 7 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 2 | 25.00% |
| ▷ Class constants | 6 | 75.00% |
| ▷ Public constants | 6 | 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.13MB with 0.09MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 29.13KB | 8.41KB | ▼ 71.13% |
| screenshot-1.png | 104.43KB | 36.18KB | ▼ 65.35% |