Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼1.13ms] Passed 4 tests
Analyzing server-side resources used by Restrict Contributors from Scheduled Posts
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 38.89 ▼8.40 |
Dashboard /wp-admin | 3.31 ▲0.01 | 51.70 ▲2.44 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 60.74 ▲8.85 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 98.88 ▲0.62 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.22 ▲0.83 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Restrict Contributors from Scheduled Posts
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.24 ▼1.31 | 4.56 ▲2.50 | 41.22 ▼3.37 |
Dashboard /wp-admin | 2,203 ▲18 | 4.90 ▼0.96 | 108.77 ▼0.24 | 43.94 ▼1.68 |
Posts /wp-admin/edit.php | 2,092 ▼0 | 2.05 ▼0.00 | 41.70 ▲1.89 | 37.38 ▲0.01 |
Add New Post /wp-admin/post-new.php | 1,542 ▲9 | 18.38 ▼4.80 | 623.51 ▼53.23 | 50.31 ▼13.28 |
Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.20 ▲0.03 | 98.40 ▼5.90 | 44.05 ▲1.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/restrict-contributors-from-scheduled-posts/restrict-contributors.php:34
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% 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:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== restrict-contributors-from-scheduled-posts ===
)
restrict-contributors-from-scheduled-posts/restrict-contributors.php 92% from 13 tests
The entry point to "Restrict Contributors from Scheduled Posts" version 1.1 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("restrict-contributors-from-scheduled-posts.php" instead of "restrict-contributors.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin40 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 16 | 33 | 40 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 1.11 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.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
There are no PNG files in this plugin