Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.38ms] Passed 4 tests
An overview of server-side resources used by Scanpay for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 42.83 ▼2.45 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 50.63 ▼20.45 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 55.85 ▲5.70 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 98.34 ▼7.55 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.01 | 36.69 ▲0.95 |
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: 25 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Scanpay for WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.34 ▼0.01 | 1.72 ▲0.02 | 44.66 ▼1.03 |
| Dashboard /wp-admin | 2,198 ▲24 | 5.63 ▼0.14 | 91.11 ▼10.67 | 45.16 ▼0.96 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 1.98 ▼0.02 | 39.12 ▼0.58 | 35.87 ▲0.64 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 23.23 ▲0.17 | 654.28 ▼6.40 | 55.07 ▲2.45 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.22 ▲0.04 | 101.00 ▼8.62 | 44.72 ▼3.02 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
4 plugin tags: payments, subscriptions, ecommerce, woocommerce
scanpay-for-woocommerce/woocommerce-scanpay.php 77% from 13 tests
The principal PHP file in "Scanpay for WooCommerce" v. 1.3.16 is loaded by WordPress automatically on each request
The following require your attention:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("scanpay-for-woocommerce.php" instead of "woocommerce-scanpay.php")
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.0" instead of "3.0.0")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin1,757 lines of code in 23 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 128 | 98 | 1,565 |
| PO File | 1 | 32 | 37 | 96 |
| SVG | 9 | 3 | 0 | 54 |
| make | 1 | 10 | 5 | 30 |
| diff | 1 | 3 | 11 | 12 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 31.62 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 119.00 |
| Average method complexity | 6.21 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 29.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 1 | 12.50% |
| ▷ Concrete classes | 7 | 87.50% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 47 | |
| ▷ Static methods | 1 | 2.13% |
| ▷ Public methods | 38 | 80.85% |
| ▷ Protected methods | 4 | 8.51% |
| ▷ Private methods | 5 | 10.64% |
| Functions | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 17 | |
| ▷ Global constants | 3 | 17.65% |
| ▷ Class constants | 14 | 82.35% |
| ▷ Public constants | 14 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin