Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.66ms] Passed 4 tests
This is a short check of server-side resources used by Gateway for Qpay on WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 36.06 ▼6.39 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 46.10 ▼8.29 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.21 ▲0.97 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.70 ▼15.92 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.57 ▼0.02 |
Server storage [IO: ▲3.57MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 39 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Gateway for Qpay on WooCommerce
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,814 ▲53 | 14.25 ▼0.35 | 2.83 ▲1.08 | 42.57 ▼2.34 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.61 ▲0.07 | 89.80 ▼14.11 | 38.86 ▼8.01 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.95 ▼0.03 | 38.69 ▲2.72 | 35.94 ▼4.02 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.03 ▼0.11 | 652.31 ▼38.98 | 46.86 ▼5.05 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.21 ▼0.01 | 94.90 ▼22.93 | 42.68 ▼6.39 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
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 fix the following
- 2× PHP files output text when accessed directly:
- > /wp-content/plugins/wc-qpay-gateway/admin/partials/qplugin-admin-display.php
- > /wp-content/plugins/wc-qpay-gateway/public/partials/qplugin-public-display.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 93% from 29 tests
readme.txt Passed 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
3 plugin tags: qpay, gateway, qr code
wc-qpay-gateway/qplugin.php 85% from 13 tests
"Gateway for Qpay on WooCommerce" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wc-qpay-gateway.php" instead of "qplugin.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected842 lines of code in 28 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 158 | 630 | 468 |
| JavaScript | 5 | 6 | 69 | 185 |
| Markdown | 3 | 68 | 0 | 151 |
| CSS | 5 | 5 | 22 | 29 |
| SVG | 1 | 0 | 0 | 9 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.12 |
| Average class complexity | 2.88 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 1.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 36 | |
| ▷ Static methods | 2 | 5.56% |
| ▷ Public methods | 27 | 75.00% |
| ▷ Protected methods | 4 | 11.11% |
| ▷ Private methods | 5 | 13.89% |
| Functions | 6 | |
| ▷ Named functions | 6 | 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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| public/images/icons/logo_100px.png | 2.95KB | 2.42KB | ▼ 17.79% |
| public/images/icons/logo.png | 22.19KB | 13.09KB | ▼ 41.01% |