Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▲0.99ms] Passed 4 tests
This is a short check of server-side resources used by WooCommerce PulzePay
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.03 | 43.90 ▲6.18 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 50.15 ▼6.16 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 47.64 ▼1.73 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 95.33 ▲6.27 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 42.94 ▲5.66 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
WooCommerce PulzePay: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.26 ▼0.01 | 1.73 ▼0.19 | 44.35 ▲1.52 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.55 ▼0.11 | 87.82 ▼8.14 | 38.89 ▼7.01 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.00 ▼0.01 | 35.93 ▼1.50 | 34.57 ▼0.53 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼9 | 23.19 ▼0.82 | 687.18 ▲63.52 | 61.28 ▼3.07 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.15 ▼0.01 | 109.30 ▲1.06 | 46.92 ▼4.10 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 50% from 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 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 4× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/woo-pulzepay/payment-return.php
- > /wp-content/plugins/woo-pulzepay/payment-callback.php
- > /wp-content/plugins/woo-pulzepay/index.php
- > /wp-content/plugins/woo-pulzepay/payment-result.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-pulzepay/woocommerce-pulzepay.php:18
- > PHP Fatal error
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 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Screenshots: These screenshots lack descriptions #3, #4 in woo-pulzepay/assets to your readme.txt
woo-pulzepay/woocommerce-pulzepay.php 92% from 13 tests
The principal PHP file in "WooCommerce PulzePay" v. 1.0.7 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("woo-pulzepay.php" instead of "woocommerce-pulzepay.php")
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
There were no executable files found in this plugin297 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 116 | 63 | 297 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.15 |
| Average class complexity | 6.00 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 6.00 |
| Average method complexity | 1.62 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.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 | 8 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 8 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 5 | |
| ▷ Named functions | 5 | 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.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/pulzepay.png | 15.84KB | 4.36KB | ▼ 72.47% |