Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.62ms] Passed 4 tests
Server-side resources used by IranDargah Payment Gateway for Woocommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 42.75 ▲3.34 |
Dashboard /wp-admin | 3.32 ▲0.02 | 46.33 ▲0.11 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.06 ▲1.95 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 83.66 ▼15.88 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.92 ▲4.43 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
IranDargah 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.35 ▼1.05 | 1.74 ▲0.02 | 43.37 ▼4.13 |
Dashboard /wp-admin | 2,206 ▲15 | 4.85 ▼0.00 | 107.85 ▲6.11 | 38.72 ▼3.98 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 2.03 ▲0.02 | 38.97 ▼0.70 | 35.57 ▲0.77 |
Add New Post /wp-admin/post-new.php | 1,541 ▲13 | 18.28 ▼0.16 | 606.90 ▲23.51 | 55.60 ▲4.25 |
Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.15 ▼0.05 | 93.58 ▼3.93 | 40.35 ▼2.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking 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
The following issues need your attention
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/irandargah-payment-gateway-for-woocommerce/includes/class-wc-gateway-irandargah.php:13
- > PHP Fatal error
Uncaught Error: Class 'Automattic\\WooCommerce\\Blocks\\Payments\\Integrations\\AbstractPaymentMethodType' not found in wp-content/plugins/irandargah-payment-gateway-for-woocommerce/includes/class-wc-gateway-irandargah-blocks-support.php:10
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that need to be fixed:
- Contributors: Plugin contributors not specified
irandargah-payment-gateway-for-woocommerce/gateway-irandargah.php 85% from 13 tests
"IranDargah Payment Gateway for Woocommerce" version 2.1.7's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("irandargah-payment-gateway-for-woocommerce.php" instead of "gateway-irandargah.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin917 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 98 | 221 | 630 |
PO File | 1 | 60 | 72 | 159 |
Markdown | 1 | 68 | 0 | 83 |
JavaScript | 3 | 5 | 12 | 35 |
SVG | 1 | 0 | 0 | 10 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 38.00 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 70.00 |
Average method complexity | 3.73 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 1 | 50.00% |
Methods | 27 | |
▷ Static methods | 1 | 3.70% |
▷ Public methods | 24 | 88.89% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 11.11% |
Functions | 6 | |
▷ Named functions | 4 | 66.67% |
▷ Anonymous functions | 2 | 33.33% |
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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There are no PNG files in this plugin