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
Installer ran successfully
Server metrics [RAM: ▲1.29MB] [CPU: ▲2.71ms] Passed 4 tests
This is a short check of server-side resources used by WordPress Events Calendar Plugin - connectDaily
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.78 ▲1.31 | 52.50 ▲8.05 |
| Dashboard /wp-admin | 4.63 ▲1.32 | 58.16 ▼6.20 |
| Posts /wp-admin/edit.php | 4.69 ▲1.33 | 60.45 ▲10.94 |
| Add New Post /wp-admin/post-new.php | 7.17 ▲1.28 | 104.08 ▼1.95 |
| Media Library /wp-admin/upload.php | 4.49 ▲1.26 | 49.91 ▲13.87 |
| Support /wp-admin/admin.php?page=cdaily-settings-support | 4.48 | 41.75 |
| Settings 1 /wp-admin/admin.php?page=cdaily-settings | 4.48 | 45.54 |
| Overview 1 /wp-admin/admin.php?page=cdaily-menu | 4.47 | 40.51 |
Server storage [IO: ▲1.20MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 69 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
| cdaily_settings |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
WordPress Events Calendar Plugin - connectDaily: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,257 ▲471 | 14.09 ▼0.28 | 14.55 ▲12.80 | 42.05 ▼1.33 |
| Dashboard /wp-admin | 2,552 ▲371 | 5.84 ▲0.12 | 92.31 ▼5.86 | 44.68 ▲4.24 |
| Posts /wp-admin/edit.php | 2,311 ▲211 | 2.43 ▲0.42 | 38.44 ▼2.50 | 35.65 ▼4.83 |
| Add New Post /wp-admin/post-new.php | 1,601 ▲66 | 23.77 ▲5.78 | 685.74 ▲64.79 | 38.92 ▼31.64 |
| Media Library /wp-admin/upload.php | 1,761 ▲361 | 4.49 ▲0.30 | 103.25 ▼7.61 | 43.94 ▼3.65 |
| Support /wp-admin/admin.php?page=cdaily-settings-support | 1,120 | 1.97 | 25.98 | 30.35 |
| Settings 1 /wp-admin/admin.php?page=cdaily-settings | 1,570 | 2.12 | 28.55 | 34.60 |
| Overview 1 /wp-admin/admin.php?page=cdaily-menu | 1,354 | 2.01 | 29.04 | 31.17 |
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
Please fix the following items
- Zombie WordPress options detected upon uninstall: 7 options
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- cdaily_settings
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 12× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/display-calendar.php:22
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/connect-daily-web-calendar/support.php:21
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-icalendar-widget.php:23
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-eventsrenderer.php:23
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-eventsrenderer.php:23
- > PHP Fatal error
Uncaught Error: Class 'CDailyPlugin' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-wordpress-plugin.php:29
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-eventsrenderer.php:23
- > PHP Fatal error
Uncaught Error: Class 'CDailyPlugin' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-wordpress-plugin.php:29
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-eventsrenderer.php:23
- > PHP Fatal error
Uncaught Error: Class 'CDailyBaseRenderer' not found in wp-content/plugins/connect-daily-web-calendar/class-cdaily-eventsrenderer.php:23
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Please fix the following browser errors
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=cdaily-menu
- > Network (severe)
wp-admin/admin-ajax.php?action=cdaily&subaction=cd_admintypedata&ver=1.4.7 - Failed to load resource: the server responded with a status of 400 (Bad Request)
- > GET request to /wp-admin/admin.php?page=cdaily-settings-support
- > Security (severe) in unknown
/wp-admin/admin.php?page=cdaily-settings-support - Refused to execute script from '/wp-admin/admin-ajax.php?action=cdaily&subaction=cd_admintypedata&ver=1.4.7' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
- > GET request to /wp-admin/admin.php?page=cdaily-settings
- > Security (severe) in unknown
/wp-admin/admin.php?page=cdaily-settings - Refused to execute script from '/wp-admin/admin-ajax.php?action=cdaily&subaction=cd_admintypedata&ver=1.4.7' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
- > GET request to /wp-admin/admin.php?page=cdaily-menu
- > Security (severe) in unknown
/wp-admin/admin.php?page=cdaily-menu - Refused to execute script from '/wp-admin/admin-ajax.php?action=cdaily&subaction=cd_admintypedata&ver=1.4.7' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
Optimizations
Plugin configuration 90% 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 require attention:
- Tags: There are too many tags (11 tag instead of maximum 10)
connect-daily-web-calendar/cdaily.php 85% from 13 tests
The main PHP file in "WordPress Events Calendar Plugin - connectDaily" ver. 1.4.6 adds more information about the plugin and also serves as the entry point for this plugin
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 ("connect-daily-web-calendar.php" instead of "cdaily.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 215 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
No dangerous file extensions were detected9,858 lines of code in 54 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 27 | 727 | 2,160 | 5,869 |
| PO File | 4 | 800 | 1,452 | 1,612 |
| JavaScript | 4 | 127 | 391 | 1,326 |
| CSS | 3 | 50 | 35 | 477 |
| HTML | 5 | 8 | 0 | 362 |
| SVG | 5 | 1 | 5 | 180 |
| Bourne Shell | 2 | 0 | 29 | 28 |
| JSON | 4 | 0 | 0 | 4 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 31.04 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 193.00 |
| Average method complexity | 3.80 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 32.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 27 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 27 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 302 | |
| ▷ Static methods | 14 | 4.64% |
| ▷ Public methods | 244 | 80.79% |
| ▷ Protected methods | 9 | 2.98% |
| ▷ Private methods | 49 | 16.23% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 31 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 31 | 100.00% |
| ▷ Public constants | 31 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
4 PNG files occupy 0.34MB with 0.13MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/WPPluginTutorial_N.png | 171.98KB | 63.46KB | ▼ 63.10% |
| tick_16.png | 0.51KB | 0.44KB | ▼ 15.05% |
| images/WPPluginTutorial_H.png | 172.30KB | 62.66KB | ▼ 63.63% |
| images/search.png | 0.31KB | 0.26KB | ▼ 15.58% |