Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼8.56ms] Passed 4 tests
This is a short check of server-side resources used by SagePay Form Gateway for WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 39.45 ▼1.82 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 50.97 ▼11.59 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 50.84 ▼2.54 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 90.26 ▼18.27 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.76 ▲5.78 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for SagePay Form Gateway for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲18 | 14.37 ▼0.15 | 1.82 ▼0.42 | 40.18 ▼3.69 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.64 ▼0.10 | 82.49 ▼2.97 | 38.59 ▼3.07 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 2.00 ▼0.03 | 35.61 ▼5.76 | 33.68 ▼3.89 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲19 | 23.22 ▲5.38 | 680.12 ▲50.07 | 52.72 ▲1.92 |
| Media Library /wp-admin/upload.php | 1,397 ▲3 | 4.22 ▼0.05 | 101.67 ▼11.55 | 46.81 ▼1.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
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
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/sagepay-form-gateway-for-woocommerce/sagepayform.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
6 plugin tags: sagepay form, wordpress, ecommerce, sagepay go, woocommerce...
sagepay-form-gateway-for-woocommerce/sagepayform.php 77% from 13 tests
The primary PHP file in "SagePay Form Gateway for WooCommerce" version 1.4.5 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("sagepay-form-gateway-for-woocommerce.php" instead of "sagepayform.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
- Domain Path: The domain path is invalid: folder "/lang/" does not exist
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
No dangerous file extensions were detected412 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 108 | 78 | 412 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 35.00 |
| ▷ Minimum class complexity | 35.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 3.27 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 21.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 | 15 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 10 | 66.67% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 33.33% |
| Functions | 2 | |
| ▷ Named functions | 2 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/card-amex.png | 4.45KB | 1.65KB | ▼ 62.79% |
| images/card-disc.png | 4.49KB | 1.47KB | ▼ 67.30% |
| images/card-visa.png | 4.73KB | 1.66KB | ▼ 64.98% |
| images/card-jcb.png | 5.54KB | 1.72KB | ▼ 69.02% |
| images/card-mc.png | 5.42KB | 1.77KB | ▼ 67.41% |