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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼10.77ms] Passed 4 tests
This is a short check of server-side resources used by Pago por Redsys
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 43.88 ▼13.20 |
| Dashboard /wp-admin | 3.37 ▲0.02 | 52.65 ▼17.53 |
| Posts /wp-admin/edit.php | 3.42 ▲0.06 | 49.67 ▲0.91 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 89.21 ▼13.24 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 39.58 ▲3.42 |
| TPV Configuration /wp-admin/options-general.php?page=pago-redsys-grafreak | 3.29 | 39.12 |
Server storage [IO: ▲0.30MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Pago por Redsys
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,883 ▲122 | 13.43 ▼0.96 | 8.98 ▲7.05 | 42.51 ▼13.33 |
| Dashboard /wp-admin | 2,203 ▲23 | 5.65 ▲0.01 | 95.93 ▼6.60 | 43.83 ▼0.73 |
| Posts /wp-admin/edit.php | 2,108 ▲8 | 2.01 ▲0.01 | 36.79 ▼2.64 | 35.92 ▲3.35 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 23.00 ▲5.30 | 648.65 ▼10.47 | 59.15 ▲3.37 |
| Media Library /wp-admin/upload.php | 1,405 ▲8 | 4.20 ▼0.03 | 101.25 ▼0.89 | 46.20 ▲1.66 |
| TPV Configuration /wp-admin/options-general.php?page=pago-redsys-grafreak | 1,091 | 2.19 | 23.32 | 28.97 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Warning
Unterminated comment starting line 1 in wp-content/plugins/pago-redsys-tpv-grafreak/admin/index.php on line 1
- > PHP Warning
Unterminated comment starting line 1 in wp-content/plugins/pago-redsys-tpv-grafreak/public/index.php on line 1
- > PHP Warning
Unterminated comment starting line 1 in wp-content/plugins/pago-redsys-tpv-grafreak/includes/index.php on line 1
- > PHP Warning
Unterminated comment starting line 1 in wp-content/plugins/pago-redsys-tpv-grafreak/index.php on line 1
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== pago-redsys-tpv-grafreak ===) - Screenshots: These screenshots have no corresponding images in /assets: #1 (Corresponds screenshot-1.jpg. This is how the contact form is displayed. The title takes it from the h2 styles and the user fills in, if the pre-filled url has not been passed (see the FAQ).), #2 (Corresponds screenshot-2.jpg. We send the user to the Redsys gateway with the order number and the amount to pay.), #3 (Corresponds screenshot-3.jpg. When the payment has been made satisfactorily, the user returns to our page with the order information and the message that we have written.)
pago-redsys-tpv-grafreak/pago-redsys-grafreak.php 85% from 13 tests
"Pago por Redsys" version 1.0.9's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("pago-redsys-tpv-grafreak.php" instead of "pago-redsys-grafreak.php")
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
No dangerous file extensions were detected986 lines of code in 19 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 159 | 815 | 838 |
| JavaScript | 2 | 6 | 20 | 72 |
| PO File | 1 | 20 | 25 | 46 |
| CSS | 2 | 10 | 8 | 30 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| Average class complexity | 5.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 25.00 |
| Average method complexity | 1.46 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 69 | |
| ▷ Static methods | 2 | 2.90% |
| ▷ Public methods | 63 | 91.30% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 8.70% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
5 PNG files occupy 0.21MB with 0.13MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| Screenshot-2.png | 126.48KB | 34.07KB | ▼ 73.06% |
| public/img/img-formaspago.png | 14.32KB | 6.64KB | ▼ 53.62% |
| Screenshot-1.png | 33.77KB | 10.98KB | ▼ 67.48% |
| Screenshot-3.png | 24.80KB | 8.08KB | ▼ 67.40% |
| public/img/ico-payment.png | 14.47KB | 7.96KB | ▼ 45.03% |