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
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.59ms] Passed 4 tests
An overview of server-side resources used by WooCommerce Varipay Payment Gateway
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 44.01 ▼0.21 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 51.09 ▼2.48 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 52.97 ▼6.95 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 93.80 ▼4.72 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 38.91 ▲1.91 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for WooCommerce Varipay Payment Gateway
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.21 ▼0.57 | 1.54 ▼0.28 | 40.52 ▼3.78 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.60 ▼0.13 | 89.85 ▼8.33 | 42.71 ▼0.20 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 1.97 ▼0.03 | 38.44 ▲0.96 | 37.68 ▲2.63 |
| Add New Post /wp-admin/post-new.php | 1,537 ▲11 | 18.34 ▼4.78 | 632.51 ▼67.71 | 62.10 ▼10.24 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.21 ▼0.01 | 96.86 ▼9.13 | 44.40 ▼2.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not 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 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Screenshots: Please add images for these screenshots: #1 (The settings panel used to configure the gateway.), #2 (Normal checkout with Varipay.), #3 (Checking out with a saved card.)
woo-varipay/woo-varipay.php Passed 13 tests
The primary PHP file in "WooCommerce Varipay Payment Gateway" version 1.0.1 is used by WordPress to initiate all plugin functionality
54 characters long description:
Take credit card payments on your store using Varipay.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected655 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 351 | 107 | 655 |
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.39 |
| Average class complexity | 31.67 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 77.00 |
| Average method complexity | 4.17 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.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 | 29 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 19 | 65.52% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 10 | 34.48% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/cards.png | 4.98KB | 2.14KB | ▼ 57.03% |