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
Install script ran successfully
Server metrics [RAM: ▲0.37MB] [CPU: ▲0.74ms] Passed 4 tests
This is a short check of server-side resources used by WP responsive FAQ with category plugin
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.78 ▲0.31 | 42.20 ▲0.07 |
| Dashboard /wp-admin | 3.72 ▲0.42 | 46.19 ▼1.22 |
| Posts /wp-admin/edit.php | 3.78 ▲0.42 | 50.10 ▲1.76 |
| Add New Post /wp-admin/post-new.php | 6.27 ▲0.39 | 94.74 ▲13.60 |
| Media Library /wp-admin/upload.php | 3.58 ▲0.35 | 35.91 ▲2.35 |
Server storage [IO: ▲0.64MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 67 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| wpos_anylc_site_uid |
| wpos_anylc_redirect |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
WP responsive FAQ with category plugin: 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 / | 1,569 ▼1,193 | 10.15 ▼4.05 | 1.73 ▲0.05 | 18.74 ▼32.06 |
| Dashboard /wp-admin | 2,218 ▲41 | 5.54 ▼0.09 | 105.38 ▲7.43 | 54.09 ▲8.64 |
| Posts /wp-admin/edit.php | 2,122 ▲22 | 1.97 ▼0.05 | 39.15 ▼2.12 | 35.85 ▲0.38 |
| Add New Post /wp-admin/post-new.php | 6,215 ▲4,689 | 19.06 ▼4.79 | 907.34 ▲309.93 | 52.37 ▼5.06 |
| Media Library /wp-admin/upload.php | 1,422 ▲19 | 4.25 ▲0.08 | 95.41 ▼2.28 | 39.80 ▼1.47 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options were found after uninstall: 8 options
- theysaidso_admin_options
- wpos_anylc_site_uid
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- wpos_anylc_redirect
- db_upgraded
- can_compress_scripts
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)
Good news, no errors were detected
SRP Passed 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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that need to be fixed:
- Tags: Too many tags (15 tag instead of maximum 10); only the first 5 tags are used in your directory listing
sp-faq/faq.php 92% from 13 tests
The main file in "WP responsive FAQ with category plugin" v. 3.9 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("sp-faq.php" instead of "faq.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected3,479 lines of code in 42 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 29 | 657 | 1,099 | 2,925 |
| JavaScript | 6 | 127 | 23 | 376 |
| CSS | 5 | 12 | 7 | 176 |
| JSON | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.49 |
| Average class complexity | 16.62 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 87.00 |
| Average method complexity | 3.78 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 2 | 25.00% |
| Methods | 45 | |
| ▷ Static methods | 2 | 4.44% |
| ▷ Public methods | 41 | 91.11% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 4 | 8.89% |
| Functions | 37 | |
| ▷ Named functions | 37 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 19 | |
| ▷ Global constants | 19 | 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
22 PNG files occupy 0.31MB with 0.16MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/image-upgrade.png | 166.27KB | 48.08KB | ▼ 71.08% |
| wpos-plugins/assets/images/sliderspack.png | 5.55KB | 2.79KB | ▼ 49.75% |
| assets/images/SlidersPack-50.png | 6.48KB | 2.79KB | ▼ 56.91% |
| wpos-plugins/assets/images/cart-2.png | 2.20KB | 1.82KB | ▼ 17.38% |
| wpos-analytics/assets/images/icon.png | 11.03KB | 4.38KB | ▼ 60.24% |