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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.07MB] [CPU: ▼10.06ms] Passed 4 tests
This is a short check of server-side resources used by iPint Payment Gateway
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.08 | 38.76 ▼6.82 |
Dashboard /wp-admin | 3.37 ▲0.07 | 45.43 ▼2.15 |
Posts /wp-admin/edit.php | 3.48 ▲0.13 | 45.67 ▼3.20 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 83.87 ▼28.06 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 34.11 ▲2.84 |
Server storage [IO: ▲0.15MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 9 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for iPint Payment Gateway
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲68 | 13.65 ▼0.70 | 4.56 ▲2.36 | 41.39 ▼1.14 |
Dashboard /wp-admin | 2,200 ▲12 | 5.84 ▲0.79 | 99.21 ▼12.71 | 37.72 ▼7.50 |
Posts /wp-admin/edit.php | 2,092 ▲3 | 2.05 ▲0.06 | 39.90 ▲3.28 | 36.51 ▲2.37 |
Add New Post /wp-admin/post-new.php | 1,533 ▼3 | 23.14 ▲0.02 | 667.28 ▲38.14 | 52.19 ▼0.48 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.25 ▲0.06 | 97.27 ▼8.79 | 42.79 ▲1.50 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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 | 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 server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_log() in wp-content/plugins/ipint-payments-gateway/templates/ipint-website-redirect-url.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 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
Attributes that require attention:
- Tags: Please reduce the number of tags, currently 12 tag instead of maximum 10
- Screenshots: Please add images for these screenshots: #1 (This screen shot description corresponds to assets/Screenshot_1.png), #2 (This screen shot description corresponds to assets/Screenshot_2.png)
ipint-payments-gateway/ipint-woocommerce-gateway.php 77% from 13 tests
The primary PHP file in "iPint Payment Gateway" version 1.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("ipint-payments-gateway.php" instead of "ipint-woocommerce-gateway.php")
- Domain Path: The domain path is invalid: folder "/i18n/languages/" does not exist
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Success! There were no dangerous files found in this plugin561 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 54 | 165 | 561 |
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.25 |
Average class complexity | 13.25 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 30.00 |
Average method complexity | 2.32 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 4 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 4 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 36 | |
▷ Static methods | 20 | 55.56% |
▷ Public methods | 36 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 1 | 25.00% |
▷ Anonymous functions | 3 | 75.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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.12MB with 0.07MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/Screenshot_2.png | 51.41KB | 20.26KB | ▼ 60.59% |
assets/Screenshot_1.png | 72.97KB | 28.85KB | ▼ 60.46% |