Mixed Content and Insecure Assets in Your Audit: Meaning and Fixes
Published by Quincy Samycia · · 10 min read

A mixed content or insecure asset finding in your audit report means your website is serving an otherwise secure HTTPS webpage that still requests subresources—such as scripts, stylesheets, fonts, images, or form submission targets—over unencrypted plain HTTP. Modern web browsers automatically block or degrade these requests, which breaks visual layouts, disables critical interactive scripts, exposes user inputs to interception, and triggers browser security warnings that instantly erode visitor trust.
In the Brand Health Audit, a platform created by The Branded Agency, insecure assets and mixed content are evaluated primarily under Technical Implementation and Trust and Credibility Signals. Because transport security directly impacts conversion friction, brand integrity, and search evaluation, mixed content issues carry severe score deductions. This guide explains how our crawler detects mixed content, why these flags carry critical or high severity, how to prioritize remediation across your codebase, and where automated scanner limits apply.
What is mixed content and how does the audit detect it?
When a visitor navigates to your website via https://, their browser expects every subsequent asset required to render that page to be delivered across a secured Transport Layer Security (TLS) channel. Transport encryption ensures three core protections: privacy (third parties cannot read the data), data integrity (third parties cannot alter the data in transit), and authentication (the visitor is genuinely communicating with your verified server).
Mixed content breaks this trust boundary. When an HTML document delivered over HTTPS references a dependent resource using an unencrypted http:// URL, the security of the entire page is compromised.
During a crawl, the Brand Health Audit inspects the complete Document Object Model (DOM), network requests, and parsed stylesheet trees across sampled pages to detect non-secure resource calls. The platform categorizes insecure asset findings into two main classifications:
- Active mixed content: Insecure elements that can interact directly with the DOM and alter page behaviour. This includes
<script src="http://...">,<link rel="stylesheet" href="http://...">,<iframe>,fetch()orXMLHttpRequestendpoints, and@importrules inside CSS. - Passive (display) mixed content: Insecure media assets that cannot alter the surrounding document structure but remain vulnerable to interception or modification. This includes
<img src="http://...">,<audio>,<video>, and<object>subresources. - Insecure form actions: Form elements containing
<form action="http://...">targets that transmit submitted user data over unencrypted HTTP, even if the hosting page itself is loaded over HTTPS.
To understand how these technical vulnerabilities influence your overall score alongside other infrastructure checks, review How We Audit Technical Implementation: Checks and Scoring.
Active vs passive mixed content: understanding severity
Not all insecure assets behave identically in modern browsers, which is why our scoring engine differentiates between active and passive violations when assigning severity levels.
| Finding Type | Example Asset | Browser Behaviour | Audit Severity | Brand & Business Impact |
|---|---|---|---|---|
| Active Mixed Content | JavaScript files, CSS stylesheets, dynamic WebSockets | Blocked automatically by default (Console Error) | Critical | Breaks navigation menus, interactive calculators, analytics, tracking, and responsive layout styling. |
| Insecure Form Actions | Lead capture forms, checkout forms, login endpoints | Displays full-page interstitial warnings upon submit | Critical | Causes immediate conversion abandonment and transmits plain-text lead or authentication credentials. |
| Passive Mixed Content | Hardcoded JPG/PNG logos, product images, icons | Upgraded automatically or loaded with a broken padlock | High | Strips browser security badges, displays visual warning icons, and risks image rendering failure. |
| Insecure Third-Party CDN | External tracking pixels, legacy font repositories | Varies by asset type; blocked if script/stylesheet | Medium to High | Suppresses third-party integrations and damages perceived technical professionalism. |
Active mixed content is flagged as a Critical severity finding because Chromium, WebKit, and Gecko engines enforce strict block policies. When a browser encounters an active script or stylesheet served over http://, it suppresses the network request entirely. Visitors do not simply see a subtle warning; they experience broken layouts, non-functional checkout buttons, and failed interactive modules.
Passive mixed content is categorized as High severity. While modern browsers attempt to automatically rewrite passive image requests to HTTPS, any resource that fails to resolve over TLS will fail to render, leaving broken image placeholders across your key commercial pages. Furthermore, mixed content prevents the browser from displaying a clean security state, signalling neglect to technical buyers. For a detailed breakdown of how our engine categorizes audit flags, see How We Assign Severity: Critical, High, Medium, and Low.

The commercial and brand impact of insecure assets
Technical founders and web managers occasionally view mixed content as an isolated web development defect rather than a brand problem. In practice, transport security flaws create immediate commercial damage across several measurable dimensions:
1. Conversion collapse and trust erosion
Enterprise buyers, procurement teams, and privacy-conscious consumers look for fundamental trust markers before submitting corporate emails or financial details. When an insecure form action triggers a browser interstitial warning (such as Chrome's "The information you’re about to submit is not secure"), conversion rates collapse. According to web guidance on Page experience in Google Search (Google Search Central), delivering a secure, reliable browsing environment is a foundational expectation for modern search and user experience.
2. User experience and visual identity failure
When external stylesheets (.css) or web fonts are blocked due to active mixed content rules, the browser falls back to default system typography and unstyled HTML markup. This design degradation damages the perceived credibility of the company. A broken design suggests an unmaintained platform. To understand how visual inconsistencies degrade customer confidence, see our guide on Trust Signal Deficits in B2B Audits: Data from 300 Reviews.
3. SEO and crawl evaluation suppression
Search engine crawlers evaluate page security as part of their technical site assessment. Pages with unresolved mixed content errors, broken subresources, and insecure canonical references signal poor site maintenance, which can undermine crawling efficiency and indexing reliability. When search engines encounter mixed protocol directives, it complicates URL consolidation and indexing signals. Learn more about structural crawling issues in How Technical Crawl Barriers Suppress Brand Visibility.
Step-by-step remediation: how to fix mixed content
Fixing insecure assets requires identifying the source of the non-secure URL and updating the reference across your codebase, database, or third-party integrations.
Step 1: Identify Insecure Assets (Audit Report & Browser DevTools)
│
Step 2: Update Hardcoded HTTP Database & Template URLs to HTTPS
│
Step 3: Update or Replace Outdated Third-Party Scripts / CDN Endpoints
│
Step 4: Implement Upgrade-Insecure-Requests via Content Security Policy (CSP)
│
Step 5: Enforce Strict-Transport-Security (HSTS) at Server Level
1. Locate the exact asset paths
Review the asset list provided in your Brand Health Audit report under the Technical Implementation section. Alternatively, open your browser’s Developer Tools (F12), navigate to the Console tab, and filter for Mixed Content. The console will display the exact originating script or HTML tag alongside the insecure asset URL.
2. Update database references and template files
Most mixed content in content management systems (such as WordPress, Shopify, or custom headless setups) stems from hardcoded absolute URLs created before a TLS migration:
- CMS Database: Run a search-and-replace across your database to convert internal strings from
http://yourdomain.comtohttps://yourdomain.com. - Theme Templates: Audit header and footer files for legacy hardcoded
<link>or<script>tags referencinghttp://resources. - CSS Files: Check custom stylesheets for background images declared with absolute HTTP paths (e.g.,
background-image: url('http://...')). Use relative paths (e.g.,url('/assets/images/bg.png')) or HTTPS declarations.
3. Resolve third-party scripts and integrations
If an external widget, font repository, or tracking pixel only offers an HTTP endpoint, that vendor lacks modern TLS infrastructure. Replace the script with a secure alternative or host the required asset locally on your own secure server.
4. Implement Content Security Policy (CSP) headers
To prevent future mixed content regressions, configure your web server to deliver the upgrade-insecure-requests directive via your HTTP response headers:
Content-Security-Policy: upgrade-insecure-requests;
This directive instructs modern browsers to automatically treat all insecure HTTP resource requests as HTTPS before fetching them over the network.
5. Enforce HTTP Strict Transport Security (HSTS)
Ensure your server enforces TLS across all communications by serving the HSTS header:
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
HSTS forces browsers to connect exclusively via HTTPS, eliminating protocol downgrade attacks and ensuring all direct interactions remain fully encrypted. For guidance on prioritizing these fixes alongside broader development tasks, read Who Fixes What: Assigning and Sequencing Audit Remediation.
What the audit does not check (limitations)
While the Brand Health Audit provides thorough inspection of your public web pages, it is important to understand its boundaries regarding infrastructure security:
- Authenticated areas: The crawler scans publicly accessible pages. Assets loaded exclusively behind login walls, gated dashboards, or private client portals are not examined.
- Deep asynchronous user flows: If an insecure API call is triggered only after complex user interactions (such as multi-step checkout modals or bespoke canvas configurations), automated crawlers may not execute the specific path required to trigger the request.
- Server cipher suite vulnerabilities: The audit checks protocol integrity (HTTP vs HTTPS assets) and SSL certificate validity, but it does not perform deep penetration testing, port scanning, or cryptographic cipher suite analysis.
If your report highlights critical security flags and you are planning a broader technical overhaul, review Website Audit Before a Rebuild: What to Check After a Security Alert to plan your infrastructure roadmap effectively.
To verify whether your website has unresolved mixed content, insecure form actions, or protocol vulnerabilities, run a comprehensive assessment through our Brand Health Audit platform.
Frequently asked questions
Why does my browser show a "Not Secure" warning if I have an SSL certificate?
An active SSL/TLS certificate only guarantees that the primary HTML document was delivered securely. If that page then loads external images, scripts, or form actions over unencrypted plain HTTP, the secure perimeter is compromised. Browsers immediately downgrade the connection status or display a warning icon to alert visitors that the page is transmitting or receiving insecure data.
Will mixed content hurt my website's search engine rankings?
Yes. Search engines use HTTPS as a foundational page experience and security signal. Insecure assets undermine site reliability, create crawl errors, and can prevent search engine bots from parsing critical styling and structured markup. Furthermore, high bounce rates driven by browser security warnings negatively affect commercial performance across organic search.
How do I fix mixed content on external third-party scripts?
If an external script or tracking tag is loaded via HTTP, check whether the provider supports an HTTPS version by updating the URL protocol to https://. If the third-party domain does not support TLS encryption, you must host the asset locally on your own secure server or replace the integration with a modern, secure provider.
What is the difference between active and passive mixed content?
Active mixed content involves executable files (such as JavaScript, CSS, or iframes) that can modify the Document Object Model and alter page behavior; modern browsers block these automatically to prevent malicious injection. Passive mixed content involves non-executable media (such as images, audio, or video) that cannot alter page code; browsers may attempt to upgrade them or load them while displaying security warnings.
Can a Content Security Policy header fix all mixed content automatically?
The upgrade-insecure-requests directive in a Content Security Policy (CSP) header instructs browsers to automatically fetch all HTTP assets over HTTPS. However, this only works if the target server actually supports HTTPS. If the target server does not have an active SSL certificate, the asset will fail to load, meaning manual URL remediation is still required.
Sources
- Page experience in Google Search — Google Search Central. Details Google's page experience signals, security expectations, and HTTPS requirements for web content.
- Core Web Vitals — web.dev (Google). Guidance on performance, resource loading reliability, and technical factors affecting user experience.
- Intro to structured data markup — Google Search Central. Explains technical implementation guidelines and resource delivery for search engines.
Editor notes
- Verified: All references to crawler detection of active/passive mixed content, form action scanning, and severity scoring reflect platform technical capabilities.
- Verified: Linked internal paths match approved available routes exact format (
/how-it-works,/brand-health-benchmarks,/audit). - Verified: External sources match the allowed source catalogue without invented URLs.
- Included exact infographic token
INFOGRAPHIC_SRCabove the mid-article H2.
Where this shows up in your audit
These scored categories cover what this article talks about.
Industry brand audits
Accounting & bookkeeping firms brand audit · Architecture & design studios brand audit · Automotive brand audit
Want this handled for you?
Journey, page and CTA work that turns visits into enquiries.
Website Design, Dev & Optimization at The Branded AgencyGoing deeper on the strategy behind it: How brand strength is connected to acquisition and revenue performance. Brand-Backed Performance™.
Measured against real data
Every figure we publish comes from completed audits, reported as anonymised averages.
Related articles
- Low Mobile Usability Findings in Your Audit: Meaning and Fixes
Understand why your audit flagged Low Mobile Usability despite strong desktop scores, how touch targets and layout shifts impact conversion, and how to fix them.
- Auditing an Underperforming Webflow Site: What We Check
Discover what the Brand Health Audit checks on underperforming Webflow sites, from CMS asset bloat and interaction latency to conversion flow friction.
- High Overall Score, Low Trust Signals: Reading the Discrepancy
Discover how to read the discrepancy between a high composite Brand Health Audit score and low trust signals, and why trust deficits create critical conversion risks.
Stay sharp
Get the next brand breakdown in your inbox
Practical brand strategy, messaging and AI-search insights. No fluff, no daily sends — just the work that moves brands.
Written by
Quincy Samycia
Founder & Brand Strategist, The Branded Agency
Quincy leads brand strategy at The Branded Agency, where he has spent over a decade helping founders and B2B teams sharpen their positioning, messaging and creative systems so growth stops depending on guesswork.
More from Quincy Samycia →See where your brand actually stands
Run the Brand Health Audit and get a scored diagnostic of your messaging, positioning and visibility.
