Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.38MB] [CPU: ▲0.88ms] Passed 4 tests
This is a short check of server-side resources used by JWD PostSlider Widget
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.83 ▲0.37 | 41.61 ▼0.34 |
| Dashboard /wp-admin | 3.68 ▲0.37 | 50.65 ▲2.74 |
| Posts /wp-admin/edit.php | 3.79 ▲0.43 | 51.07 ▲1.50 |
| Add New Post /wp-admin/post-new.php | 6.28 ▲0.39 | 90.54 ▼0.39 |
| Media Library /wp-admin/upload.php | 3.60 ▲0.37 | 44.24 ▲12.28 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 49 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| jwdsp_general_settings |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| widget_jwdsp_postslider |
Browser metrics Passed 4 tests
An overview of browser requirements for JWD PostSlider Widget
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,816 ▲70 | 13.20 ▼1.25 | 1.59 ▼0.54 | 40.84 ▼1.93 |
| Dashboard /wp-admin | 2,222 ▲37 | 5.91 ▲0.10 | 101.61 ▼18.48 | 43.66 ▼0.62 |
| Posts /wp-admin/edit.php | 2,105 ▲19 | 2.02 ▲0.00 | 39.95 ▲3.71 | 35.38 ▼2.09 |
| Add New Post /wp-admin/post-new.php | 6,246 ▲4,727 | 18.65 ▼4.54 | 932.02 ▲257.96 | 74.09 ▲21.21 |
| Media Library /wp-admin/upload.php | 1,407 ▲19 | 4.21 ▲0.05 | 100.80 ▼0.65 | 52.13 ▲6.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- jwdsp_general_settings
- widget_jwdsp_postslider
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 8× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_metabox.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_widget.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_ajax.php
- > /wp-content/plugins/jwd-postslider-widget/jwd_postslider.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_enqueue.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_admin_page.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_deprecated.php
- > /wp-content/plugins/jwd-postslider-widget/inc/jwdsp_hooks.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Tags: Please delete some tags, you are using 32 tag instead of maximum 10
jwd-postslider-widget/jwd_postslider.php 85% from 13 tests
The primary PHP file in "JWD PostSlider Widget" version 1.8.4 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("jwd-postslider-widget.php" instead of "jwd_postslider.php")
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
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 detected4,719 lines of code in 34 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PO File | 9 | 874 | 932 | 1,975 |
| PHP | 8 | 1 | 289 | 1,470 |
| CSS | 4 | 64 | 142 | 798 |
| JavaScript | 7 | 0 | 48 | 249 |
| SVG | 6 | 5 | 1 | 227 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.57 |
| Average class complexity | 135.00 |
| ▷ Minimum class complexity | 135.00 |
| ▷ Maximum class complexity | 135.00 |
| Average method complexity | 34.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 58.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 38 | |
| ▷ Named functions | 38 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG images were found in this plugin