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.49ms] Passed 4 tests
Analyzing server-side resources used by goEmerchant Payment Gateway Plugin for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 42.09 ▲2.96 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 46.84 ▼5.32 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.68 ▼3.54 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 92.14 ▼10.37 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.51 ▲1.26 |
Server storage [IO: ▲0.84MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact 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 |
|---|
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by goEmerchant Payment Gateway Plugin for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.41 ▲0.05 | 1.83 ▲0.13 | 43.47 ▼0.32 |
| Dashboard /wp-admin | 2,195 ▲21 | 5.54 ▼0.10 | 86.26 ▼3.37 | 40.82 ▼1.42 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.96 ▼0.07 | 34.90 ▼5.74 | 38.22 ▲2.00 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.23 ▲0.19 | 676.94 ▲25.64 | 61.86 ▲6.17 |
| Media Library /wp-admin/upload.php | 1,403 ▼0 | 4.21 ▲0.02 | 94.83 ▼9.39 | 43.66 ▼3.26 |
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
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4 in goemerchant-gateway-for-woocommerce/assets to your readme.txt
goemerchant-gateway-for-woocommerce/goemerchant-gateway.php 92% from 13 tests
The primary PHP file in "goEmerchant Payment Gateway Plugin for WooCommerce" version 1.2.1 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("goemerchant-gateway-for-woocommerce.php" instead of "goemerchant-gateway.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected1,136 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 156 | 246 | 1,057 |
| Markdown | 1 | 22 | 0 | 48 |
| JavaScript | 1 | 8 | 5 | 31 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.56 |
| Average class complexity | 41.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 142.00 |
| Average method complexity | 5.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 6 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 55 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 54 | 98.18% |
| ▷ Protected methods | 1 | 1.82% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 51 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 51 | 100.00% |
| ▷ Public constants | 51 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
5 PNG files occupy 0.76MB with 0.48MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/banner-1880x609.png | 311.90KB | 100.78KB | ▼ 67.69% |
| assets/screenshot-2.PNG | 43.77KB | 20.49KB | ▼ 53.19% |
| assets/screenshot-4.PNG | 272.92KB | 64.21KB | ▼ 76.47% |
| assets/screenshot-1.PNG | 46.30KB | 16.00KB | ▼ 65.45% |
| assets/screenshot-3.PNG | 104.24KB | 47.91KB | ▼ 54.04% |