Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.57ms] Passed 4 tests
Analyzing server-side resources used by Widget Visibility Time Scheduler
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 33.19 ▼7.38 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 44.24 ▼3.12 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.07 ▲3.42 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 94.48 ▼2.94 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.26 ▼0.85 |
Server storage [IO: ▲0.13MB] [DB: ▲0.07MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 39 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Widget Visibility Time Scheduler
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,834 ▲99 | 13.30 ▼1.13 | 1.74 ▼0.20 | 37.98 ▼7.54 |
| Dashboard /wp-admin | 2,215 ▲27 | 4.83 ▼0.25 | 105.05 ▼9.05 | 40.87 ▼5.16 |
| Posts /wp-admin/edit.php | 2,094 ▲2 | 2.01 ▼0.11 | 39.15 ▼2.11 | 37.70 ▲1.91 |
| Add New Post /wp-admin/post-new.php | 1,523 ▲9 | 17.77 ▲0.06 | 654.91 ▼18.31 | 59.83 ▲7.22 |
| Media Library /wp-admin/upload.php | 1,400 ▲9 | 4.30 ▲0.14 | 101.35 ▲4.82 | 43.74 ▲2.92 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.08MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- 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 | 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
Please take a closer look at the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/widget-visibility-time-scheduler/admin/partials/hinjiwvts-fieldsets.php:15
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need to be fixed:
- Tags: You are using too many tags: 34 tag instead of maximum 10
widget-visibility-time-scheduler/hinjiwvts.php 85% from 13 tests
Analyzing the main PHP file in "Widget Visibility Time Scheduler" version 5.3.13
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("widget-visibility-time-scheduler.php" instead of "hinjiwvts.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected1,219 lines of code in 25 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 199 | 683 | 578 |
| PO File | 9 | 133 | 168 | 573 |
| CSS | 4 | 0 | 5 | 54 |
| JavaScript | 2 | 0 | 8 | 14 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 12.57 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 61.00 |
| Average method complexity | 3.70 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 7 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 7 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 30 | |
| ▷ Static methods | 5 | 16.67% |
| ▷ Public methods | 22 | 73.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 8 | 26.67% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.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
No PNG files were detected