Benchmarks
Plugin footprint Passed 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.11MB] [CPU: ▼142.31ms] Passed 4 tests
Analyzing server-side resources used by PayIBAN – Plugin machtigen via Incassomachtigen voor Woocommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.95 ▲0.11 | 33.16 ▼6.27 |
Dashboard /wp-admin | 3.17 ▲0.12 | 47.80 ▼15.26 |
Posts /wp-admin/edit.php | 3.22 ▲0.12 | 50.63 ▲10.31 |
Add New Post /wp-admin/post-new.php | 5.53 ▲0.10 | 86.45 ▼554.26 |
Media Library /wp-admin/upload.php | 3.12 ▲0.11 | 35.82 ▲6.56 |
Welcome /wp-admin/index.php?page=machtiging-free-plugin-welcome | 3.08 | 29.72 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 5 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for PayIBAN – Plugin machtigen via Incassomachtigen voor Woocommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,684 ▲112 | 15.92 ▲0.24 | 10.86 ▲1.57 | 46.08 ▼4.57 |
Dashboard /wp-admin | 2,972 ▲38 | 5.93 ▼0.07 | 144.59 ▼46.74 | 114.11 ▼18.26 |
Posts /wp-admin/edit.php | 2,744 ▲5 | 2.72 ▲0.01 | 67.97 ▼2.55 | 84.77 ▼5.56 |
Add New Post /wp-admin/post-new.php | 1,503 ▼175 | 18.59 ▼0.20 | 373.10 ▼22.07 | 107.12 ▼2.04 |
Media Library /wp-admin/upload.php | 1,815 ▲5 | 5.04 ▲0.01 | 145.13 ▼4.64 | 120.63 ▲6.25 |
Welcome /wp-admin/index.php?page=machtiging-free-plugin-welcome | 1,002 | 2.35 | 75.91 | 54.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
No output text or server-side errors detected on direct access of PHP files
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There are user-side issues you should fix
- > GET request to /wp-admin/index.php?page=machtiging-free-plugin-welcome
- > Network (severe)
chrome-error://chromewebdata/ - Failed to load resource: the server responded with a status of 403 ()
- > GET request to /wp-admin/index.php?page=machtiging-free-plugin-welcome
- > Other (severe) in unknown
chrome-error://chromewebdata/ - Refused to display 'https://www.payiban.com/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
Optimizations
Plugin configuration 96% 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
8 plugin tags: woocommerce, ideal, sepa incasso, sepa direct debit, payment provider...
digital-mandate-for-woocommerce/digital-mandate-payIBAN.php 92% from 13 tests
"PayIBAN – Plugin machtigen via Incassomachtigen voor Woocommerce" version 1.3.7's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("digital-mandate-for-woocommerce.php" instead of "digital-mandate-payIBAN.php")
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
No dangerous file extensions were detected632 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 134 | 93 | 499 |
PO File | 1 | 68 | 125 | 133 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 26.00 |
▷ Minimum class complexity | 26.00 |
▷ Maximum class complexity | 26.00 |
Average method complexity | 4.57 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.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 | 7 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 7 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 12 | |
▷ Named functions | 12 | 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
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 |
payibanlogo.png | 3.46KB | 2.18KB | ▼ 37.00% |