Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼8.39ms] Passed 4 tests
An overview of server-side resources used by Woo Payments with PayLeap
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 35.96 ▼0.17 |
| Dashboard /wp-admin | 3.37 ▲0.03 | 49.03 ▼11.94 |
| Posts /wp-admin/edit.php | 3.42 ▲0.07 | 45.71 ▲1.78 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 86.36 ▼21.19 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 35.32 ▼0.26 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Woo Payments with PayLeap
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.55 ▼0.84 | 1.50 ▼0.14 | 39.23 ▲1.09 |
| Dashboard /wp-admin | 2,209 ▲17 | 4.86 ▼0.13 | 99.32 ▼9.58 | 39.63 ▼0.85 |
| Posts /wp-admin/edit.php | 2,086 ▼0 | 1.99 ▼0.04 | 35.13 ▼2.53 | 32.48 ▼2.02 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼14 | 17.71 ▼5.59 | 643.40 ▲31.91 | 57.69 ▲5.82 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.17 ▼0.06 | 98.02 ▲0.96 | 41.60 ▼4.02 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
Smoke tests 75% 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 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woo-payment-processing-payleap/gateway-payleap.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
10 plugin tags: payment, online payments, process credit cards, credit card processing, payment gateway...
woo-payment-processing-payleap/gateway-payleap.php 92% from 13 tests
This is the main PHP file of "Woo Payments with PayLeap" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("woo-payment-processing-payleap.php" instead of "gateway-payleap.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin297 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 74 | 74 | 297 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 34.00 |
| ▷ Minimum class complexity | 34.00 |
| ▷ Maximum class complexity | 34.00 |
| Average method complexity | 4.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.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 | 3 | |
| ▷ Named functions | 3 | 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 |
| images/cards.png | 2.78KB | 1.78KB | ▼ 36.10% |