Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼23.88ms] Passed 4 tests
Analyzing server-side resources used by Certegy EziPay Payment Gateway for WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.03 ▼8.27 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 47.14 ▼31.21 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 50.69 ▼12.26 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 86.91 ▼43.78 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 41.64 ▲4.81 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 17 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Certegy EziPay Payment Gateway for WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,815 ▲69 | 13.18 ▼1.20 | 1.91 ▼0.31 | 41.42 ▼13.00 |
| Dashboard /wp-admin | 2,218 ▲21 | 5.80 ▲0.88 | 99.27 ▼28.27 | 37.81 ▼13.19 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.02 ▼0.00 | 39.88 ▼6.95 | 34.10 ▼9.80 |
| Add New Post /wp-admin/post-new.php | 1,549 ▲17 | 23.30 ▲0.32 | 692.02 ▲34.13 | 57.70 ▲3.54 |
| Media Library /wp-admin/upload.php | 1,403 ▲9 | 4.23 ▲0.00 | 110.14 ▲1.36 | 47.03 ▲1.02 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/certegy-ezipay-payment-gateway/WC_Flexi_Gateway.php:2
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/certegy-ezipay-payment-gateway/WC_Flexi_Gateway.php:2
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that require attention:
- Contributors: Contributors not specified
certegy-ezipay-payment-gateway/ezipay.php 92% from 13 tests
The entry point to "Certegy EziPay Payment Gateway for WooCommerce" version 1.3.4 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("certegy-ezipay-payment-gateway.php" instead of "ezipay.php")
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
Success! There were no dangerous files found in this plugin2,554 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 7 | 272 | 143 | 1,328 |
| PHP | 4 | 117 | 201 | 620 |
| SVG | 1 | 24 | 0 | 385 |
| CSS | 2 | 22 | 0 | 221 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 26.33 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 73.00 |
| Average method complexity | 3.05 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 1 | 33.33% |
| ▷ Concrete classes | 2 | 66.67% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 40 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 23 | 57.50% |
| ▷ Protected methods | 4 | 10.00% |
| ▷ Private methods | 13 | 32.50% |
| Functions | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 10 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 10 | 100.00% |
| ▷ Public constants | 10 | 100.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.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/ezipay.png | 8.51KB | 3.12KB | ▼ 63.30% |