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.01MB] [CPU: ▼3.13ms] Passed 4 tests
An overview of server-side resources used by Charge Anywhere Payment Gateway For WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.79 ▼3.76 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.81 ▼2.11 |
Posts /wp-admin/edit.php | 3.42 ▲0.07 | 45.78 ▲0.27 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 83.65 ▼5.36 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 32.50 ▼1.29 |
Server storage [IO: ▲0.22MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
Charge Anywhere Payment Gateway For WooCommerce: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.21 ▼1.25 | 1.66 ▼0.46 | 43.17 ▼3.70 |
Dashboard /wp-admin | 2,203 ▲12 | 5.90 ▲0.97 | 93.21 ▼10.62 | 38.90 ▼5.26 |
Posts /wp-admin/edit.php | 2,089 ▲21 | 2.02 ▼0.03 | 38.61 ▲3.73 | 32.54 ▼3.01 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.28 ▲0.10 | 668.61 ▼7.17 | 63.77 ▲4.48 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.24 ▲0.03 | 94.76 ▼18.54 | 40.79 ▼7.75 |
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
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
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 fix the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/charge-anywhere-payment-gateway-for-woocommerce/credit_card.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/charge-anywhere-payment-gateway-for-woocommerce/index.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== Charge Anywhere Payment Gateway For WooCommerce===
)
charge-anywhere-payment-gateway-for-woocommerce/index.php 92% from 13 tests
The primary PHP file in "Charge Anywhere Payment Gateway For WooCommerce" version 1.13 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("charge-anywhere-payment-gateway-for-woocommerce.php" instead of "index.php")
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
Success! There were no dangerous files found in this plugin1,510 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 160 | 163 | 1,229 |
JavaScript | 2 | 62 | 5 | 280 |
SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 130.00 |
▷ Minimum class complexity | 130.00 |
▷ Maximum class complexity | 130.00 |
Average method complexity | 6.38 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 51.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 | 24 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 24 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 9 | |
▷ Named functions | 6 | 66.67% |
▷ Anonymous functions | 3 | 33.33% |
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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG images were found in this plugin