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.08MB] [CPU: ▼4.01ms] Passed 4 tests
Analyzing server-side resources used by XPAY Payment GateWay
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 42.19 ▲2.25 |
| Dashboard /wp-admin | 3.38 ▲0.08 | 42.39 ▼4.22 |
| Posts /wp-admin/edit.php | 3.50 ▲0.14 | 49.56 ▲2.75 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 77.77 ▼12.68 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.08 | 31.23 ▼1.37 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 11 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for XPAY Payment GateWay
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.23 ▼1.06 | 1.55 ▼0.23 | 36.65 ▼2.56 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.90 ▲0.01 | 110.36 ▲6.06 | 42.87 ▲1.52 |
| Posts /wp-admin/edit.php | 2,086 ▼0 | 2.04 ▲0.04 | 37.27 ▲0.71 | 33.29 ▼1.45 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼3 | 17.57 ▼0.01 | 677.94 ▼17.15 | 68.75 ▲8.80 |
| Media Library /wp-admin/upload.php | 1,391 ▼0 | 4.23 ▲0.03 | 93.47 ▼7.27 | 42.62 ▼0.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
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)
Even though everything seems fine, this is not an exhaustive test
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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/xpay-payment-gateway/XPAY-Payment-GateWay.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 81% from 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
These attributes need to be fixed:
- Screenshots: These screenshots need descriptions #1, #2, #3, #4, #5 in xpay-payment-gateway/assets to your readme.txt
- Contributors: Plugin contributors field is missing
- Tested up to: Version format is invalid
xpay-payment-gateway/XPAY-Payment-GateWay.php 85% from 13 tests
This is the main PHP file of "XPAY Payment GateWay" version 1.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("xpay-payment-gateway.php" instead of "XPAY-Payment-GateWay.php")
- Requires at least: Required version number formatted incorrectly (ex. "7.0" instead of "3.0 or higher")
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
Good job! No executable or dangerous file extensions detected512 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 97 | 67 | 442 |
| XML | 4 | 0 | 0 | 70 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| Average class complexity | 41.00 |
| ▷ Minimum class complexity | 41.00 |
| ▷ Maximum class complexity | 41.00 |
| Average method complexity | 3.22 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.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 | 18 | |
| ▷ Static methods | 1 | 5.56% |
| ▷ Public methods | 12 | 66.67% |
| ▷ Protected methods | 2 | 11.11% |
| ▷ Private methods | 4 | 22.22% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 1 | 25.00% |
| ▷ Class constants | 3 | 75.00% |
| ▷ Public constants | 3 | 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
PNG images were not found in this plugin