Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼2.93ms] Passed 4 tests
Analyzing server-side resources used by ECPay Payment for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 41.97 ▼7.60 |
| Dashboard /wp-admin | 3.34 ▲0.04 | 52.34 ▼1.10 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 55.36 ▼0.67 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 94.15 ▼2.33 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 38.57 ▲2.82 |
Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 21 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by ECPay Payment for WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,809 ▲74 | 13.24 ▼1.50 | 1.83 ▼0.30 | 39.56 ▼2.34 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.85 ▼0.04 | 97.94 ▼14.89 | 38.35 ▼5.08 |
| Posts /wp-admin/edit.php | 2,097 ▲8 | 2.02 ▼0.04 | 42.18 ▼0.36 | 36.65 ▼1.87 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲6 | 23.45 ▲0.04 | 598.05 ▼97.27 | 49.59 ▼4.46 |
| Media Library /wp-admin/upload.php | 1,394 ▲6 | 4.28 ▲0.09 | 98.21 ▼14.12 | 43.31 ▼0.34 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/ecpay-payment-for-woocommerce/includes/class-wc-gateway-ecpay.php:3
- > PHP Fatal error
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)
There were no browser issues found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #2, #3 in ecpay-payment-for-woocommerce/assets to your readme.txt
- Requires php: Invalid plugin version format
ecpay-payment-for-woocommerce/integration_plugin.php 85% from 13 tests
The principal PHP file in "ECPay Payment for WooCommerce" v. 2.0.2106300 is loaded by WordPress automatically on each request
It is important to fix the following:
- Requires at least: Required version does not match the one declared in readme.txt ("4.5" instead of "3.1")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("ecpay-payment-for-woocommerce.php" instead of "integration_plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin4,613 lines of code in 17 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 13 | 973 | 1,674 | 4,196 |
| JavaScript | 2 | 63 | 16 | 220 |
| PO File | 1 | 69 | 0 | 155 |
| CSS | 1 | 1 | 0 | 42 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 7.87 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 97.00 |
| Average method complexity | 3.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 67.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 69 | |
| ▷ Abstract classes | 24 | 34.78% |
| ▷ Concrete classes | 45 | 65.22% |
| ▷ Final classes | 1 | 2.22% |
| Methods | 240 | |
| ▷ Static methods | 49 | 20.42% |
| ▷ Public methods | 189 | 78.75% |
| ▷ Protected methods | 18 | 7.50% |
| ▷ Private methods | 33 | 13.75% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 98 | |
| ▷ Global constants | 6 | 6.12% |
| ▷ Class constants | 92 | 93.88% |
| ▷ Public constants | 92 | 100.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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon.png | 2.62KB | 2.09KB | ▼ 20.22% |