Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.10MB] [CPU: ▼4.66ms] Passed 4 tests
Analyzing server-side resources used by Vipps Recurring Payments for WooCommerce
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.57 ▲0.11 | 35.37 ▼4.58 |
Dashboard /wp-admin | 3.40 ▲0.10 | 44.89 ▼4.84 |
Posts /wp-admin/edit.php | 3.52 ▲0.16 | 44.81 ▼2.53 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 90.51 ▼6.67 |
Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 34.54 ▲3.16 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 40 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
widget_theysaidso_widget |
woo-vipps-recurring-version |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Vipps Recurring Payments for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲28 | 14.29 ▲0.03 | 1.71 ▲0.01 | 37.54 ▼4.27 |
Dashboard /wp-admin | 2,195 ▲15 | 5.59 ▼0.03 | 91.01 ▲0.11 | 42.49 ▲1.24 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.95 ▼0.07 | 39.80 ▲2.57 | 34.73 ▼2.92 |
Add New Post /wp-admin/post-new.php | 1,526 ▼19 | 23.01 ▼2.18 | 614.82 ▼39.43 | 54.33 ▼7.11 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.17 ▼0.03 | 100.04 ▲3.23 | 43.09 ▲0.75 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- woo-vipps-recurring-version
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
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
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
5 plugin tags: woocommerce subscriptions, subscriptions, recurring payments, vipps, woocommerce
vipps-recurring-payments-gateway-for-woocommerce/woo-vipps-recurring.php 77% from 13 tests
The entry point to "Vipps Recurring Payments for WooCommerce" version 1.17.1 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Requires at least: Required version must be the same as the one declared in readme.txt ("5.0" instead of "4.4")
- Main file name: The principal plugin file should be the same as the plugin slug ("vipps-recurring-payments-gateway-for-woocommerce.php" instead of "woo-vipps-recurring.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected4,063 lines of code in 30 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 24 | 1,101 | 1,451 | 3,599 |
PO File | 1 | 121 | 164 | 372 |
JavaScript | 1 | 9 | 0 | 54 |
CSS | 2 | 6 | 0 | 36 |
SVG | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 22.74 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 214.00 |
Average method complexity | 2.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 22.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 23 | |
▷ Abstract classes | 1 | 4.35% |
▷ Concrete classes | 22 | 95.65% |
▷ Final classes | 0 | 0.00% |
Methods | 245 | |
▷ Static methods | 48 | 19.59% |
▷ Public methods | 218 | 88.98% |
▷ Protected methods | 13 | 5.31% |
▷ Private methods | 14 | 5.71% |
Functions | 15 | |
▷ Named functions | 4 | 26.67% |
▷ Anonymous functions | 11 | 73.33% |
Constants | 69 | |
▷ Global constants | 8 | 11.59% |
▷ Class constants | 61 | 88.41% |
▷ Public constants | 61 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.14MB with 0.08MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/vipps-logg-inn-neg.png | 20.10KB | 10.72KB | ▼ 46.68% |
assets/images/vipps-rgb-black.png | 25.32KB | 11.92KB | ▼ 52.92% |
assets/images/vipps-icon-smile.png | 3.96KB | 1.91KB | ▼ 51.65% |
assets/images/vipps_logo_negative_rgb.png | 54.24KB | 19.04KB | ▼ 64.90% |
assets/images/vipps-logo-negative-rgb-transparent.png | 16.36KB | 7.33KB | ▼ 55.17% |