Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
These installer errors require your attention
- Install procedure had errors
- > Warning in wp-content/plugins/acquired-payments-gateway-for-woocommerce/acquired-payment.php+63
include_once(wp-content/plugins/woocommerce/includes/admin/wc-admin-functions.php): failed to open stream: No such file or directory
Server metrics [RAM: ▼0.01MB] [CPU: ▼6.38ms] Passed 4 tests
Analyzing server-side resources used by Acquired Payments Gateway for WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 37.04 ▼7.17 |
Dashboard /wp-admin | 3.31 ▼0.04 | 50.64 ▼6.98 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.92 ▼0.60 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.08 ▼10.76 |
Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 35.22 ▲0.93 |
Server storage [IO: ▲0.47MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 31 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Acquired Payments Gateway for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,815 ▲43 | 14.27 ▼0.01 | 1.92 ▼0.11 | 36.83 ▼5.65 |
Dashboard /wp-admin | 2,195 ▲14 | 5.53 ▼0.19 | 99.55 ▼12.32 | 43.27 ▲4.92 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▲0.02 | 40.68 ▲1.91 | 35.05 ▼2.11 |
Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 23.04 ▼0.62 | 657.49 ▲67.72 | 52.60 ▲5.70 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.18 ▲0.00 | 94.66 ▲0.86 | 41.07 ▲0.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests Passed 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 Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions 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 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% 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:
- Screenshots: Screenshot #1 (Payments configuration) image missing
acquired-payments-gateway-for-woocommerce/acquired-payment.php 77% from 13 tests
The main PHP file in "Acquired Payments Gateway for WooCommerce" ver. 1.2.4 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("acquired-payments-gateway-for-woocommerce.php" instead of "acquired-payment.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
- Domain Path: The domain path points to a folder that does not exist ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected7,856 lines of code in 29 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 15 | 742 | 1,850 | 5,780 |
JavaScript | 7 | 307 | 524 | 1,878 |
SVG | 5 | 7 | 1 | 104 |
CSS | 2 | 11 | 0 | 94 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 79.11 |
▷ Minimum class complexity | 27.00 |
▷ Maximum class complexity | 176.00 |
Average method complexity | 5.14 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 36.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 9 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 163 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 160 | 98.16% |
▷ Protected methods | 3 | 1.84% |
▷ Private methods | 0 | 0.00% |
Functions | 9 | |
▷ Named functions | 4 | 44.44% |
▷ Anonymous functions | 5 | 55.56% |
Constants | 5 | |
▷ Global constants | 4 | 80.00% |
▷ Class constants | 1 | 20.00% |
▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There are no PNG files in this plugin