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 gracefully, with no errors
Server metrics [RAM: ▼0.00MB] [CPU: ▼4.43ms] Passed 4 tests
An overview of server-side resources used by PayStand for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 34.80 ▼4.02 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 52.11 ▼13.59 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 54.44 ▲4.79 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 101.81 ▼4.35 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 38.80 ▲4.24 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for PayStand for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲68 | 14.26 ▼0.07 | 2.00 ▲0.11 | 42.28 ▲1.11 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.55 ▼0.14 | 87.97 ▼4.00 | 40.43 ▼3.20 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▼0.00 | 39.51 ▲0.75 | 35.98 ▲3.04 |
| Add New Post /wp-admin/post-new.php | 1,554 ▲23 | 18.22 ▼4.84 | 612.06 ▼74.37 | 50.40 ▼7.29 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.24 ▲0.02 | 102.30 ▼8.37 | 46.45 ▲0.75 |
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
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
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 output text when accessed directly:
- > /wp-content/plugins/woocommerce-paystand/woocommerce-paystand.php
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
7 plugin tags: echeck, ach, bitcoin, woocommerce, payment...
woocommerce-paystand/woocommerce-paystand.php Passed 13 tests
The entry point to "PayStand for WooCommerce" version 1.0.3 is a PHP file that has certain tags in its header comment area
45 characters long description:
Adds PayStand payment gateway to WooCommerce.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected593 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 103 | 122 | 593 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.37 |
| Average class complexity | 67.00 |
| ▷ Minimum class complexity | 67.00 |
| ▷ Maximum class complexity | 67.00 |
| Average method complexity | 6.50 |
| ▷ Minimum method complexity | 2.00 |
| ▷ Maximum method complexity | 32.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 | 12 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 12 | 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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.26MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/paystand_logo_small.png | 3.42KB | 1.91KB | ▼ 44.23% |
| images/paystand_logo_banner.png | 261.45KB | 70.04KB | ▼ 73.21% |