Methodology: This check follows wSEO methodology 1.0. How the assessment works

Inspect actual browser requests

Find mixed content and preserve evidence

A lock icon alone is insufficient. Check Console and Network after a cache-free load, exercise interactive features and record the page, insecure URL and resource type.

DevTools shows an HTTP request inside an HTTPS page and a mixed-content warning
Useful evidence connects the exact page to a specific insecure request.

Simple browser check

  1. Open the exact HTTPS URL in a private window.
  2. Open DevTools → Console, enable Preserve log and reload without cache.
  3. Find Mixed Content messages and expand the resource URL.
  4. Filter Network for http:, then use menus, forms, video and other dynamic features.
  5. Save the page URL, message screenshot, resource URL and type.

How to classify the issue

Mixed-content severity
SituationLevelAction
No HTTP requests or warnings after all actionsNo issueSave tested URLs and date.
An optional image is automatically upgradedMinor, repairMake the safe source explicit.
A script, style, frame or API request is blockedCriticalRepair and test the feature.
HTTP appears only after a click or consentHidden issueTest the dynamic scenario.

Alternative check

curl -sS https://example.com/page \
  | rg -n 'http://|url\(["'"']?http:'

This sees source HTML only. It misses requests created by JavaScript, nested frames or loaded CSS, so the browser remains the primary evidence.

False positives and scope

http:// written in an article, comment or data attribute is not mixed content until the browser requests it. Extensions and proxies can also inject messages, so retest in a clean profile.

Any automated price applies only to the templates and scope on the service page. Follow the step-by-step guide for your own repair.