Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.42ms] Passed 4 tests
A check of server-side resources used by Zapper Payments
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 38.13 ▼7.80 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 50.88 ▼16.40 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.36 ▼4.53 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.37 ▼4.58 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.06 ▼4.91 |
Server storage [IO: ▲0.74MB] [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: 12 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
Checking browser requirements for Zapper Payments
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.17 ▼0.46 | 1.70 ▼0.38 | 43.72 ▼2.39 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.52 ▼0.14 | 86.30 ▼7.46 | 41.91 ▲3.57 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 1.98 ▼0.06 | 36.15 ▼6.96 | 30.97 ▼6.39 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲9 | 18.48 ▼4.40 | 617.65 ▼31.56 | 67.84 ▲14.21 |
| Media Library /wp-admin/upload.php | 1,403 ▲9 | 4.20 ▼0.06 | 92.72 ▼5.39 | 41.61 ▼0.74 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (Zapper Payments for WooCommerce plugin configuration.), #2 (Checkout option to select Zapper as a payment method.), #3 (Desktop Payment Gateway.), #4 (Mobile Payment Gateway.)
zapper-payments/zapper-payments.php 92% from 13 tests
Analyzing the main PHP file in "Zapper Payments" version 2.1.8
The following require your attention:
- Requires at least: The required version number must match the one declared in readme.txt ("4.3" instead of "2.5")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin577 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 58 | 20 | 360 |
| JavaScript | 2 | 40 | 5 | 217 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 25.00 |
| Average method complexity | 3.31 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.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 | 13 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 10 | 76.92% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 3 | 23.08% |
| Functions | 4 | |
| ▷ Named functions | 3 | 75.00% |
| ▷ Anonymous functions | 1 | 25.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
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/zapper.png | 3.36KB | 1.49KB | ▼ 55.68% |