Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.08MB] [CPU: ▼3.39ms] Passed 4 tests
A check of server-side resources used by SagePay Server Gateway for WooCommerce
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.55 ▲0.08 | 36.95 ▼8.27 |
| Dashboard /wp-admin | 3.39 ▲0.08 | 44.87 ▼2.61 |
| Posts /wp-admin/edit.php | 3.44 ▲0.08 | 50.21 ▲5.32 |
| Add New Post /wp-admin/post-new.php | 5.97 ▲0.08 | 89.11 ▼7.22 |
| Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 36.90 ▲4.56 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
SagePay Server Gateway for WooCommerce: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲43 | 14.39 ▲0.05 | 1.60 ▼0.80 | 42.99 ▼2.44 |
| Dashboard /wp-admin | 2,206 ▲18 | 5.04 ▼0.78 | 115.00 ▲9.27 | 41.47 ▼2.66 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.06 ▲0.04 | 40.96 ▲6.42 | 35.56 ▲2.50 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.23 ▲5.71 | 636.21 ▼79.65 | 50.56 ▼14.57 |
| Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.23 ▼0.06 | 103.09 ▼9.02 | 43.49 ▼3.35 |
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
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
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/sagepay-server-gateway-for-woocommerce/woosagepayserver.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
6 plugin tags: payment gateway, wordpress, sagepay go, woocommerce, ecommerce...
sagepay-server-gateway-for-woocommerce/woosagepayserver.php 77% from 13 tests
"SagePay Server Gateway for WooCommerce" version 1.1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Domain Path: The domain path points to a folder that does not exist ("/lang/")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("sagepay-server-gateway-for-woocommerce.php" instead of "woosagepayserver.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin434 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 91 | 65 | 434 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.29 |
| Average class complexity | 45.00 |
| ▷ Minimum class complexity | 45.00 |
| ▷ Maximum class complexity | 45.00 |
| Average method complexity | 5.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 25.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 81.82% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 18.18% |
| 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
PNG files should be compressed to save space and minimize bandwidth usage
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-disc.png | 4.49KB | 1.47KB | ▼ 67.30% |
| images/card-dc.png | 6.16KB | 1.85KB | ▼ 70.00% |
| images/card-mc.png | 5.42KB | 1.77KB | ▼ 67.41% |
| images/card-jcb.png | 5.54KB | 1.72KB | ▼ 69.02% |
| images/card-amex.png | 4.45KB | 1.65KB | ▼ 62.79% |