Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼1.93MB] [CPU: ▼56.75ms] Passed 4 tests
A check of server-side resources used by PPM FAQ
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.06 ▼1.40 | 4.07 ▼42.42 |
| Dashboard /wp-admin | 2.08 ▼1.23 | 7.34 ▼47.72 |
| Posts /wp-admin/edit.php | 2.08 ▼1.28 | 5.10 ▼40.71 |
| Add New Post /wp-admin/post-new.php | 2.08 ▼3.81 | 5.36 ▼96.14 |
| Media Library /wp-admin/upload.php | 2.08 ▼1.15 | 7.67 ▼31.69 |
| Add New /wp-admin/post-new.php?post_type=ppm-faq | 2.08 | 5.54 |
| FAQs /wp-admin/edit.php?post_type=ppm-faq | 2.08 | 7.01 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for PPM FAQ
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,921 ▲186 | 13.99 ▼0.18 | 9.11 ▲7.19 | 40.58 ▼8.83 |
| Dashboard /wp-admin | 2,240 ▲52 | 4.87 ▼0.99 | 126.86 ▲9.96 | 45.13 ▼2.49 |
| Posts /wp-admin/edit.php | 2,120 ▲31 | 2.05 ▲0.04 | 50.57 ▲14.02 | 37.78 ▲2.46 |
| Add New Post /wp-admin/post-new.php | 1,541 ▲8 | 22.95 ▼0.25 | 632.82 ▼37.67 | 70.55 ▲12.36 |
| Media Library /wp-admin/upload.php | 1,419 ▲31 | 4.30 ▲0.11 | 133.55 ▲8.99 | 55.28 ▲4.48 |
| Add New /wp-admin/post-new.php?post_type=ppm-faq | 2,227 | 7.63 | 186.35 | 70.16 |
| FAQs /wp-admin/edit.php?post_type=ppm-faq | 1,084 | 2.00 | 35.29 | 31.47 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the ppm-faq-plugin-script-active handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Smoke test failed, please fix the following
- 3 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-admin/admin-ajax.php
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the ppm-faq-plugin-script-active handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 3 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-admin/admin-ajax.php
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the ppm-faq-plugin-style handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 19 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-cron.php?doing_wp_cron=1696658530.1360850334167480468750
- > Notice in wp-content/plugins/pressforward/Core/Utility/Retrieval.php+204
Undefined offset: 0
- 19 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-cron.php?doing_wp_cron=1696658530.1360850334167480468750
- > Notice in wp-content/plugins/pressforward/Core/Utility/Retrieval.php+205
Trying to get property 'guid' of non-object
- 74 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-cron.php?doing_wp_cron=1696658530.1360850334167480468750
- > Notice in wp-content/plugins/pressforward/Core/Utility/Retrieval.php+206
Trying to get property 'ID' of non-object
- 18 occurences, only the last one shown
- > GET request to /wp-admin/edit.php?post_type=ppm-faq
- > POST request to /wp-cron.php?doing_wp_cron=1696658530.1360850334167480468750
- > Notice in wp-content/plugins/pressforward/Core/Utility/Retrieval.php+222
Trying to get property 'post_title' of non-object
SRP 50% from 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 following issues need your attention
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/ppm-faq/faq-type.php:31
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/ppm-faq/plugin-hook.php:13
- > PHP Warning
Use of undefined constant WP_PLUGIN_URL - assumed 'WP_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/ppm-faq/plugin-hook.php on line 13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% 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
Attributes that require attention:
- Screenshots: These screenshots do not have images: #1 (PPM FAQ in a post), #2 (PPM FAQ Admin Panel Screenshot.)
- Donate link: Please fix this invalid URI: ""
ppm-faq/plugin-hook.php 92% from 13 tests
This is the main PHP file of "PPM FAQ" version 1.1, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("ppm-faq.php" instead of "plugin-hook.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin108 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 19 | 19 | 71 |
| JavaScript | 2 | 6 | 25 | 36 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.05 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 8 | |
| ▷ Named functions | 8 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 8 | 100.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 |
| js/faq.png | 1.32KB | 0.61KB | ▼ 54.04% |