Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.02MB] [CPU: ▼12.84ms] Passed 4 tests
A check of server-side resources used by WP Content Scheduler With Range
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.70 ▲0.24 | 44.08 ▼4.94 |
Dashboard /wp-admin | 3.27 ▼0.03 | 32.10 ▼14.78 |
Posts /wp-admin/edit.php | 3.41 ▲0.06 | 33.95 ▼17.34 |
Add New Post /wp-admin/post-new.php | 5.65 ▼0.23 | 88.51 ▼14.30 |
Media Library /wp-admin/upload.php | 3.35 ▲0.13 | 34.66 ▼0.13 |
Scheduled posts /wp-admin/admin.php?page=scheduler-posts | 3.25 | 29.91 |
WCSWR /wp-admin/admin.php?page=wp-content-scheduler-with-range | 3.25 | 38.30 |
Server storage [IO: ▲0.58MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 41 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_theysaidso_widget |
ced_wcswr_latest_version |
widget_recent-comments |
db_upgraded |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for WP Content Scheduler With Range
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,939 ▲193 | 13.77 ▼0.79 | 5.58 ▲3.65 | 45.79 ▼0.75 |
Dashboard /wp-admin | 2,247 ▲62 | 5.13 ▲0.26 | 100.93 ▼4.88 | 83.13 ▲37.76 |
Posts /wp-admin/edit.php | 2,158 ▲66 | 2.30 ▲0.31 | 37.18 ▼1.94 | 37.38 ▲0.34 |
Add New Post /wp-admin/post-new.php | 1,721 ▲193 | 22.25 ▲3.88 | 671.89 ▲6.41 | 34.83 ▼16.74 |
Media Library /wp-admin/upload.php | 1,441 ▲53 | 4.42 ▲0.26 | 99.55 ▼18.88 | 63.74 ▲16.89 |
Scheduled posts /wp-admin/admin.php?page=scheduler-posts | 961 | 2.12 | 30.16 | 41.06 |
WCSWR /wp-admin/admin.php?page=wp-content-scheduler-with-range | 3,154 | 7.48 | 173.35 | 106.17 |
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 7 options in the database
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- ced_wcswr_latest_version
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Deprecated in wp-content/plugins/wp-content-scheduler-with-range/includes/wp-content-scheduler-with-range-class.php+107
array_key_exists(): Using array_key_exists() on objects is deprecated. Use isset() or property_exists() instead
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > User notice in wp-includes/functions.php+5905
Function WP_Scripts::localize was called incorrectly. The $l10n parameter must be an array. To pass arbitrary data to scripts, use the wp_add_inline_script() function instead. Please see Debugging in WordPress for more information. (This message was added in version 5.7.0.)
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Notice in wp-content/plugins/wp-content-scheduler-with-range/includes/settings.php+62
Undefined variable: _SESSION
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Notice in wp-content/plugins/wp-content-scheduler-with-range/includes/settings.php+62
Trying to access array offset on value of type null
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Warning in wp-content/plugins/wp-content-scheduler-with-range/includes/settings.php+690
session_start(): Cannot start session when headers already sent
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Notice in wp-content/plugins/wp-content-scheduler-with-range/includes/settings.php+634
Trying to access array offset on value of type bool
SRP Passed 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Looking good! No server-side errors or output on direct access of PHP files
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-content-scheduler-with-range
- > Network (severe)
wp-content/plugins/wp-content-scheduler-with-range/assets/js/wcswr_admin_mailer.js?ver=1.1 - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Tags: Too many tags (12 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: Add a description for screenshot #10 in wp-content-scheduler-with-range/assets to your readme.txt
wp-content-scheduler-with-range/wp-content-scheduler-with-range.php Passed 13 tests
The entry point to "WP Content Scheduler With Range" version 1.1 is a PHP file that has certain tags in its header comment area
42 characters long description:
Show or hide your posts in a range of date
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected3,422 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 215 | 256 | 1,746 |
CSS | 5 | 129 | 6 | 735 |
JavaScript | 5 | 77 | 64 | 708 |
PO File | 1 | 100 | 104 | 233 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 82.00 |
▷ Minimum class complexity | 82.00 |
▷ Maximum class complexity | 82.00 |
Average method complexity | 5.26 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.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 | 19 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 19 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 12 | |
▷ Named functions | 12 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 5 | |
▷ Global constants | 5 | 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
15 compressed PNG files occupy 0.04MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/ui-bg_glass_75_e6e6e6_1x400.png | 0.11KB | 0.14KB | 0.00% |
assets/images/ui-icons_2e83ff_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |
assets/images/cross.png | 7.04KB | 2.92KB | ▼ 58.46% |
assets/images/ui-icons_454545_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |
assets/images/ui-icons_222222_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |