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.22MB] [CPU: ▼7.15ms] Passed 4 tests
Analyzing server-side resources used by jQuery Manager for WordPress
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.65 ▲0.18 | 44.84 ▲1.73 |
| Dashboard /wp-admin | 3.60 ▲0.25 | 50.08 ▼11.75 |
| Posts /wp-admin/edit.php | 3.65 ▲0.29 | 55.59 ▲9.10 |
| Add New Post /wp-admin/post-new.php | 6.12 ▲0.23 | 82.91 ▼20.67 |
| Media Library /wp-admin/upload.php | 3.44 ▲0.21 | 38.34 ▲2.08 |
| jQuery Manager /wp-admin/tools.php?page=wp-jquery-manager-plugin-settings | 3.44 | 36.78 |
Server storage [IO: ▲1.92MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 58 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| wp_jquery_manager_plugin_jquery_migrate_settings |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| wp_jquery_manager_plugin_jquery_settings |
Browser metrics Passed 4 tests
This is an overview of browser requirements for jQuery Manager for WordPress
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,112 ▲341 | 15.20 ▲0.45 | 4.94 ▲2.82 | 37.24 ▼6.95 |
| Dashboard /wp-admin | 2,389 ▲204 | 6.63 ▲0.78 | 134.07 ▲15.68 | 51.87 ▲9.00 |
| Posts /wp-admin/edit.php | 2,298 ▲206 | 3.53 ▲1.53 | 57.03 ▲15.71 | 47.48 ▲10.36 |
| Add New Post /wp-admin/post-new.php | 1,557 ▲20 | 18.37 ▼0.11 | 639.57 ▼41.26 | 35.46 ▼20.42 |
| Media Library /wp-admin/upload.php | 1,431 ▲46 | 4.33 ▲0.15 | 84.15 ▼33.02 | 49.45 ▲2.28 |
| jQuery Manager /wp-admin/tools.php?page=wp-jquery-manager-plugin-settings | 1,238 | 3.59 | 51.55 | 38.30 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% 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
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/jquery-manager/tests/bootstrap.php
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/jquery-manager/tests/test-sample.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/jquery-manager/tests/php7.php:3
- > 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 93% 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: Please reduce the number of tags, currently 16 tag instead of maximum 10
jquery-manager/jquery-manager.php 92% from 13 tests
"jQuery Manager for WordPress" version 1.10.6's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 254 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected28,859 lines of code in 48 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 13 | 7,956 | 7,129 | 27,028 |
| PHP | 8 | 245 | 377 | 985 |
| Markdown | 9 | 156 | 0 | 407 |
| YAML | 9 | 32 | 41 | 143 |
| Bourne Shell | 1 | 21 | 11 | 123 |
| JSON | 4 | 0 | 0 | 89 |
| XML | 3 | 20 | 54 | 82 |
| CSS | 1 | 0 | 1 | 2 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 25.75 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 69.00 |
| Average method complexity | 2.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 44 | |
| ▷ Static methods | 6 | 13.64% |
| ▷ Public methods | 44 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 10 | |
| ▷ Named functions | 8 | 80.00% |
| ▷ Anonymous functions | 2 | 20.00% |
| Constants | 15 | |
| ▷ Global constants | 15 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin