Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.32ms] Passed 4 tests
An overview of server-side resources used by Payment Gateway - Logistic Pro Pay
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.37 ▼5.28 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.44 ▼1.48 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.22 ▼2.19 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 90.64 ▼7.14 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 35.59 ▼2.65 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Payment Gateway - Logistic Pro Pay
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 14.48 ▼0.18 | 1.69 ▼0.16 | 40.69 ▼5.30 |
Dashboard /wp-admin | 2,206 ▲35 | 4.83 ▼1.02 | 111.79 ▲5.01 | 44.08 ▼4.89 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 2.02 ▲0.01 | 39.60 ▲3.90 | 36.11 ▲4.84 |
Add New Post /wp-admin/post-new.php | 1,542 ▲8 | 23.12 ▲0.01 | 590.55 ▼105.13 | 52.21 ▼8.95 |
Media Library /wp-admin/upload.php | 1,385 ▼0 | 4.21 ▼0.05 | 94.93 ▼4.13 | 41.22 ▼2.88 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function untrailingslashit() in wp-content/plugins/logistic-pro-pay/gateway-logistic-pro-pay.php:30
- > 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)
No browser issues were found
Optimizations
Plugin configuration 96% 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
5 plugin tags: payment, shopping cart, gateway, woocommerce, crypto currencies
logistic-pro-pay/gateway-logistic-pro-pay.php 92% from 13 tests
"Payment Gateway - Logistic Pro Pay" version 1.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("logistic-pro-pay.php" instead of "gateway-logistic-pro-pay.php")
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
Good job! No executable or dangerous file extensions detected457 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 115 | 190 | 404 |
CSS | 1 | 2 | 0 | 43 |
JavaScript | 1 | 4 | 0 | 10 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 20.50 |
▷ Minimum class complexity | 5.00 |
▷ Maximum class complexity | 36.00 |
Average method complexity | 2.86 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 21 | |
▷ Static methods | 1 | 4.76% |
▷ Public methods | 19 | 90.48% |
▷ Protected methods | 2 | 9.52% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 5 | 100.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
No PNG files were detected