Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.57ms] Passed 4 tests
An overview of server-side resources used by pipwave WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 36.80 ▼1.36 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 45.88 ▼2.71 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.88 ▼2.86 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 84.15 ▼15.33 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.52 ▲3.12 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by pipwave WooCommerce
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 13.63 ▼0.76 | 1.69 ▲0.02 | 42.00 ▼0.77 |
| Dashboard /wp-admin | 2,206 ▲15 | 5.87 ▲0.98 | 104.22 ▼10.06 | 39.22 ▼3.37 |
| Posts /wp-admin/edit.php | 2,094 ▲2 | 2.00 ▼0.02 | 42.09 ▲7.50 | 34.49 ▼1.35 |
| Add New Post /wp-admin/post-new.php | 1,520 ▲6 | 23.44 ▲5.95 | 649.87 ▼37.78 | 53.15 ▼3.53 |
| Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.26 ▲0.05 | 95.85 ▼5.02 | 43.18 ▼0.86 |
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
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
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 | 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
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pipwave-woocommerce/wc-pipwave.php:25
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: Screenshot #8 (Sample checkout page after order is placed. Payment methods will be shown for buyer to choose to make payment.) image not found
- Tags: You are using too many tags: 13 tag instead of maximum 10
- Screenshots: Please describe screenshot #7 in pipwave-woocommerce/assets to your readme.txt
pipwave-woocommerce/wc-pipwave.php 92% from 13 tests
"pipwave WooCommerce" version 1.1.4's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("pipwave-woocommerce.php" instead of "wc-pipwave.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected410 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 38 | 52 | 410 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 48.00 |
| ▷ Minimum class complexity | 48.00 |
| ▷ Maximum class complexity | 48.00 |
| Average method complexity | 4.62 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 33.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 | 13 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 84.62% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 15.38% |
| Functions | 4 | |
| ▷ Named functions | 4 | 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
PNG files should be compressed to save space and minimize bandwidth usage
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 |
| images/pipwave.png | 3.16KB | 2.20KB | ▼ 30.20% |