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 gracefully, with no errors
Server metrics [RAM: ▲0.04MB] [CPU: ▼9.50ms] Passed 4 tests
An overview of server-side resources used by Jambopay WooCommerce Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.04 | 37.42 ▼1.75 |
| Dashboard /wp-admin | 3.35 ▲0.05 | 44.63 ▼8.74 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 46.77 ▼4.11 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 82.17 ▼21.17 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 34.50 ▼3.98 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
Jambopay WooCommerce Payment Gateway: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.25 ▼0.35 | 1.59 ▲0.01 | 40.19 ▲3.28 |
| Dashboard /wp-admin | 2,189 ▲8 | 5.50 ▼0.13 | 83.44 ▼14.53 | 36.75 ▼7.10 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▼0.10 | 32.69 ▼7.08 | 31.57 ▼8.43 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.38 ▲0.27 | 664.33 ▲33.14 | 57.39 ▲0.29 |
| Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.18 ▲0.04 | 105.15 ▲8.66 | 43.97 ▼1.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
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
Everything seems fine, however 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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/jambopay-woocommerce-payment-gateway/class-wc-jambopay.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that require attention:
- Tags: There are too many tags (11 tag instead of maximum 10)
jambopay-woocommerce-payment-gateway/class-wc-jambopay.php 92% from 13 tests
Analyzing the main PHP file in "Jambopay WooCommerce Payment Gateway" version 2.6.1.0
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("jambopay-woocommerce-payment-gateway.php" instead of "class-wc-jambopay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin184 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 46 | 63 | 184 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.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 | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin