Benchmarks
Plugin footprint 23% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
You still need to fix the following installer errors
- Install procedure had errors
- > Notice in wp-content/plugins/yawave/yawave.php+59
Trying to access array offset on value of type bool
Server metrics [RAM: ▼1.96MB] [CPU: ▼65.63ms] Passed 4 tests
Analyzing server-side resources used by Yawave
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.03 ▼1.44 | 7.78 ▼36.98 |
| Dashboard /wp-admin | 2.05 ▼1.26 | 7.57 ▼45.49 |
| Posts /wp-admin/edit.php | 2.05 ▼1.31 | 6.37 ▼65.69 |
| Add New Post /wp-admin/post-new.php | 2.05 ▼3.84 | 6.64 ▼114.36 |
| Media Library /wp-admin/upload.php | 2.05 ▼1.18 | 6.10 ▼29.85 |
| Categories /wp-admin/edit-tags.php?taxonomy=category&post_type=publication | 2.05 | 6.69 |
| Settings /wp-admin/admin.php?page=yawave-setting-admin | 2.05 | 7.41 |
| Add New /wp-admin/post-new.php?post_type=publication | 2.05 | 5.70 |
| All Items /wp-admin/edit.php?post_type=publication | 2.05 | 6.44 |
| Types /wp-admin/edit-tags.php?taxonomy=media_type&post_type=publication | 2.05 | 7.87 |
| Portals /wp-admin/edit-tags.php?taxonomy=portal&post_type=publication | 2.05 | 5.92 |
| Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=publication | 2.05 | 6.60 |
| Liveblogs /wp-admin/admin.php?page=yawave-setting-admin-liveblog | 2.05 | 8.43 |
Server storage [IO: ▲1.13MB] [DB: ▲0.01MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 59 new files
Database: 3 new tables, 8 new options
| New tables |
|---|
| wp_yawave_liveblogs |
| wp_yawave_log |
| wp_yawave_liveblogs_posts |
| New WordPress options |
|---|
| widget_recent-posts |
| widget_theysaidso_widget |
| category_children |
| yawave_db_version |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Yawave: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,474 ▲713 | 25.90 ▲11.53 | 43.74 ▲41.88 | 37.83 ▼4.90 |
| Dashboard /wp-admin | 2,527 ▲350 | 11.63 ▲6.10 | 121.72 ▲16.63 | 45.59 ▼2.38 |
| Posts /wp-admin/edit.php | 2,641 ▲538 | 14.45 ▲12.44 | 223.63 ▲178.49 | 35.11 ▼4.33 |
| Add New Post /wp-admin/post-new.php | 6,251 ▲4,716 | 18.95 ▲0.54 | 824.05 ▲203.38 | 39.66 ▼27.13 |
| Media Library /wp-admin/upload.php | 1,883 ▲480 | 10.95 ▲6.77 | 142.63 ▲34.36 | 53.16 ▲7.16 |
| Categories /wp-admin/edit-tags.php?taxonomy=category&post_type=publication | 1,790 | 10.11 | 72.54 | 36.15 |
| Settings /wp-admin/admin.php?page=yawave-setting-admin | 1,192 | 10.02 | 73.88 | 30.44 |
| Add New /wp-admin/post-new.php?post_type=publication | 6,239 | 22.11 | 722.52 | 35.04 |
| All Items /wp-admin/edit.php?post_type=publication | 1,306 | 21.10 | 246.67 | 29.79 |
| Types /wp-admin/edit-tags.php?taxonomy=media_type&post_type=publication | 1,596 | 10.13 | 71.60 | 35.01 |
| Portals /wp-admin/edit-tags.php?taxonomy=portal&post_type=publication | 1,601 | 10.16 | 74.25 | 34.66 |
| Tags /wp-admin/edit-tags.php?taxonomy=post_tag&post_type=publication | 1,652 | 10.24 | 91.77 | 49.40 |
| Liveblogs /wp-admin/admin.php?page=yawave-setting-admin-liveblog | 1,316 | 10.06 | 68.79 | 31.11 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 25% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > Notice in wp-content/plugins/yawave/yawave.php+59
Trying to access array offset on value of type bool
- This plugin does not fully uninstall, leaving 3 tables in the database
- wp_yawave_log
- wp_yawave_liveblogs_posts
- wp_yawave_liveblogs
- The uninstall procedure has failed, leaving 8 options in the database
- can_compress_scripts
- widget_recent-posts
- yawave_db_version
- category_children
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Almost there, just fix the following server-side errors
- 35 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > Notice in wp-content/plugins/yawave/yawave.php+63
Trying to access array offset on value of type bool
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-wp-sdk-script handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-livelog-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-liveblog-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-focuspoint-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-focuspoint-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-app-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-wp-sdk-script handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-liveblog-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-livelog-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-focuspoint-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-focuspoint-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-app-js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-liveblog-block handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-liveblog-block-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-publications-block handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 17 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the yawave-publications-block-css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- 8 occurences, only the last one shown
- > GET request to /wp-admin/post-new.php?post_type=publication
- > User notice in wp-includes/functions.php+5905
Function is_feed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.)
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
Almost there! Just fix the following items
- 10× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/yawave/includes/shortcode.liveblog.php:66
- > PHP Fatal error
Uncaught Error: Class 'Yawave\\WP_Async_Request' not found in wp-content/plugins/yawave/includes/class-importer-request.php:4
- > PHP Fatal error
Trait 'Yawave\\WP_Yawave_Importer' not found in wp-content/plugins/yawave/includes/class-importer-process.php on line 4
- > PHP Fatal error
Uncaught Error: Class 'Yawave\\WP_Async_Request' not found in wp-content/plugins/yawave/includes/wp-background-process.php:17
- > PHP Notice
Undefined variable: wpdb in wp-content/plugins/yawave/includes/settings.liveblogs.details.php on line 20
- > PHP Fatal error
Uncaught Error: Call to a member function get_row() on null in wp-content/plugins/yawave/includes/settings.liveblogs.details.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function Yawave\\is_admin() in wp-content/plugins/yawave/includes/settings.php:676
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/yawave/includes/settings.liveblogs.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/yawave/includes/shortcodes.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function Yawave\\add_action() in wp-content/plugins/yawave/includes/metadata.php:26
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please take a look at the following user-side issues
- 7 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=yawave-setting-admin-liveblog
- > Javascript (severe) in unknown
/wp-content/plugins/yawave/assets/js/yawave.sdk.js?ver=1.0 0:187 Uncaught ReferenceError: yawavesdkobject is not defined
- > GET request to /wp-admin/edit.php?post_type=publication
- > Console-api (severe) in unknown
https://s3.eu-central-1.amazonaws.com/yawave-analytics.master.yawave/bundle.js 0:10409 "[Storage] rl_user_id should be string"
- > GET request to /wp-admin/edit.php?post_type=publication
- > Network (severe)
https://api.yawave.com/core/yawave-tenant/open/sdk/track?ssoBaseUrl=https%3A%2F%2Fsso.yawave.com%2Fauth&realm=&lang=de&appId=null&referrer=http%3A%2F%2Fwp.com%2Fwp-admin%2Fedit.php%3Fpost_type%3Dpublication&post_type=publication&cookiesDeny=no - Failed to load resource: the server responded with a status of 400 (Bad Request)
- > GET request to /wp-admin/edit.php?post_type=publication
- > Console-api (severe) in unknown
https://s3.eu-central-1.amazonaws.com/yawave-sdk.master.yawave/static/js/main.6e37d168.chunk.js 0:44829 "YawaveSDK: You do not have sufficient permissions to perform this action."
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: yawave, publizieren, analysieren, kommunikation, content marketing...
yawave/yawave.php 92% from 13 tests
The principal PHP file in "Yawave" v. 2.5.6 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
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 plugin4,289 lines of code in 50 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 18 | 1,363 | 758 | 3,271 |
| CSS | 4 | 55 | 3 | 338 |
| JavaScript | 6 | 55 | 11 | 277 |
| PO File | 1 | 91 | 93 | 274 |
| SVG | 20 | 1 | 0 | 73 |
| SQL | 1 | 3 | 0 | 56 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.48 |
| Average class complexity | 28.53 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 89.00 |
| Average method complexity | 4.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 89.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 6 | |
| Classes | 9 | |
| ▷ Abstract classes | 2 | 22.22% |
| ▷ Concrete classes | 7 | 77.78% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 132 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 109 | 82.58% |
| ▷ Protected methods | 22 | 16.67% |
| ▷ Private methods | 1 | 0.76% |
| Functions | 37 | |
| ▷ Named functions | 27 | 72.97% |
| ▷ Anonymous functions | 10 | 27.03% |
| Constants | 21 | |
| ▷ Global constants | 21 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
7 PNG files occupy 0.88MB with 0.30MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/yawave_logo.png | 2.87KB | 2.11KB | ▼ 26.29% |
| assets/screenshot-3.png | 136.25KB | 35.49KB | ▼ 73.96% |
| assets/img/liveblog/icons/yellow_card-hand.png | 0.97KB | 0.59KB | ▼ 39.18% |
| assets/img/liveblog/icons/ball-icon.png | 0.68KB | 0.46KB | ▼ 32.66% |
| assets/img/menue-icon.png | 0.36KB | 0.54KB | 0.00% |