Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.01MB] [CPU: ▼3.75ms] Passed 4 tests
A check of server-side resources used by Query Strings Remover
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.39 ▼0.07 | 26.67 ▼12.22 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 46.82 ▼1.06 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 49.79 ▲6.43 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 91.92 ▼2.84 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.37 ▲1.14 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Query Strings Remover
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,637 ▼98 | 7.97 ▼6.42 | 1.15 ▼0.62 | 6.81 ▼37.63 |
| Dashboard /wp-admin | 2,209 ▲17 | 4.87 ▼0.09 | 112.53 ▲10.80 | 41.21 ▼5.84 |
| Posts /wp-admin/edit.php | 2,089 ▲3 | 2.02 ▲0.04 | 34.97 ▼2.23 | 33.50 ▲0.92 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲20 | 23.19 ▲0.04 | 577.38 ▼103.78 | 60.54 ▼4.01 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.21 ▼0.01 | 93.51 ▼11.92 | 44.12 ▲0.59 |
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
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
Please fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/query-string-remover-from-static-resources/hibiscus-query-string-remover.php:14
- > 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 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need your attention:
- Tags: There are too many tags (11 tag instead of maximum 10)
query-string-remover-from-static-resources/hibiscus-query-string-remover.php 85% from 13 tests
The main file in "Query Strings Remover" v. 1.7 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 270 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("query-string-remover-from-static-resources.php" instead of "hibiscus-query-string-remover.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected24 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 2 | 8 | 24 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| 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 | 3 | |
| ▷ Named functions | 3 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There are no PNG files in this plugin