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.16MB] [CPU: ▼5.27ms] Passed 4 tests
Server-side resources used by Widgetkits
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.63 ▲0.17 | 35.11 ▲1.09 |
Dashboard /wp-admin | 3.46 ▲0.16 | 46.64 ▼2.65 |
Posts /wp-admin/edit.php | 3.57 ▲0.22 | 45.37 ▼6.21 |
Add New Post /wp-admin/post-new.php | 6.04 ▲0.15 | 92.03 ▼13.29 |
Media Library /wp-admin/upload.php | 3.38 ▲0.15 | 34.86 ▲1.30 |
Server storage [IO: ▲0.56MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 21 new files
Database: no new tables, 9 new options
New WordPress options |
---|
can_compress_scripts |
widget_widgetkits_socail |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_widgetkits_recent_post |
widget_theysaidso_widget |
widget_widgetkits_about |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Widgetkits
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,822 ▲51 | 13.16 ▼1.25 | 1.63 ▼0.11 | 39.93 ▼4.12 |
Dashboard /wp-admin | 2,221 ▲33 | 5.80 ▲0.92 | 97.03 ▼11.24 | 39.73 ▼3.31 |
Posts /wp-admin/edit.php | 2,106 ▲14 | 2.11 ▲0.08 | 40.81 ▲2.88 | 34.47 ▲2.88 |
Add New Post /wp-admin/post-new.php | 1,546 ▲32 | 23.31 ▲5.62 | 659.72 ▼12.40 | 49.26 ▼2.17 |
Media Library /wp-admin/upload.php | 1,409 ▲21 | 4.25 ▲0.04 | 96.17 ▼9.93 | 43.75 ▼3.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin did not uninstall successfully, leaving 9 options in the database
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_widgetkits_socail
- widget_recent-comments
- widget_widgetkits_about
- widget_widgetkits_recent_post
- widget_recent-posts
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
The following issues need your attention
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/widgetkits/widgets/hello.php
- 6× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/widgetkits/inc/Clasess/class-widgetkits-socail.php:11
- > PHP Warning
Use of undefined constant WIGETKITS_WIDGET_INC - assumed 'WIGETKITS_WIDGET_INC' (this will throw an Error in a future version of PHP) in wp-content/plugins/widgetkits/inc/sidebar-widget-file.php on line 2
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/widgetkits/inc/Clasess/class-widgetkits-about.php:11
- > PHP Warning
require_once(WIGETKITS_WIDGET_INCClasess/class-widgetkits-recent-post.php): failed to open stream: No such file or directory in wp-content/plugins/widgetkits/inc/sidebar-widget-file.php on line 2
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/widgetkits/inc/Clasess/class-widgetkits-recent-post.php:12
- > PHP Fatal error
require_once(): Failed opening required 'WIGETKITS_WIDGET_INCClasess/class-widgetkits-recent-post.php' (include_path='.:/usr/share/php') in wp-content/plugins/widgetkits/inc/sidebar-widget-file.php on line 2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Screenshots: These screenshots need descriptions #1, #2, #3 in widgetkits/assets to your readme.txt
widgetkits/widgetkits.php Passed 13 tests
The main file in "Widgetkits" v. 1.1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
88 characters long description:
The Widgetkits is an Elementor helping plugin that will make your designing work easier.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin4,336 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 268 | 305 | 2,175 |
CSS | 2 | 28 | 27 | 1,486 |
SVG | 1 | 0 | 0 | 362 |
JavaScript | 2 | 76 | 23 | 313 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 17.14 |
▷ Minimum class complexity | 7.00 |
▷ Maximum class complexity | 45.00 |
Average method complexity | 3.46 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 19.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 1 | 14.29% |
Methods | 46 | |
▷ Static methods | 2 | 4.35% |
▷ Public methods | 42 | 91.30% |
▷ Protected methods | 4 | 8.70% |
▷ Private methods | 0 | 0.00% |
Functions | 12 | |
▷ Named functions | 12 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 10 | |
▷ Global constants | 7 | 70.00% |
▷ Class constants | 3 | 30.00% |
▷ Public constants | 3 | 100.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
There were not PNG files found in your plugin