Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼9.18ms] Passed 4 tests
Analyzing server-side resources used by Payment gateway via Teya SecurePay for WooCommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 35.33 ▼8.10 |
Dashboard /wp-admin | 3.32 ▼0.02 | 46.56 ▼13.26 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 46.58 ▲1.83 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 80.83 ▼17.18 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 37.38 ▲2.52 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Payment gateway via Teya SecurePay for WooCommerce
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲43 | 14.21 ▼0.13 | 1.69 ▼0.01 | 41.08 ▼2.61 |
Dashboard /wp-admin | 2,195 ▲21 | 5.61 ▼0.05 | 87.74 ▼11.26 | 39.94 ▼2.11 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.95 ▼0.02 | 39.34 ▲1.73 | 37.03 ▲3.22 |
Add New Post /wp-admin/post-new.php | 1,526 ▼13 | 23.17 ▼0.17 | 604.17 ▲3.82 | 48.61 ▼6.71 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.18 ▼0.02 | 96.17 ▼0.95 | 41.81 ▼1.60 |
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
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/payment-gateway-via-borgun-for-woocommerce/borgun.php:18
- > PHP Warning
The use statement with non-compound name 'Exception' has no effect in wp-content/plugins/payment-gateway-via-borgun-for-woocommerce/includes/class-payment-method-borgun-registration.php on line 3
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/payment-gateway-via-borgun-for-woocommerce/includes/class-wc-gateway-borgun.php:14
- > PHP Fatal error
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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
5 plugin tags: woocommerce, saltpay, gateway, credit card, teya
payment-gateway-via-borgun-for-woocommerce/borgun.php 85% from 13 tests
The main file in "Payment gateway via Teya SecurePay for WooCommerce" v. 1.3.28 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("payment-gateway-via-borgun-for-woocommerce.php" instead of "borgun.php")
- Text Domain: The text domain should only use lowercase characters and dashes
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected992 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 102 | 220 | 800 |
PO File | 1 | 67 | 70 | 165 |
JavaScript | 2 | 6 | 14 | 27 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 54.50 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 103.00 |
Average method complexity | 4.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 32.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 | 0 | 0.00% |
▷ Public methods | 22 | 81.48% |
▷ Protected methods | 5 | 18.52% |
▷ Private methods | 0 | 0.00% |
Functions | 7 | |
▷ Named functions | 6 | 85.71% |
▷ Anonymous functions | 1 | 14.29% |
Constants | 5 | |
▷ Global constants | 3 | 60.00% |
▷ Class constants | 2 | 40.00% |
▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
cards.png | 5.49KB | 2.76KB | ▼ 49.80% |