Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼0.41ms] Passed 4 tests
An overview of server-side resources used by Schedule Notice Banner
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 42.43 ▲2.63 |
| Dashboard /wp-admin | 3.35 ▲0.01 | 49.78 ▼11.50 |
| Posts /wp-admin/edit.php | 3.47 ▲0.12 | 49.30 ▲6.46 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 101.99 ▲9.38 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.60 ▲0.77 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Schedule Notice Banner
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,065 ▲319 | 15.34 ▲0.95 | 5.70 ▲3.75 | 38.00 ▼4.73 |
| Dashboard /wp-admin | 2,366 ▲178 | 6.58 ▲0.72 | 134.35 ▲30.34 | 41.53 ▲1.97 |
| Posts /wp-admin/edit.php | 2,269 ▲180 | 3.50 ▲1.45 | 53.39 ▲18.76 | 35.31 ▲1.40 |
| Add New Post /wp-admin/post-new.php | 1,532 ▲13 | 23.35 ▲0.15 | 658.54 ▼29.67 | 37.57 ▼29.46 |
| Media Library /wp-admin/upload.php | 1,405 ▲17 | 4.23 ▲0.01 | 87.93 ▼26.22 | 45.01 ▼3.74 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
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
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/schedule-notice-banner/includes/banner-settings.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/schedule-notice-banner/includes/schedule-notice-banner-display-content.php:59
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/schedule-notice-banner/includes/schedule-notice-banner-settings.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/schedule-notice-banner/includes/loadscripts.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
3 plugin tags: banner, promotions, store notice
schedule-notice-banner/schedule-notice-banner.php 92% from 13 tests
This is the main PHP file of "Schedule Notice Banner" version 1.0, 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: If Twitter did it, so should we! Keep the description under 140 characters (currently 193 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,997 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 178 | 156 | 1,532 |
| CSS | 2 | 55 | 31 | 262 |
| PHP | 5 | 50 | 11 | 203 |
PHP code Passed 2 tests
Analyzing 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.22 |
| 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 | 8 | |
| ▷ Named functions | 7 | 87.50% |
| ▷ Anonymous functions | 1 | 12.50% |
| 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected