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: ▼8.13ms] Passed 4 tests
This is a short check of server-side resources used by Payzee
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 38.26 ▼2.25 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 44.56 ▼18.82 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 44.92 ▲1.69 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 86.63 ▼13.13 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 35.07 ▲4.45 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Payzee
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.59 ▼0.71 | 1.66 ▼0.23 | 39.64 ▼5.05 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.86 ▼1.02 | 109.70 ▲11.71 | 42.61 ▲3.92 |
| Posts /wp-admin/edit.php | 2,086 ▼3 | 2.02 ▼0.04 | 39.92 ▲0.46 | 34.84 ▼0.77 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼9 | 23.36 ▲5.18 | 603.28 ▼12.77 | 49.82 ▼6.13 |
| Media Library /wp-admin/upload.php | 1,382 ▼0 | 4.18 ▲0.02 | 96.36 ▼2.57 | 40.41 ▼2.51 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 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
Please take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/payzee-payment-gateway/payzee.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: installment, credit, gateway, card, payment
payzee-payment-gateway/payzee.php 69% from 13 tests
"Payzee" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Requires at least: Required version must match the one declared in readme.txt ("4.7" instead of "5.2")
- Description: A good plugin description is longer than 10 characters (currently 6 characters long)
- Requires PHP: Required version must match the one declared in readme.txt ("7.0" instead of "7.2")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("payzee-payment-gateway.php" instead of "payzee.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected196 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 37 | 14 | 196 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 3.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.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 | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
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/icon.png | 3.30KB | 2.45KB | ▼ 25.95% |