Scanned sites / www.wowwinnipeg.com / 2026-10-01-0932

www.wowwinnipeg.com scan from 10/1/2026, 9:32:19 AM

A newer scan exists. See the latest report for www.wowwinnipeg.com.

Scan 2026-10-01-0932

Scanned 10/1/2026, 9:32:19 AM, finished 10/1/2026, 10:56:29 PM. Found on page 5 of brave web search results

Site: https://www.wowwinnipeg.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

73/ 100Needs work

On October 1, 2026 the Site Spider crawled 1006 pages and 1000 assets of www.wowwinnipeg.com, starting from https://www.wowwinnipeg.com/. It scored 73 out of 100, a result that needs work. 10 of 16 checks found something to fix, led by heavy assets (117), sitemap coverage (510), title tags (308); 4 checks passed. Most of the points went to heavy assets (−6), title tags (−5.5), sitemap coverage (−5.5). 2 checks found something the score does not count, listed as noted. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium3 medium and 3 low findings. See the security findings ↓

Pages crawled
1006
Assets fetched
1000
Status
Completed
Checks with issues
10 of 16
CoverageJob finished, partial coverage

2,006 of 2,006 discovered URLs were fetched, 8,442 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 6894 left unchecked.

  • Title tags308 issues
    308 of 510 pages have title issues. 49 noindex or canonicalized pages excluded.
    −5.5 points
  • Meta descriptions280 issues
    280 of 510 pages have meta description issues. 49 noindex or canonicalized pages excluded.
    −4 points
  • Headings7 issues
    7 of 510 pages have heading issues. 49 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites4 issues
    4 destinations answered with an error, 58 could not be determined (timeouts, rate limits or refusals), 6894 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.3 points
  • Redirects447 issues
    448 redirecting URLs, 0 of them chained.
    −3.2 points
  • Non-200 responses448 noted
    448 URLs did not return a 2xx response. 447 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability49 issues
    49 of 559 indexable pages have indexability warnings.
    −0.9 points
  • Image alt text1,039 issues
    1039 of 4766 image references have no alt attribute. 1319 use an empty alt (decorative), which is fine.
    −1.3 points
  • Heavy assets117 issues
    117 assets larger than 500 KB among 1000 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage510 issues
    1 sitemap listing 0 URLs: 510 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.5 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content59 issues
    59 of 510 pages have fewer than 200 words. 49 noindex or canonicalized pages excluded.
    −0.8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1645 sites, median 80%, average 79%

www.wowwinnipeg.com scores 73%, higher than 23% of the 1645 scanned sites. See the full ranking.

0511020%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 10 sites65%: 18 sites66%: 18 sites67%: 31 sites68%: 25 sites69%: 24 sites70%: 34 sites71%: 37 sites72%: 47 sites73%: 41 sites74%: 46 sites75%: 53 sites76%: 61 sites77%: 59 sites78%: 76 sites79%: 58 sites80%: 80 sites81%: 102 sites82%: 80 sites83%: 77 sites84%: 71 sites85%: 56 sites86%: 58 sites87%: 53 sites88%: 56 sites89%: 49 sites90%: 31 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 54 sites73% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

The site has critical issues with redirects, indexability, and missing meta descriptions that need immediate attention to improve SEO health. Addressing these will enhance visibility and user experience.

  1. 1

    Resolve Redirects

    Why: 448 URLs redirecting could degrade user experience and SEO.

    How: Update or remove outdated URLs to eliminate unnecessary redirects.

    Checks: redirects

  2. 2

    Fix Meta Descriptions

    Why: 280 pages lack optimized meta descriptions, impacting click-through rates.

    How: Write engaging meta descriptions for affected pages to improve visibility on search engines.

    Checks: meta-descriptions

  3. 3

    Improve Indexability

    Why: 49 pages have canonical issues pointing elsewhere, reducing search visibility.

    How: Adjust canonical tags to ensure they point to the correct versions of affected pages.

    Checks: indexability

  4. 4

    Add H1 Tags

    Why: 7 pages missing H1 tags may confuse search engines about page content.

    How: Add a clear and concise H1 tag to each affected page.

    Checks: headings

  5. 5

    Update Sitemap

    Why: 510 crawled pages missing from the sitemap can prevent proper indexing.

    How: Generate and submit a new sitemap to include all important URLs.

    Checks: sitemap-coverage

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website www.wowwinnipeg.com lacks critical security headers that can expose users to various vulnerabilities. Most notably, it does not implement HTTP Strict Transport Security, Content Security Policy, or protections against clickjacking. Implementing these headers is essential to enhance the security posture of the site and protect visitor information.

  • 0 high
  • 3 medium
  • 3 low
  • 0 info
  1. 1

    Lack of HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be intercepted on initial HTTP requests to the site.

    Fix: Add the following header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: The absence of a CSP allows scripts and resources to load from any source, increasing the risk of XSS attacks.

    Fix: Implement a Content Security Policy suitable for your site, for example: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Not using X-Frame-Options allows other sites to frame your content, which can lead to clickjacking attacks.

    Fix: Add the following header: X-Frame-Options: SAMEORIGIN

    Evidence: Clickjacking protection

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Absence of X-Content-Type-Options may allow browsers to misinterpret file types, increasing the risk of script execution.

    Fix: Add the following header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Not having a referrer policy exposes full URLs, compromising visitor privacy.

    Fix: Set the following header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Use of Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Running scripts from external domains without integrity checks poses a risk if those scripts are compromised.

    Fix: Incorporate Subresource Integrity for any external scripts or implement a robust Content Security Policy.

    Evidence: Third-party scripts

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.wowwinnipeg.com/ → no strict-transport-security
    • https://www.wowwinnipeg.com/news-and-events/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/construction/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/dining/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/education/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/healthcare/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/internet-tech/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/legal/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/maintenance/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/other-services/ → no strict-transport-security
    • https://www.wowwinnipeg.com/services/repairs/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 559 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://www.wowwinnipeg.com/ → no content-security-policy
    • https://www.wowwinnipeg.com/news-and-events/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/construction/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/dining/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/education/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/healthcare/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/internet-tech/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/legal/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/maintenance/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/other-services/ → no content-security-policy
    • https://www.wowwinnipeg.com/services/repairs/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://www.wowwinnipeg.com/ → no x-frame-options
    • https://www.wowwinnipeg.com/news-and-events/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/construction/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/dining/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/education/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/healthcare/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/internet-tech/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/legal/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/maintenance/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/other-services/ → no x-frame-options
    • https://www.wowwinnipeg.com/services/repairs/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://www.wowwinnipeg.com/ → no x-content-type-options
    • https://www.wowwinnipeg.com/news-and-events/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/construction/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/dining/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/education/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/healthcare/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/internet-tech/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/legal/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/maintenance/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/other-services/ → no x-content-type-options
    • https://www.wowwinnipeg.com/services/repairs/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://www.wowwinnipeg.com/ → no referrer-policy
    • https://www.wowwinnipeg.com/news-and-events/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/construction/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/dining/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/education/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/healthcare/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/internet-tech/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/legal/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/maintenance/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/other-services/ → no referrer-policy
    • https://www.wowwinnipeg.com/services/repairs/ → no referrer-policy
  • NoteThird-party scripts

    Scripts run from 3 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • www.googletagmanager.com (40 script tags)
    • www.instagram.com (70 script tags)
    • www.google.com (2 script tags)
9 checks passed, 1 not applicable
  • OKHTTPS

    All 559 crawled pages were served over HTTPS.

  • OKPermissions policy

    permissions-policy is set on all 559 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    43 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near www.wowwinnipeg.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling www.wowwinnipeg.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.wowwinnipeg.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.wowwinnipeg.com. Removal needs no account and no proof of purchase.
www.wowwinnipeg.com scan 2026-10-01-0932 | DIY SEO Hub