Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.05MB] [CPU: ▼9.51ms] Passed 4 tests
Analyzing server-side resources used by DirectPay-IPG WooCommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 41.58 ▲0.39 |
| Dashboard /wp-admin | 3.37 ▲0.02 | 52.40 ▼18.48 |
| Posts /wp-admin/edit.php | 3.42 ▲0.06 | 50.30 ▲0.22 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 86.06 ▼20.18 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 39.10 ▲2.80 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
DirectPay-IPG WooCommerce: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.19 ▼0.21 | 1.91 ▲0.09 | 43.82 ▼1.41 |
| Dashboard /wp-admin | 2,192 ▲15 | 5.56 ▼0.12 | 84.93 ▼4.65 | 37.77 ▲1.99 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.01 ▼0.03 | 35.14 ▼7.97 | 34.78 ▼3.61 |
| Add New Post /wp-admin/post-new.php | 1,550 ▼4 | 23.19 ▲4.97 | 681.85 ▲53.38 | 58.82 ▲10.63 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.21 ▲0.03 | 103.07 ▼5.81 | 47.09 ▲0.97 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however 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
Please 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/directpay-ipg-woocommerce/index.php:10
- > 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 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Plugin Name: Please specify the plugin name on the first line (
=== directpay-ipg-woocommerce ===) - Screenshots: Screenshot #3 (Settings) image missing
directpay-ipg-woocommerce/index.php 92% from 13 tests
The main file in "DirectPay-IPG WooCommerce" v. 2.0.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("directpay-ipg-woocommerce.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
There were no executable files found in this plugin327 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 63 | 70 | 327 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 26.00 |
| ▷ Minimum class complexity | 26.00 |
| ▷ Maximum class complexity | 26.00 |
| Average method complexity | 3.78 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.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 | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 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
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/logo_.png | 13.37KB | 4.96KB | ▼ 62.94% |