Hi,
Thank you for providing the console screenshot and detailed explanation — that’s really helpful. Here’s what’s going on:
Mixed Content Warnings (Yellow Alerts)
These appear when your page is served over HTTPS, but a resource (like an image or script) is being requested via HTTP instead.
In your screenshot, the image from
http://wp-royal-themes.com/themes/ashe-pro/wp-content/uploads/2017/11/banner.jpg
is the cause.
This link is a demo placeholder image from our theme preview, not something you did wrong. When you imported demo content or used a starter layout, that demo image was included. You can safely remove or replace it with your own image.
Fix:
Go to your site’s media or customizer sections and replace any references to that banner with your own image uploaded over HTTPS.
After that, clear your cache — the mixed content warning will disappear.
Red 404 Errors (Favicon Requests)
These are requests from Google services like https://t0.gstatic.com/faviconV2, and they aren’t coming from the Ashe theme itself. They’re usually generated by browser extensions or third-party plugins trying to fetch favicons (the little tab icons).
Since the error references Google’s own gstatic.com domain, it’s not a theme issue and doesn’t affect your site’s performance or security.
Theme Code Status
The Ashe Pro theme itself does not generate these errors in a fresh install. The yellow warnings are purely due to demo image URLs, and the red ones are browser-side. There’s nothing in the Ashe theme code that’s broken or outdated in this case.
In short:
You did nothing wrong.
The warnings come from a demo image loaded over HTTP.
The errors come from browser requests, not the theme.
No update to Ashe is required for this — simply replacing demo assets will resolve the mixed-content messages.
Kind regards
.
