Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼141.97ms] Passed 4 tests
Analyzing server-side resources used by WooFakePay
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.86 ▲0.14 | 35.55 ▲14.79 |
| Dashboard /wp-admin | 3.08 ▲0.03 | 43.80 ▼0.13 |
| Posts /wp-admin/edit.php | 3.13 ▲0.02 | 43.78 ▲0.47 |
| Add New Post /wp-admin/post-new.php | 5.44 ▲0.01 | 90.96 ▼559.41 |
| Media Library /wp-admin/upload.php | 3.02 ▲0.01 | 29.85 ▼8.79 |
Server storage [IO: ▲0.54MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 7 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for WooFakePay
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,703 ▲107 | 15.99 ▲0.44 | 8.34 ▼0.65 | 50.66 ▼1.07 |
| Dashboard /wp-admin | 2,989 ▲55 | 5.96 ▲0.03 | 136.45 ▼4.82 | 105.53 ▼0.59 |
| Posts /wp-admin/edit.php | 2,736 ▼3 | 2.80 ▲0.11 | 71.83 ▲4.63 | 93.45 ▲5.11 |
| Add New Post /wp-admin/post-new.php | 1,670 ▲157 | 19.14 ▲0.66 | 372.72 ▲24.35 | 102.23 ▼14.36 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.01 ▼0.01 | 143.63 ▼13.00 | 122.23 ▲0.46 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The plugin uninstalled successfully, without leaving any zombie files or tables
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 add_action() in wp-content/plugins/woofakepay/woofakepay.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Payment Gateway config), #2 (Checkout), #3 (Visitor being redirected to the fake "remote" URL, and back), #4 (All done, Order has been paid and processed)
woofakepay/woofakepay.php Passed 13 tests
The main PHP file in "WooFakePay" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
57 characters long description:
Test Payment Gateway for WooCommerce That Always Pays Off
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin102 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 27 | 60 | 102 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.07 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.25 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 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 | 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 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
4 PNG files occupy 0.51MB with 0.37MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 92.48KB | 25.20KB | ▼ 72.75% |
| screenshot-4.png | 196.47KB | 44.51KB | ▼ 77.34% |
| screenshot-1.png | 73.37KB | 22.50KB | ▼ 69.34% |
| screenshot-3.png | 159.92KB | 49.72KB | ▼ 68.91% |