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 gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼1.66ms] Passed 4 tests
Analyzing server-side resources used by AquaGates Payments for WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 43.49 ▲4.93 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 45.08 ▼3.54 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.40 ▲2.25 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 90.48 ▼5.12 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.32 ▼0.23 |
Server storage [IO: ▲0.19MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 36 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for AquaGates Payments for WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,807 ▲72 | 13.26 ▼1.02 | 1.75 ▼0.05 | 40.42 ▼5.45 |
| Dashboard /wp-admin | 2,216 ▲28 | 4.86 ▼0.24 | 109.13 ▲1.60 | 50.63 ▲7.60 |
| Posts /wp-admin/edit.php | 2,095 ▲6 | 2.05 ▼0.00 | 40.59 ▲0.84 | 42.60 ▲7.78 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲5 | 23.07 ▼0.11 | 588.56 ▼87.49 | 52.59 ▼6.86 |
| Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.21 ▼0.07 | 96.32 ▼15.05 | 48.10 ▼0.93 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 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
Please fix the following items
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/aquagates-payments-for-woocommerce/public/aquagates-payments-link-payresulthook.php
- > /wp-content/plugins/aquagates-payments-for-woocommerce/public/partials/aquagates-payments-public-display.php
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/aquagates-payments-for-woocommerce/aquagates/DataEntity.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_errors() in wp-content/plugins/aquagates-payments-for-woocommerce/admin/partials/aquagates-payments-admin-display.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: aquagates, credit cards, woocommerce, japan, payment
aquagates-payments-for-woocommerce/aquagates-payments.php 85% from 13 tests
The main file in "AquaGates Payments for WooCommerce" v. 1.0.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("aquagates-payments-for-woocommerce.php" instead of "aquagates-payments.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected3,264 lines of code in 30 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 26 | 724 | 864 | 3,214 |
| CSS | 2 | 8 | 8 | 44 |
| JavaScript | 2 | 4 | 54 | 6 |
PHP code 50% from 2 tests
This is a very shot review of cyclomatic complexity and code structure
The following items need your attention
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 217)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 25.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 253.00 |
| Average method complexity | 3.88 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 217.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 4 | |
| Classes | 16 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 16 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 166 | |
| ▷ Static methods | 2 | 1.20% |
| ▷ Public methods | 147 | 88.55% |
| ▷ Protected methods | 10 | 6.02% |
| ▷ Private methods | 9 | 5.42% |
| Functions | 14 | |
| ▷ Named functions | 12 | 85.71% |
| ▷ Anonymous functions | 2 | 14.29% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin