Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼135.17ms] Passed 4 tests
A check of server-side resources used by WooCommerce DropPay
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.84 ▲0.01 | 45.08 ▲14.52 |
| Dashboard /wp-admin | 3.07 ▲0.01 | 52.86 ▲9.22 |
| Posts /wp-admin/edit.php | 3.12 ▲0.01 | 48.31 ▲1.03 |
| Add New Post /wp-admin/post-new.php | 5.43 ▼0.00 | 98.37 ▼540.85 |
| Media Library /wp-admin/upload.php | 3.01 ▲0.00 | 31.64 ▼10.09 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 11 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for WooCommerce DropPay
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,703 ▲107 | 15.92 ▲0.21 | 9.52 ▼0.80 | 54.43 ▼2.58 |
| Dashboard /wp-admin | 2,970 ▲36 | 6.05 ▲0.07 | 147.90 ▼3.27 | 116.14 ▼5.88 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.72 ▲0.01 | 71.31 ▲1.08 | 100.30 ▲4.91 |
| Add New Post /wp-admin/post-new.php | 1,683 ▼374 | 18.74 ▼0.56 | 380.36 ▲4.65 | 109.31 ▼8.79 |
| Media Library /wp-admin/upload.php | 1,810 ▲3 | 5.03 ▲0.00 | 161.28 ▲7.97 | 124.30 ▲3.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Uninstaller ran successfully
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-droppay/woo-droppay.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: droppay, payment method, woocommerce
woo-droppay/woo-droppay.php Passed 13 tests
"WooCommerce DropPay" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
89 characters long description:
With DropPay you can send and receive money with your smartphone and make payments safely
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
Everything looks great! No dangerous files found in this plugin505 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 78 | 82 | 344 |
| JavaScript | 1 | 22 | 10 | 87 |
| PO File | 1 | 10 | 12 | 46 |
| CSS | 1 | 5 | 0 | 28 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 12.33 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 14.00 |
| Average method complexity | 2.79 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 19 | |
| ▷ Static methods | 1 | 5.26% |
| ▷ Public methods | 17 | 89.47% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 10.53% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 4 | 100.00% |
| ▷ Public constants | 4 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/close.png | 9.57KB | 3.89KB | ▼ 59.31% |
| logo.png | 9.88KB | 2.81KB | ▼ 71.54% |