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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼5.52ms] Passed 4 tests
An overview of server-side resources used by Gateway for PayPing on WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.55 ▲0.09 | 41.40 ▼8.43 |
| Dashboard /wp-admin | 3.39 ▲0.09 | 52.88 ▲4.89 |
| Posts /wp-admin/edit.php | 3.44 ▲0.09 | 49.47 ▼1.77 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.09 | 89.73 ▼8.78 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 34.61 ▼3.11 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for Gateway for PayPing on WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.78 ▲0.58 | 1.75 ▼0.31 | 43.67 ▼0.29 |
| Dashboard /wp-admin | 2,206 ▲18 | 5.85 ▲0.97 | 103.78 ▼5.62 | 39.09 ▼2.04 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.02 ▼0.01 | 36.39 ▼3.54 | 34.10 ▼2.12 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼1 | 23.18 ▼0.01 | 666.16 ▲56.67 | 52.04 ▼4.13 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.18 ▲0.02 | 103.98 ▼0.05 | 44.66 ▲0.34 |
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
You still need to fix the following
- Zombie WordPress options were found after 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
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
7 plugin tags: iran, persian, woocommerce, pay ping, payment...
woo-payping-gateway/index.php 92% from 13 tests
The main PHP script in "Gateway for PayPing on WooCommerce" version 4.3.0 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woo-payping-gateway.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Success! There were no dangerous files found in this plugin530 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 55 | 24 | 440 |
| JavaScript | 1 | 4 | 2 | 46 |
| CSS | 1 | 5 | 0 | 44 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 54.00 |
| ▷ Minimum class complexity | 54.00 |
| ▷ Maximum class complexity | 54.00 |
| Average method complexity | 6.89 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.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 | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
3 PNG files occupy 0.05MB with 0.02MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/logo.png | 0.51KB | 0.35KB | ▼ 31.54% |
| screenshot-1.png | 34.01KB | 19.62KB | ▼ 42.30% |
| screenshot-2.png | 18.06KB | 11.44KB | ▼ 36.67% |