Real Accessability

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "my_plugin_load_plugin_textdomain".

The parameter "FALSE" at position #2 of load_plugin_textdomain() has been deprecated since WordPress version 2.7.0. Use "" instead.

load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$imgUserBlue'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'plugins_url'.

Scripts must be registered/enqueued via wp_enqueue_script()

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'str_replace'.

Plugin name header in your readme is missing or invalid. Please update your readme with a valid plugin name header. Eg: "=== Example Name ==="

Tested up to: 4.3 < 6.8. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

Mismatched Stable Tag: 1 != 1.0. Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.