Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼1.87MB] [CPU: ▼56.18ms] Passed 4 tests
Analyzing server-side resources used by Bullet FAQs
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.12 ▼1.35 | 5.11 ▼32.75 |
| Dashboard /wp-admin | 2.14 ▼1.17 | 6.20 ▼53.89 |
| Posts /wp-admin/edit.php | 2.14 ▼1.22 | 6.66 ▼38.41 |
| Add New Post /wp-admin/post-new.php | 2.14 ▼3.75 | 5.63 ▼99.65 |
| Media Library /wp-admin/upload.php | 2.14 ▼1.10 | 6.38 ▼26.54 |
| FAQ Categories /wp-admin/edit-tags.php?taxonomy=faq_categories&post_type=faq | 2.14 | 6.51 |
| FAQ Settings /wp-admin/edit.php?post_type=faq&page=faq_settings | 2.14 | 6.93 |
| All FAQs /wp-admin/edit.php?post_type=faq | 2.14 | 7.44 |
| Add New /wp-admin/post-new.php?post_type=faq | 2.14 | 6.77 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 15 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_faq_widget |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Bullet FAQs
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,957 ▲171 | 13.44 ▼0.99 | 7.44 ▲5.26 | 37.05 ▼5.69 |
| Dashboard /wp-admin | 2,252 ▲78 | 5.60 ▲0.00 | 95.62 ▲8.23 | 43.80 ▲6.34 |
| Posts /wp-admin/edit.php | 2,158 ▲58 | 2.14 ▲0.12 | 34.28 ▼6.34 | 32.65 ▼11.21 |
| Add New Post /wp-admin/post-new.php | 1,577 ▲29 | 23.80 ▲5.49 | 658.18 ▲46.32 | 49.16 ▼20.76 |
| Media Library /wp-admin/upload.php | 1,457 ▲57 | 4.23 ▲0.07 | 100.93 ▲7.83 | 41.55 ▲0.72 |
| FAQ Categories /wp-admin/edit-tags.php?taxonomy=faq_categories&post_type=faq | 1,356 | 2.29 | 30.45 | 35.25 |
| FAQ Settings /wp-admin/edit.php?post_type=faq&page=faq_settings | 920 | 2.02 | 24.99 | 27.17 |
| All FAQs /wp-admin/edit.php?post_type=faq | 1,136 | 1.93 | 29.85 | 32.89 |
| Add New /wp-admin/post-new.php?post_type=faq | 2,348 | 7.76 | 163.09 | 67.75 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/bullet-faqs/bullet_faqs.php+40
Undefined property: FAQ::$location
- This plugin does not fully uninstall, leaving 7 options in the database
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- widget_faq_widget
- can_compress_scripts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Almost there, just fix the following server-side errors
- 5 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=faq
- > Notice in wp-content/plugins/bullet-faqs/bullet_faqs.php+40
Undefined property: FAQ::$location
- 13 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=faq&page=faq_settings
- > Notice in wp-content/plugins/bullet-faqs/bullet_faqs.php+226
Trying to access array offset on value of type bool
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 5× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/bullet-faqs/bullet_faqs.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/bullet-faqs/templates/all_view.php:3
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/bullet-faqs/lib/widget.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/bullet-faqs/templates/widget_view.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/bullet-faqs/templates/category_view.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% 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:
- Plugin Name: You should set the name of your plugin on the first line (
=== bullet-faqs ===)
bullet-faqs/bullet_faqs.php 85% from 13 tests
The main PHP file in "Bullet FAQs" ver. 2.1.9 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 398 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("bullet-faqs.php" instead of "bullet_faqs.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin738 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 75 | 78 | 373 |
| PO File | 2 | 92 | 92 | 214 |
| CSS | 1 | 20 | 12 | 89 |
| JavaScript | 1 | 12 | 34 | 62 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 12.67 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 29.00 |
| Average method complexity | 2.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 10.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 25 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 25 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/q-icon.png | 0.58KB | 0.65KB | 0.00% |
| images/a-icon.png | 2.31KB | 0.49KB | ▼ 78.84% |