Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▲0.06ms] Passed 4 tests
An overview of server-side resources used by CryptAPI Payment Gateway for WooCommerce
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.03 | 41.08 ▼0.78 |
Dashboard /wp-admin | 3.33 ▲0.02 | 49.57 ▲1.46 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 51.62 ▲1.83 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 98.67 ▲0.09 |
Media Library /wp-admin/upload.php | 3.26 ▲0.02 | 34.99 ▼0.53 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for CryptAPI Payment Gateway for WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,821 ▲60 | 14.24 ▲0.08 | 2.46 ▲0.46 | 46.69 ▲2.40 |
Dashboard /wp-admin | 2,202 ▲35 | 5.60 ▼0.10 | 95.93 ▼9.23 | 42.79 ▲1.57 |
Posts /wp-admin/edit.php | 2,110 ▲13 | 1.98 ▼0.05 | 42.76 ▲4.69 | 37.58 ▲1.62 |
Add New Post /wp-admin/post-new.php | 1,537 ▲9 | 23.13 ▲0.07 | 664.10 ▼3.15 | 58.43 ▲5.04 |
Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.28 ▲0.07 | 110.25 ▼0.29 | 48.05 ▲3.36 |
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
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/cryptapi-payment-gateway-for-woocommerce/controllers/CryptAPI.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/cryptapi-payment-gateway-for-woocommerce/define.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/cryptapi-payment-gateway-for-woocommerce/define.php:4
- > 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 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Requires at least: Version format is invalid
- Tags: Please delete some tags, you are using 15 tag instead of maximum 10
cryptapi-payment-gateway-for-woocommerce/CryptAPI.php 85% from 13 tests
"CryptAPI Payment Gateway for WooCommerce" version 4.7.10's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
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 ("cryptapi-payment-gateway-for-woocommerce.php" instead of "CryptAPI.php")
- Requires at least: Periods and digits should be used for the required version number (ex. "7.0" instead of "5")
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
Everything looks great! No dangerous files found in this plugin4,289 lines of code in 15 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 312 | 39 | 1,694 |
PO File | 4 | 464 | 543 | 1,576 |
CSS | 1 | 92 | 0 | 509 |
Markdown | 1 | 100 | 0 | 263 |
JavaScript | 1 | 47 | 0 | 185 |
SVG | 3 | 0 | 0 | 62 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 97.00 |
▷ Minimum class complexity | 50.00 |
▷ Maximum class complexity | 144.00 |
Average method complexity | 5.80 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 24.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 40 | |
▷ Static methods | 9 | 22.50% |
▷ Public methods | 37 | 92.50% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 7.50% |
Functions | 12 | |
▷ Named functions | 10 | 83.33% |
▷ Anonymous functions | 2 | 16.67% |
Constants | 3 | |
▷ Global constants | 3 | 100.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
2 PNG files occupy 0.07MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
static/files/logo_ca.png | 67.00KB | 27.26KB | ▼ 59.31% |
static/files/200_logo_ca.png | 4.03KB | 2.50KB | ▼ 37.85% |