Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.59MB] [CPU: ▼10.28ms] Passed 4 tests
Server-side resources used by PayHub Plugin For WooCommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.10 ▲0.63 | 39.87 ▼21.39 |
Dashboard /wp-admin | 3.94 ▲0.59 | 50.88 ▼13.00 |
Posts /wp-admin/edit.php | 3.99 ▲0.63 | 56.03 ▲0.53 |
Add New Post /wp-admin/post-new.php | 6.46 ▲0.57 | 101.44 ▼7.27 |
Media Library /wp-admin/upload.php | 3.80 ▲0.57 | 42.09 ▲7.15 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 29 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for PayHub Plugin For WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,828 ▲82 | 13.74 ▼0.67 | 1.85 ▲0.11 | 39.16 ▲1.12 |
Dashboard /wp-admin | 2,209 ▲21 | 4.87 ▼0.03 | 108.05 ▲6.27 | 42.46 ▼0.36 |
Posts /wp-admin/edit.php | 2,095 ▲6 | 2.03 ▼0.08 | 41.91 ▲5.23 | 35.43 ▲1.16 |
Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.25 ▲0.03 | 680.01 ▲24.91 | 57.37 ▲0.52 |
Media Library /wp-admin/upload.php | 1,388 ▲6 | 4.24 ▲0.07 | 103.82 ▼2.29 | 44.42 ▲1.03 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
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
Even though no errors were found, this is by no means an exhaustive test
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
- 8× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WsConnections' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/model/Refund.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/payhub-payment-gateway-for-woocommerce/woocommerce-payhub.php:10
- > PHP Fatal error
Uncaught Error: Class 'WsConnections' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/model/Sale.php:9
- > PHP Fatal error
Uncaught Error: Class 'AbstractInfo' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/api/CardDataInformation.php:9
- > PHP Fatal error
Uncaught Error: Class 'AbstractInfo' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/api/StatusInformation.php:9
- > PHP Warning
Use of undefined constant WP_PLUGIN_DIR - assumed 'WP_PLUGIN_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/payhub-payment-gateway-for-woocommerce/woocommerce-payhub.php on line 10
- > PHP Fatal error
Uncaught Error: Class 'WsConnections' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/api/TransactionManager.php:8
- > PHP Fatal error
Uncaught Error: Class 'AbstractInfo' not found in wp-content/plugins/payhub-payment-gateway-for-woocommerce/com/payhub/ws/api/MerchantInformation.php:9
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
6 plugin tags: visa, mastercard, credit card, payment, gateway...
payhub-payment-gateway-for-woocommerce/woocommerce-payhub.php 92% from 13 tests
Analyzing the main PHP file in "PayHub Plugin For WooCommerce" version 1.0.17
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("payhub-payment-gateway-for-woocommerce.php" instead of "woocommerce-payhub.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected3,530 lines of code in 27 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 27 | 551 | 1,212 | 3,530 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 13.23 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 119.00 |
Average method complexity | 1.87 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 26 | |
▷ Abstract classes | 1 | 3.85% |
▷ Concrete classes | 25 | 96.15% |
▷ Final classes | 0 | 0.00% |
Methods | 367 | |
▷ Static methods | 20 | 5.45% |
▷ Public methods | 361 | 98.37% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 6 | 1.63% |
Functions | 6 | |
▷ Named functions | 6 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 13 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 13 | 100.00% |
▷ Public constants | 13 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
PoweredbyPayHubCards.png | 9.28KB | 3.96KB | ▼ 57.36% |