Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.92ms] Passed 4 tests
Analyzing server-side resources used by Periodical Widget Visibility
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.03 | 37.78 ▼0.21 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 43.53 ▼3.53 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.20 ▼4.86 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.53 ▼7.07 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.86 ▲2.43 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 24 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Periodical Widget Visibility
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,809 ▲74 | 13.28 ▲0.02 | 4.89 ▲2.96 | 44.32 ▼4.94 |
| Dashboard /wp-admin | 2,212 ▲21 | 4.91 ▼1.05 | 122.21 ▲17.83 | 52.70 ▲12.26 |
| Posts /wp-admin/edit.php | 2,100 ▲8 | 2.01 ▲0.03 | 39.72 ▲0.14 | 37.90 ▲1.60 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲9 | 23.29 ▲0.14 | 661.93 ▲20.22 | 54.76 ▼5.64 |
| Media Library /wp-admin/upload.php | 1,397 ▲6 | 4.32 ▲0.09 | 96.05 ▲2.11 | 43.22 ▲1.53 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- 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
Good news, no errors were detected
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
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/periodical-widget-visibility/admin/partials/formfields.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that require attention:
- Tags: You are using too many tags: 21 tag instead of maximum 10
periodical-widget-visibility/periodical-widget-visibility.php Passed 13 tests
The entry point to "Periodical Widget Visibility" version 2.3.7 is a PHP file that has certain tags in its header comment area
102 characters long description:
Control the periodical visibility of each widget based on weekdays within a yearly time period easily.
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
Good job! No executable or dangerous file extensions detected767 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 197 | 612 | 548 |
| PO File | 2 | 38 | 48 | 132 |
| Markdown | 1 | 34 | 0 | 55 |
| CSS | 1 | 0 | 2 | 19 |
| JavaScript | 1 | 0 | 8 | 13 |
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.38 |
| Average class complexity | 11.43 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 54.00 |
| Average method complexity | 3.35 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 26.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 | 31 | |
| ▷ Static methods | 4 | 12.90% |
| ▷ Public methods | 22 | 70.97% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 9 | 29.03% |
| 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG images were found in this plugin