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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼6.14ms] Passed 4 tests
An overview of server-side resources used by Product FAQ for Woocommerce
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 38.01 ▼1.59 |
Dashboard /wp-admin | 3.37 ▲0.06 | 47.79 ▲0.01 |
Posts /wp-admin/edit.php | 3.48 ▲0.12 | 48.93 ▼1.76 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 89.09 ▼21.20 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 40.99 ▲5.60 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Product FAQ for Woocommerce
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,890 ▲155 | 13.55 ▼1.11 | 5.49 ▲3.73 | 38.66 ▼2.68 |
Dashboard /wp-admin | 2,213 ▲25 | 4.87 ▲0.01 | 102.09 ▼4.57 | 38.55 ▼1.50 |
Posts /wp-admin/edit.php | 2,086 ▼6 | 2.01 ▼0.04 | 35.91 ▼4.56 | 32.87 ▼2.87 |
Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.29 ▲5.75 | 677.50 ▲79.79 | 55.41 ▼6.02 |
Media Library /wp-admin/upload.php | 1,395 ▲4 | 4.23 ▲0.07 | 92.92 ▼4.10 | 41.76 ▼6.34 |
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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% 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
These attributes need to be fixed:
- Screenshots: These screenshots require images: #1 (Backend), #2 (Frontend)
product-faq/woo-product-faq.php 85% from 13 tests
The main file in "Product FAQ for Woocommerce" v. 1.1 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: The principal plugin file should be the same as the plugin slug ("product-faq.php" instead of "woo-product-faq.php")
- 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 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin413 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 100 | 102 | 240 |
CSS | 4 | 4 | 2 | 84 |
Sass | 1 | 4 | 0 | 53 |
JavaScript | 4 | 5 | 1 | 36 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 10.33 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 16.00 |
Average method complexity | 2.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 1 | 33.33% |
Methods | 16 | |
▷ Static methods | 2 | 12.50% |
▷ Public methods | 14 | 87.50% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 12.50% |
Functions | 1 | |
▷ Named functions | 1 | 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
2 PNG files occupy 0.04MB with 0.03MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 20.24KB | 5.21KB | ▼ 74.24% |
screenshot-2.png | 22.44KB | 6.46KB | ▼ 71.21% |