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.00MB] [CPU: ▼2.15ms] Passed 4 tests
An overview of server-side resources used by WooCommerce PayWorks Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 40.32 ▼4.85 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 48.78 ▼0.74 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.47 ▲1.82 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.99 ▼2.55 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.00 ▼0.44 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
WooCommerce PayWorks Payment Gateway: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.34 ▼0.30 | 1.98 ▲0.32 | 45.71 ▲1.33 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.62 ▼0.03 | 86.30 ▼17.25 | 42.55 ▼0.78 |
| Posts /wp-admin/edit.php | 2,097 ▼0 | 1.95 ▼0.07 | 35.37 ▼2.75 | 31.86 ▼1.30 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 22.85 ▼0.44 | 664.67 ▼45.58 | 59.37 ▼0.44 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▲0.08 | 101.98 ▼11.44 | 47.26 ▼0.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/woo-payworks-payment-gateway/class-woocommerce-payworks-payment-gateway.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/woo-payworks-payment-gateway/woocommerce-payworks-payment-gateway.php:12
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Tags: Too many tags (15 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: No descriptions were found for these screenshots #1, #2, #3, #4, #5 in woo-payworks-payment-gateway/assets to your readme.txt
woo-payworks-payment-gateway/woocommerce-payworks-payment-gateway.php 85% from 13 tests
This is the main PHP file of "WooCommerce PayWorks Payment Gateway" version 5.4, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("woo-payworks-payment-gateway.php" instead of "woocommerce-payworks-payment-gateway.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 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin370 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 13 | 32 | 333 |
| PO File | 1 | 9 | 11 | 37 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 11.00 |
| Average method complexity | 3.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.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 | 5 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 4 | |
| ▷ Named functions | 4 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin