Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▼0.11MB] [CPU: ▼7.70ms] Passed 4 tests
A check of server-side resources used by Auto Schedule
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 39.52 ▲2.35 |
| Dashboard /wp-admin | 3.25 ▼0.05 | 32.55 ▼15.64 |
| Posts /wp-admin/edit.php | 3.32 ▼0.03 | 35.79 ▼5.90 |
| Add New Post /wp-admin/post-new.php | 5.49 ▼0.39 | 80.60 ▼7.74 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 30.64 ▼1.51 |
| Auto Schedule /wp-admin/options-general.php?page=auto-schedule | 3.23 | 30.94 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Auto Schedule
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.21 ▼1.09 | 1.86 ▲0.25 | 40.58 ▲2.45 |
| Dashboard /wp-admin | 2,210 ▲19 | 5.88 ▲0.07 | 104.14 ▼13.54 | 40.38 ▼5.74 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.01 ▼0.03 | 37.33 ▲1.96 | 34.40 ▲3.51 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲31 | 18.10 ▲0.50 | 618.90 ▼49.65 | 51.79 ▼10.42 |
| Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.24 ▼0.13 | 95.47 ▼7.14 | 39.43 ▼3.29 |
| Auto Schedule /wp-admin/options-general.php?page=auto-schedule | 2,356 | 2.19 | 23.39 | 27.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
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 errors were triggered by the plugin
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=auto-schedule
- > Notice in wp-content/plugins/auto-scheduling/functions/plugins.php+18
Undefined variable: new_edit
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
The following issues need your attention
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/auto-scheduling/views/admin_page.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/auto-scheduling/autoschedule.php:12
- > 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 96% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
6 plugin tags: future, schedule, custom, default, automatic...
auto-scheduling/autoschedule.php 92% from 13 tests
The primary PHP file in "Auto Schedule" version 1.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("auto-scheduling.php" instead of "autoschedule.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected893 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| Markdown | 1 | 121 | 0 | 553 |
| PHP | 4 | 37 | 20 | 247 |
| JavaScript | 1 | 20 | 0 | 93 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 15.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 23.00 |
| Average method complexity | 2.33 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 12.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 21 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 16 | 76.19% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 23.81% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected