Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.05MB] [CPU: ▲1.91ms] Passed 4 tests
Analyzing server-side resources used by Scan2Pay for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 40.30 ▲2.81 |
| Dashboard /wp-admin | 3.35 ▲0.05 | 48.76 ▲3.15 |
| Posts /wp-admin/edit.php | 3.40 ▲0.05 | 50.20 ▲1.66 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 100.69 ▲6.17 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 37.13 ▼0.00 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
Scan2Pay for WooCommerce: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.62 ▼0.78 | 4.59 ▲2.83 | 37.17 ▼0.22 |
| Dashboard /wp-admin | 2,206 ▲14 | 5.89 ▲0.98 | 115.30 ▲0.46 | 48.18 ▲5.15 |
| Posts /wp-admin/edit.php | 2,089 ▲11 | 1.99 ▼0.18 | 38.99 ▲3.39 | 34.65 ▲0.64 |
| Add New Post /wp-admin/post-new.php | 1,542 ▲20 | 18.10 ▼5.21 | 599.39 ▼66.59 | 56.39 ▲3.36 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.24 ▲0.04 | 93.99 ▼4.12 | 40.61 ▼2.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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 83% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Contributors: Contributors not specified
- Screenshots: These screenshots need descriptions #1, #2, #3, #4 in scan2pay-alertco-woo/assets to your readme.txt
scan2pay-alertco-woo/woocommerce-gateway-scan2pay.php 77% from 13 tests
Analyzing the main PHP file in "Scan2Pay for WooCommerce" version 2.5.6
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("scan2pay-alertco-woo.php" instead of "woocommerce-gateway-scan2pay.php")
- Description: The description should be shorter than 140 characters (currently 250 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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
Success! There were no dangerous files found in this plugin265 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 116 | 57 | 238 |
| Markdown | 1 | 13 | 0 | 27 |
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.18 |
| Average class complexity | 14.00 |
| ▷ Minimum class complexity | 14.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 2.30 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.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 | 10 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 10 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
9 PNG files occupy 0.15MB with 0.04MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/fav4.png | 1.23KB | 1.18KB | ▼ 4.12% |
| images/fav3.png | 1.72KB | 1.45KB | ▼ 15.69% |
| images/logo_dash.png | 3.12KB | 2.16KB | ▼ 30.75% |
| screenshots/scan2pay-woo2.png | 46.33KB | 12.04KB | ▼ 74.01% |
| images/meu_icon.png | 1.15KB | 1.30KB | 0.00% |