Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼4.81ms] Passed 4 tests
Server-side resources used by PayBill.NG Woocommerce Payment Gateway
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 39.75 ▼4.45 |
Dashboard /wp-admin | 3.34 ▲0.04 | 49.09 ▼1.95 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 49.30 ▲0.66 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 86.02 ▼13.50 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 36.63 ▲4.14 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for PayBill.NG Woocommerce Payment Gateway
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.17 ▼0.12 | 1.85 ▼0.39 | 43.66 ▲0.09 |
Dashboard /wp-admin | 2,198 ▲21 | 5.64 ▼0.04 | 98.22 ▲8.24 | 43.05 ▲4.47 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 1.99 ▼0.01 | 37.13 ▼0.51 | 33.50 ▼7.03 |
Add New Post /wp-admin/post-new.php | 1,529 ▲1 | 23.25 ▲0.35 | 616.16 ▼43.82 | 54.11 ▼7.21 |
Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.18 ▲0.00 | 98.43 ▼3.33 | 40.47 ▼3.24 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/paybill-payment-gateway-for-woocommerce/includes/templates/processing_form.php:8
- > PHP Fatal error
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 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Contributors: Contributors not specified
- Screenshots: No descriptions were found for these screenshots #1, #2 in paybill-payment-gateway-for-woocommerce/assets to your readme.txt
paybill-payment-gateway-for-woocommerce/index.php 92% from 13 tests
The main PHP file in "PayBill.NG Woocommerce Payment Gateway" ver. 0.1.7 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("paybill-payment-gateway-for-woocommerce.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin384 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 138 | 35 | 384 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.21 |
Average class complexity | 5.20 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 15.00 |
Average method complexity | 3.10 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 10 | |
▷ Static methods | 3 | 30.00% |
▷ Public methods | 10 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 6 | 100.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.24MB with 0.14MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/logo.png | 250.29KB | 104.24KB | ▼ 58.35% |