Benchmarks
Plugin footprint 83% from 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.00MB] [CPU: ▼5.37ms] Passed 4 tests
Server-side resources used by Payway Custom Payment Gateway
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 35.69 ▼2.04 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 43.67 ▼16.33 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.99 ▲4.91 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.76 ▼4.89 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.79 ▲1.80 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Payway Custom Payment Gateway
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.38 ▼0.19 | 1.68 ▼0.08 | 36.72 ▼1.83 |
| Dashboard /wp-admin | 2,189 ▲11 | 5.48 ▼0.17 | 79.96 ▼15.05 | 37.38 ▼7.49 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.02 ▲0.08 | 38.38 ▲3.68 | 38.49 ▼1.30 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.74 ▲0.61 | 606.89 ▼61.90 | 45.55 ▼14.60 |
| Media Library /wp-admin/upload.php | 1,397 ▼0 | 4.23 ▲0.02 | 96.31 ▼7.42 | 44.49 ▼1.31 |
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 does not fully uninstall, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/payway-custom-payment-gateway/payway-payment-gateway.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/payway-custom-payment-gateway/src/payway-init.php:10
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/payway-custom-payment-gateway/src/payway-gateway.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% 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 require attention:
- Tags: There are too many tags (17 tag instead of maximum 10)
payway-custom-payment-gateway/payway-payment-gateway.php 92% from 13 tests
The main file in "Payway Custom Payment Gateway" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("payway-custom-payment-gateway.php" instead of "payway-payment-gateway.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected653 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 67 | 87 | 548 |
| JavaScript | 1 | 9 | 13 | 59 |
| CSS | 1 | 0 | 0 | 46 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 16.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 3.81 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 16 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
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/img/payway.png | 11.14KB | 6.26KB | ▼ 43.75% |