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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.83ms] Passed 4 tests
A check of server-side resources used by Payment in-Lire Gateway
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 39.25 ▲2.58 |
| Dashboard /wp-admin | 3.33 ▲0.02 | 47.59 ▼0.30 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 49.46 ▲2.88 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 80.80 ▼15.30 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 34.80 ▼2.29 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Payment in-Lire Gateway
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,808 ▲62 | 13.18 ▼1.57 | 1.78 ▼0.02 | 46.78 ▲6.96 |
| Dashboard /wp-admin | 2,211 ▲23 | 5.80 ▼0.07 | 97.44 ▼4.74 | 41.00 ▼2.60 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 1.99 ▼0.06 | 34.98 ▼1.57 | 34.47 ▲0.78 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲33 | 23.32 ▲5.71 | 589.39 ▼100.39 | 55.22 ▲1.55 |
| Media Library /wp-admin/upload.php | 1,396 ▲8 | 4.33 ▲0.13 | 94.77 ▼17.47 | 40.12 ▼9.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
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
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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)
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need to be fixed:
- Contributors: Plugin contributors not specified
payment-inlire-gateway/payment-inlire-gateway.php Passed 13 tests
The primary PHP file in "Payment in-Lire Gateway" version 0.1 is used by WordPress to initiate all plugin functionality
53 characters long description:
Extension for WooCommerce to add payment with in-Lire
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
Everything looks great! No dangerous files found in this plugin573 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 9 | 146 | 401 | 573 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 11.86 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 32.00 |
| Average method complexity | 2.77 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 17.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 1 | 14.29% |
| ▷ Concrete classes | 6 | 85.71% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 43 | |
| ▷ Static methods | 6 | 13.95% |
| ▷ Public methods | 39 | 90.70% |
| ▷ Protected methods | 1 | 2.33% |
| ▷ Private methods | 3 | 6.98% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 7 | 87.50% |
| ▷ Class constants | 1 | 12.50% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/inlire.png | 5.65KB | 2.95KB | ▼ 47.84% |