Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.06ms] Passed 4 tests
Server-side resources used by Postepay Gateway per Woocommerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.70 ▼0.23 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 47.47 ▲0.39 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 53.59 ▲5.98 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.72 ▼13.34 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.67 ▲0.95 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Postepay Gateway per Woocommerce: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.30 ▼1.08 | 1.68 ▼0.04 | 42.96 ▲0.72 |
| Dashboard /wp-admin | 2,203 ▲12 | 5.77 ▲0.74 | 96.99 ▼4.65 | 40.64 ▼0.80 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.04 ▲0.01 | 45.25 ▲4.16 | 39.63 ▲5.13 |
| Add New Post /wp-admin/post-new.php | 1,520 ▲1 | 23.63 ▲0.36 | 645.55 ▼7.75 | 50.82 ▼14.97 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.19 ▼0.13 | 95.85 ▼9.32 | 43.40 ▼6.08 |
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
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/postepay-woocommerce-gateway/wc-postepay.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== postepay-woocommerce-gateway ===)
postepay-woocommerce-gateway/wc-postepay.php 92% from 13 tests
The main PHP file in "Postepay Gateway per Woocommerce" ver. 5.1 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("postepay-woocommerce-gateway.php" instead of "wc-postepay.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
There were no executable files found in this plugin118 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 39 | 39 | 118 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 2.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.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 | 6 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.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
There were not PNG files found in your plugin