Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼5.83ms] Passed 4 tests
An overview of server-side resources used by WooCommerce Payment Gateway for Saferpay
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 42.40 ▲4.25 |
Dashboard /wp-admin | 3.31 ▲0.01 | 48.81 ▼7.17 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 52.43 ▲2.99 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 86.03 ▼23.38 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 39.45 ▲5.46 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, 7 new options
New WordPress options |
---|
db_upgraded |
saferpay_page_id |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
WooCommerce Payment Gateway for Saferpay: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲39 | 14.37 ▲0.02 | 2.08 ▲0.11 | 44.56 ▼4.96 |
Dashboard /wp-admin | 2,206 ▲29 | 5.64 ▲0.06 | 85.48 ▼6.16 | 41.92 ▲1.44 |
Posts /wp-admin/edit.php | 2,111 ▲11 | 2.10 ▲0.06 | 40.67 ▲4.32 | 36.61 ▼0.83 |
Add New Post /wp-admin/post-new.php | 1,535 ▲9 | 23.97 ▲1.04 | 661.55 ▼33.53 | 54.76 ▼8.25 |
Media Library /wp-admin/upload.php | 1,402 ▲2 | 4.21 ▼0.02 | 105.85 ▼3.64 | 42.75 ▼4.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woocommerce-payment-gateway-for-saferpay/fn-plugin.php:119
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (Settings panel in WooCommerce.), #2 (Payment method on the checkout page)
woocommerce-payment-gateway-for-saferpay/fn-plugin.php 92% from 13 tests
The main PHP file in "WooCommerce Payment Gateway for Saferpay" ver. 0.4.9 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("woocommerce-payment-gateway-for-saferpay.php" instead of "fn-plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin573 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 256 | 242 | 472 |
PO File | 1 | 33 | 40 | 101 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 13.00 |
▷ Minimum class complexity | 13.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 2.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.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 | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 19 | |
▷ Named functions | 19 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 7 | |
▷ Global constants | 7 | 100.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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/credit_cards.png | 2.76KB | 0.09KB | ▼ 96.57% |