Benchmarks
Plugin footprint 83% from 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.16MB] [CPU: ▼5.50ms] Passed 4 tests
An overview of server-side resources used by Zaver Checkout for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.63 ▲0.17 | 38.99 ▼8.44 |
Dashboard /wp-admin | 3.46 ▲0.16 | 50.50 ▲0.15 |
Posts /wp-admin/edit.php | 3.58 ▲0.22 | 50.16 ▲0.68 |
Add New Post /wp-admin/post-new.php | 6.05 ▲0.16 | 91.69 ▼14.38 |
Media Library /wp-admin/upload.php | 3.39 ▲0.16 | 38.22 ▲2.04 |
Server storage [IO: ▲0.90MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 195 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
Zaver Checkout for WooCommerce: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.19 ▼1.12 | 4.93 ▲2.93 | 44.44 ▲0.77 |
Dashboard /wp-admin | 2,209 ▲17 | 4.83 ▼0.07 | 114.87 ▲6.47 | 38.13 ▼6.49 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.01 | 40.06 ▼4.47 | 34.93 ▲4.37 |
Add New Post /wp-admin/post-new.php | 1,534 ▲13 | 23.21 ▼0.12 | 645.90 ▼21.93 | 51.69 ▲3.17 |
Media Library /wp-admin/upload.php | 1,382 ▼0 | 4.17 ▼0.01 | 95.80 ▼0.46 | 42.17 ▲1.78 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 64× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/zaver-checkout-for-woocommerce/classes/checkout-gateway.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/psr7/src/DroppingStream.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Client\\ClientExceptionInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/guzzle/src/Exception/GuzzleException.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromiseInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/promises/src/RejectedPromise.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Client\\ClientExceptionInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/psr/http-client/src/NetworkExceptionInterface.php:14
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Cookie\\CookieJar' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/guzzle/src/Cookie/SessionCookieJar.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/psr7/src/NoSeekStream.php:12
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/guzzle/src/Pool.php:24
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\TaskQueueInterface' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/guzzlehttp/promises/src/TaskQueue.php:14
- > PHP Fatal error
Uncaught Error: Class 'Zaver\\SDK\\Utils\\DataObject' not found in wp-content/plugins/zaver-checkout-for-woocommerce/vendor/zaver/sdk/src/Object/PaymentStatusResponse.php:9
- > 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 90% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
6 plugin tags: zaver, refund, swish, checkout, woocommerce...
zaver-checkout-for-woocommerce/woocommerce-zaver-checkout.php 77% from 13 tests
The main PHP script in "Zaver Checkout for WooCommerce" version 1.0.18 is automatically included on every request by WordPress
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.7" instead of "6.0.0")
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("zaver-checkout-for-woocommerce.php" instead of "woocommerce-zaver-checkout.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
No dangerous file extensions were detected16,332 lines of code in 178 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 149 | 2,438 | 6,257 | 11,336 |
Markdown | 16 | 1,266 | 0 | 3,714 |
JSON | 10 | 0 | 0 | 1,132 |
PO File | 1 | 42 | 42 | 134 |
make | 1 | 4 | 0 | 9 |
YAML | 1 | 0 | 0 | 7 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 11.62 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 88.00 |
Average method complexity | 2.60 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 16 | |
Interfaces | 26 | |
Traits | 3 | |
Classes | 107 | |
▷ Abstract classes | 2 | 1.87% |
▷ Concrete classes | 105 | 98.13% |
▷ Final classes | 36 | 34.29% |
Methods | 904 | |
▷ Static methods | 168 | 18.58% |
▷ Public methods | 770 | 85.18% |
▷ Protected methods | 4 | 0.44% |
▷ Private methods | 130 | 14.38% |
Functions | 123 | |
▷ Named functions | 34 | 27.64% |
▷ Anonymous functions | 89 | 72.36% |
Constants | 98 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 98 | 100.00% |
▷ Public constants | 87 | 88.78% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
PNG images were not found in this plugin