Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼0.32ms] Passed 4 tests
An overview of server-side resources used by Floating Quick Buy Button for WooCommerce
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 49.27 ▲5.63 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 50.92 ▼3.44 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.75 ▼5.79 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 105.93 ▲5.77 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 39.81 ▲2.31 |
Server storage [IO: ▲0.29MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Floating Quick Buy Button for WooCommerce
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.34 ▼0.19 | 1.62 ▼0.04 | 39.87 ▼0.16 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.61 ▼0.05 | 94.95 ▲4.90 | 41.32 ▼4.28 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 2.00 ▲0.00 | 38.52 ▼0.27 | 37.00 ▲1.53 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲9 | 18.11 ▼4.88 | 648.88 ▼11.15 | 70.36 ▲16.65 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.14 ▼0.06 | 111.51 ▲4.38 | 48.12 ▲2.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
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
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 2× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/floating-quick-buy-button-for-woocommerce/admin/partials/mobile-quick-buy-kp-admin-display.php
- > /wp-content/plugins/floating-quick-buy-button-for-woocommerce/public/partials/mobile-quick-buy-kp-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Screenshots: These screenshots need descriptions #1, #2 in floating-quick-buy-button-for-woocommerce/assets to your readme.txt
floating-quick-buy-button-for-woocommerce/mobile-quick-buy-kp.php 85% from 13 tests
The main file in "Floating Quick Buy Button for WooCommerce" v. 1.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("floating-quick-buy-button-for-woocommerce.php" instead of "mobile-quick-buy-kp.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
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
No dangerous file extensions were detected967 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 12 | 164 | 526 | 441 |
| CSS | 2 | 45 | 35 | 398 |
| JavaScript | 3 | 31 | 74 | 114 |
| SVG | 1 | 2 | 0 | 14 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 6.14 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 1.97 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 37 | |
| ▷ Static methods | 2 | 5.41% |
| ▷ Public methods | 32 | 86.49% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 13.51% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.18MB with 0.13MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| admin/images/mobile-frame-final.png | 183.36KB | 54.05KB | ▼ 70.52% |