Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.17MB] [CPU: ▼3.95ms] Passed 4 tests
Analyzing server-side resources used by TogetherPay for WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.64 ▲0.17 | 37.99 ▲1.22 |
| Dashboard /wp-admin | 3.48 ▲0.18 | 44.55 ▼3.35 |
| Posts /wp-admin/edit.php | 3.59 ▲0.23 | 44.84 ▼2.29 |
| Add New Post /wp-admin/post-new.php | 6.06 ▲0.17 | 80.54 ▼11.38 |
| Media Library /wp-admin/upload.php | 3.40 ▲0.17 | 38.30 ▲3.36 |
Server storage [IO: ▲0.35MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 29 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| splitoff_rating_notification_timestamp |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by TogetherPay for WooCommerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲54 | 14.35 ▲0.01 | 1.74 ▼0.10 | 40.00 ▼1.25 |
| Dashboard /wp-admin | 2,192 ▲15 | 5.56 ▼0.05 | 82.66 ▼10.21 | 38.20 ▼5.15 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▲0.04 | 34.01 ▼2.99 | 32.56 ▼2.10 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.46 ▲0.17 | 669.50 ▲42.64 | 53.88 ▲2.78 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.21 ▲0.02 | 101.46 ▲3.33 | 43.75 ▲2.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- splitoff_rating_notification_timestamp
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 6× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff/instalments.html.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_editor() in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff/wysiwyg.html.php:22
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff/form_fields.php:8
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff/environments.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_script() in wp-content/plugins/splitoff-pay-woocommerce/class/WC_Gateway_SplitOff/splitoff_js_init.html.php:5
- > 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 Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
2 plugin tags: woocommerce, splitoff
splitoff-pay-woocommerce/splitoff-gateway-for-woocommerce.php 77% from 13 tests
"TogetherPay for WooCommerce" version 1.0.10's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Requires at least: Required version must be the same as the one declared in readme.txt ("4.4.0" instead of "2.6.0")
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("splitoff-pay-woocommerce.php" instead of "splitoff-gateway-for-woocommerce.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
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
There were no executable files found in this plugin3,737 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 735 | 1,939 | 3,244 |
| JavaScript | 2 | 48 | 0 | 211 |
| Markdown | 1 | 43 | 0 | 121 |
| CSS | 1 | 19 | 6 | 89 |
| XML | 4 | 0 | 0 | 72 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| Average class complexity | 199.33 |
| ▷ Minimum class complexity | 21.00 |
| ▷ Maximum class complexity | 422.00 |
| Average method complexity | 6.95 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 49.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 | 100 | |
| ▷ Static methods | 8 | 8.00% |
| ▷ Public methods | 72 | 72.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 28 | 28.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
10 PNG files occupy 0.09MB with 0.04MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon-check.png | 2.45KB | 1.50KB | ▼ 38.46% |
| class/logo.png | 12.02KB | 4.73KB | ▼ 60.63% |
| class/splitoff-logo-colour.png | 4.63KB | 2.25KB | ▼ 51.37% |
| images/icon-statistics.png | 3.17KB | 1.90KB | ▼ 40.08% |
| class/logo1.png | 12.02KB | 4.73KB | ▼ 60.63% |