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 gracefully, with no errors
Server metrics [RAM: ▲0.10MB] [CPU: ▼2.22ms] Passed 4 tests
Analyzing server-side resources used by Lekirpay for WooCommerce
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.58 ▲0.11 | 36.18 ▼3.08 |
Dashboard /wp-admin | 3.41 ▲0.06 | 53.39 ▼4.50 |
Posts /wp-admin/edit.php | 3.52 ▲0.17 | 50.12 ▲1.51 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 93.93 ▼2.81 |
Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 34.87 ▲3.30 |
Server storage [IO: ▲0.23MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Lekirpay for WooCommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,796 ▲34 | 14.67 ▲0.46 | 1.78 ▲0.23 | 45.39 ▲7.11 |
Dashboard /wp-admin | 2,204 ▲27 | 5.59 ▲0.08 | 94.66 ▼9.27 | 39.89 ▼6.97 |
Posts /wp-admin/edit.php | 2,106 ▲3 | 1.98 ▲0.01 | 39.55 ▼3.93 | 36.14 ▼1.54 |
Add New Post /wp-admin/post-new.php | 1,535 ▼1 | 23.36 ▲0.26 | 593.73 ▼56.01 | 51.20 ▼4.27 |
Media Library /wp-admin/upload.php | 1,406 ▲3 | 4.23 ▲0.03 | 96.89 ▼0.85 | 40.56 ▼2.41 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_uninstall_hook() in wp-content/plugins/lekirpay-for-woocommerce/lekirpayWoo.php:39
- > 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 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Donate link: Please fix this invalid URI: ""
- Screenshots: These screenshots require images: #1 (This is the first screen shot), #2 (This is the second screen shot)
lekirpay-for-woocommerce/lekirpayWoo.php 77% from 13 tests
"Lekirpay for WooCommerce" version 3.4.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("lekirpay-for-woocommerce.php" instead of "lekirpayWoo.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 points to an invalid folder, "/languages/" does not exist
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 plugin702 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 202 | 133 | 654 |
JavaScript | 1 | 3 | 2 | 24 |
JSON | 1 | 0 | 0 | 16 |
Markdown | 1 | 4 | 0 | 8 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 19.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 51.00 |
Average method complexity | 2.96 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.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 | 28 | |
▷ Static methods | 4 | 14.29% |
▷ Public methods | 27 | 96.43% |
▷ Protected methods | 1 | 3.57% |
▷ Private methods | 0 | 0.00% |
Functions | 9 | |
▷ Named functions | 8 | 88.89% |
▷ Anonymous functions | 1 | 11.11% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 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
3 PNG files occupy 0.16MB with 0.09MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.PNG | 21.54KB | 10.52KB | ▼ 51.14% |
assets/pay_with_lekirpay.png | 89.10KB | 27.39KB | ▼ 69.26% |
screenshot-1.PNG | 54.66KB | 27.22KB | ▼ 50.20% |