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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.45ms] Passed 4 tests
A check of server-side resources used by Limepay WooCommerce Gateway
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.19 ▲2.35 |
Dashboard /wp-admin | 3.31 ▲0.01 | 42.61 ▼1.76 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.88 ▼2.26 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 87.62 ▼12.13 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.29 ▲4.34 |
Server storage [IO: ▲0.72MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Limepay WooCommerce Gateway
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,883 ▲126 | 13.97 ▼0.83 | 7.69 ▲5.76 | 37.55 ▼3.11 |
Dashboard /wp-admin | 2,200 ▲12 | 5.83 ▲0.90 | 108.02 ▼8.86 | 49.01 ▲3.44 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.09 | 39.43 ▼6.20 | 34.99 ▼2.56 |
Add New Post /wp-admin/post-new.php | 1,514 ▼31 | 17.72 ▼0.26 | 650.10 ▲30.54 | 61.46 ▲3.86 |
Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.24 ▲0.04 | 96.74 ▼6.84 | 41.52 ▼0.16 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
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)
Even though no errors were found, 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
Please fix the following
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/limepay-woocommerce-gateway/woocommerce-gateway-limepay.php:14
- > PHP Fatal error
Uncaught Error: Class 'WC_Payment_Gateway' not found in wp-content/plugins/limepay-woocommerce-gateway/woocommerce-limepay.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
4 plugin tags: split payments, debit card, checkout, credit card
limepay-woocommerce-gateway/woocommerce-gateway-limepay.php 85% from 13 tests
The principal PHP file in "Limepay WooCommerce Gateway" v. 3.0.3 is loaded by WordPress automatically on each request
Please take the time to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("limepay-woocommerce-gateway.php" instead of "woocommerce-gateway-limepay.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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
Success! There were no dangerous files found in this plugin964 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 97 | 66 | 499 |
CSS | 1 | 32 | 12 | 291 |
JavaScript | 2 | 23 | 8 | 112 |
Markdown | 1 | 33 | 0 | 62 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 50.00 |
▷ Minimum class complexity | 50.00 |
▷ Maximum class complexity | 50.00 |
Average method complexity | 3.88 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.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 | 17 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 9 | 52.94% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 47.06% |
Functions | 9 | |
▷ Named functions | 9 | 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
No PNG images were found in this plugin