Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
It is recommended to fix the following installer errors
- Install procedure validation failed for this plugin
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+8
Constant PEK_CONTENT_SCHEDULER_VERSION already defined
Server metrics [RAM: ▼1.61MB] [CPU: ▼58.74ms] Passed 4 tests
Server-side resources used by Content Scheduler
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.57 ▲0.10 | 40.00 ▼1.81 |
| Dashboard /wp-admin | 2.35 ▼1.00 | 13.23 ▼52.99 |
| Posts /wp-admin/edit.php | 2.35 ▼1.01 | 8.26 ▼47.72 |
| Add New Post /wp-admin/post-new.php | 2.35 ▼3.54 | 9.29 ▼106.18 |
| Media Library /wp-admin/upload.php | 2.35 ▼0.89 | 7.31 ▼28.08 |
| Content Scheduler /wp-admin/options-general.php?page=content_scheduler | 2.35 | 8.13 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 41 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| ContentScheduler_Options |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Content Scheduler
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.20 ▲0.22 | 1.60 ▼0.19 | 41.45 ▼0.24 |
| Dashboard /wp-admin | 2,202 ▲31 | 5.64 ▼0.03 | 90.59 ▲0.87 | 37.43 ▼4.35 |
| Posts /wp-admin/edit.php | 2,104 ▲1 | 1.98 ▼0.07 | 40.33 ▼2.36 | 36.34 ▼0.76 |
| Add New Post /wp-admin/post-new.php | 6,259 ▲4,733 | 18.98 ▲1.42 | 955.30 ▲333.26 | 63.19 ▲5.79 |
| Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.15 ▼0.07 | 108.07 ▼0.49 | 45.24 ▲1.18 |
| Content Scheduler /wp-admin/options-general.php?page=content_scheduler | 1,120 | 1.71 | 25.29 | 31.90 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+8
Constant PEK_CONTENT_SCHEDULER_VERSION already defined
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-comments
- ContentScheduler_Options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+8
Constant PEK_CONTENT_SCHEDULER_VERSION already defined
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+439
Undefined index: def-hours
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+440
Undefined index: def-days
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > Notice in wp-content/plugins/content-scheduler/content-scheduler-settings.php+441
Undefined index: def-weeks
- > GET request to /wp-admin/options-general.php?page=content_scheduler
- > Warning in wp-admin/includes/template.php+1824
call_user_func() expects parameter 1 to be a valid callback, class 'Content_Scheduler_Settings' does not have a method 'cs_view_cron_settings'
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 fix the following items
- 13× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Notice
Undefined variable: why_notify in wp-content/plugins/content-scheduler/includes/send-notifications.php on line 10
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/content-scheduler/includes/process-post.php:6
- > PHP Notice
Undefined variable: postid in wp-content/plugins/content-scheduler/includes/process-page.php on line 4
- > PHP Notice
Undefined variable: why_notify in wp-content/plugins/content-scheduler/includes/send-notifications.php on line 14
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/content-scheduler/includes/process-expirations.php:5
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/content-scheduler/includes/update-postmeta-expiration-values.php:14
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/content-scheduler/includes/process-page.php:9
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/content-scheduler/includes/process-notifications.php:5
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/content-scheduler/includes/update-minlevel-options.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/content-scheduler/includes/send-notifications.php:20
- > PHP Notice
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 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (The Content Scheduler options screen, where you determine what happens when the expiration date is reached.), #2 (Content Scheduler can optionally display the expiraton date and status in a column where your Posts and Pages are listed.), #3 (Scheduling content expiration uses a small, unobtrusive box on your Post and Pages edit screens.)
content-scheduler/content-scheduler.php 92% from 13 tests
This is the main PHP file of "Content Scheduler" version 2.0.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Description: Keep the plugin description shorter than 140 characters (currently 158 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin3,557 lines of code in 20 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 205 | 286 | 1,734 |
| PHP | 14 | 176 | 814 | 1,607 |
| PO File | 1 | 90 | 95 | 202 |
| CSS | 2 | 2 | 5 | 11 |
| Markdown | 1 | 1 | 0 | 3 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 39.33 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 69.00 |
| Average method complexity | 2.80 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 64 | |
| ▷ Static methods | 3 | 4.69% |
| ▷ Public methods | 60 | 93.75% |
| ▷ Protected methods | 3 | 4.69% |
| ▷ Private methods | 1 | 1.56% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 8 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
17 PNG files occupy 0.21MB with 0.06MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| js/images/ui-icons_228ef1_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |
| js/images/ui-icons_ef8c08_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |
| js/images/ui-bg_gloss-wave_35_f6a828_500x100.png | 5.68KB | 1.83KB | ▼ 67.77% |
| js/images/ui-icons_ffd27a_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |
| screenshot-3.png | 35.89KB | 19.01KB | ▼ 47.04% |