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.01MB] [CPU: ▼4.78ms] Passed 4 tests
This is a short check of server-side resources used by JCC Payment Gateway for Woocommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 42.47 ▲2.03 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.00 ▼7.27 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.70 ▲2.52 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 82.43 ▼16.38 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.83 ▲3.96 |
Server storage [IO: ▲2.95MB] [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: 38 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by JCC Payment Gateway for Woocommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,846 ▲111 | 14.75 ▲0.37 | 1.96 ▲0.08 | 40.31 ▲1.31 |
| Dashboard /wp-admin | 2,213 ▲28 | 5.83 ▼0.03 | 105.32 ▼13.69 | 40.02 ▼12.26 |
| Posts /wp-admin/edit.php | 2,102 ▲13 | 1.98 ▼0.06 | 39.99 ▲5.32 | 38.70 ▲2.35 |
| Add New Post /wp-admin/post-new.php | 1,422 ▼98 | 22.32 ▼0.94 | 547.24 ▼59.32 | 43.19 ▼5.62 |
| Media Library /wp-admin/upload.php | 1,392 ▲10 | 4.18 ▲0.00 | 97.53 ▼1.56 | 39.47 ▼2.58 |
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
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/jcc-payment-gateway-for-wc/includes/class-wc-jcc-payment-gateway.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that require attention:
- Screenshots: Add a description for screenshot #5 in jcc-payment-gateway-for-wc/assets to your readme.txt
- Screenshots: Screenshot #1 (Section is used by Administrators to select Test or Production configuration.If Test Mode is enabled you can only use Test Credentials and if it is diasbled you can only use the Production Credentials.) image not found
jcc-payment-gateway-for-wc/class-wc-jcc-plugin.php 92% from 13 tests
Analyzing the main PHP file in "JCC Payment Gateway for Woocommerce" version 1.3.6
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("jcc-payment-gateway-for-wc.php" instead of "class-wc-jcc-plugin.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
Good job! No executable or dangerous file extensions detected1,335 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 215 | 97 | 1,335 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 41.33 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 62.00 |
| Average method complexity | 2.92 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 48.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 63 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 51 | 80.95% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 12 | 19.05% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.43MB with 0.34MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| (invalid) assets/icon-256x256.png | 37.61KB | 0.00KB | ▼ 100.00% |
| (invalid) assets/img/icon-256x256.png | 37.61KB | 0.00KB | ▼ 100.00% |
| assets/screenshot-3.png | 146.43KB | 53.11KB | ▼ 63.73% |
| assets/screenshot-2.png | 37.96KB | 12.31KB | ▼ 67.56% |
| assets/img/screenshot-3.png | 146.43KB | 53.11KB | ▼ 63.73% |