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.01MB] [CPU: ▼0.82ms] Passed 4 tests
A check of server-side resources used by Opay Now Payment Gateway for WooCommerce
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 42.78 ▼1.40 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 64.32 ▲1.62 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 51.59 ▲0.41 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 96.55 ▼3.92 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 41.25 ▲7.87 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Opay Now Payment Gateway for WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲54 | 13.27 ▼0.94 | 1.73 ▲0.02 | 43.85 ▼2.60 |
| Dashboard /wp-admin | 2,218 ▲17 | 5.77 ▲0.86 | 98.85 ▼17.35 | 43.24 ▼0.91 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▼0.03 | 38.69 ▲3.43 | 36.93 ▲1.32 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼15 | 17.61 ▼5.44 | 672.64 ▼20.40 | 58.88 ▲6.00 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▼0.01 | 99.33 ▼20.60 | 47.81 ▼2.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means 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
The following issues need your attention
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/opay-now-payment-gateway-for-woocommerce/front/index.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots lack descriptions #1, #2, #3, #4 in opay-now-payment-gateway-for-woocommerce/assets to your readme.txt
opay-now-payment-gateway-for-woocommerce/opaynow_woocommerce.php 92% from 13 tests
This is the main PHP file of "Opay Now Payment Gateway for WooCommerce" version 1.1.0, 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 ("opay-now-payment-gateway-for-woocommerce.php" instead of "opaynow_woocommerce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected707 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 96 | 210 | 690 |
| JavaScript | 1 | 1 | 0 | 17 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 11.33 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 30.00 |
| Average method complexity | 2.94 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.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 | 12 | 75.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 25.00% |
| Functions | 14 | |
| ▷ Named functions | 14 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 12 | |
| ▷ Global constants | 5 | 41.67% |
| ▷ Class constants | 7 | 58.33% |
| ▷ Public constants | 7 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/logo.png | 10.76KB | 4.37KB | ▼ 59.39% |