Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.54ms] Passed 4 tests
Server-side resources used by Jetpack Widget Visibility - Query Args
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 36.36 ▼2.86 |
| Dashboard /wp-admin | 3.33 ▲0.02 | 44.31 ▼3.16 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 49.66 ▼5.76 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 93.43 ▲2.35 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 36.36 ▲1.61 |
Server storage [IO: ▲0.38MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Jetpack Widget Visibility - Query Args
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲90 | 13.54 ▼1.11 | 4.71 ▲3.07 | 42.23 ▼3.58 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.84 ▼0.19 | 108.95 ▼7.81 | 41.78 ▼6.36 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.05 ▼0.00 | 44.44 ▲5.05 | 36.46 ▲3.22 |
| Add New Post /wp-admin/post-new.php | 1,519 ▼10 | 23.24 ▲5.05 | 589.51 ▼54.20 | 52.44 ▼15.06 |
| Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.20 ▲0.01 | 93.60 ▼11.14 | 40.43 ▼2.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 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)
Even though everything seems fine, this is not an exhaustive test
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
The following issues need your attention
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/jetpack-widget-visibility-additional-fields-query-args/jetpack-widget-visibility-query-args.php:83
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
4 plugin tags: visibility, extend, jetpack, widget
jetpack-widget-visibility-additional-fields-query-args/jetpack-widget-visibility-query-args.php 92% from 13 tests
The main PHP script in "Jetpack Widget Visibility - Query Args" version 1.0.0 is automatically included on every request by WordPress
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("jetpack-widget-visibility-additional-fields-query-args.php" instead of "jetpack-widget-visibility-query-args.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected64 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 18 | 8 | 64 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| 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 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.08MB with 0.05MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.png | 30.79KB | 8.60KB | ▼ 72.08% |
| assets/screenshot-1.png | 10.93KB | 3.20KB | ▼ 70.76% |
| assets/wpml-lang.png | 35.40KB | 10.20KB | ▼ 71.19% |