Scanned sites / www.winnipegroofing.ca / 2026-10-03-0217

www.winnipegroofing.ca scan from 10/3/2026, 2:17:52 AM

Scan 2026-10-03-0217

Scanned 10/3/2026, 2:17:52 AM, finished 10/3/2026, 6:58:45 AM. Found on page 5 of brave web search results

Site: https://www.winnipegroofing.ca/

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

79/ 100Good

On October 3, 2026 the Site Spider crawled 286 pages and 983 assets of www.winnipegroofing.ca, starting from https://www.winnipegroofing.ca/. It scored 79 out of 100, a good result. 10 of 16 checks found something to fix, led by title tags (117), meta descriptions (132), thin content (127); 4 checks passed. Most of the points went to title tags (−4.1), meta descriptions (−3.7), thin content (−3.6). 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: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
286
Assets fetched
983
Status
Completed
Checks with issues
10 of 16
CoverageComplete crawl

1,269 of 1,270 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 50 link destinations on other sites were checked.

  • Title tags117 issues
    117 of 132 pages have title issues. 153 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions132 issues
    132 of 132 pages have meta description issues. 153 noindex or canonicalized pages excluded.
    −3.7 points
  • Headings117 issues
    117 of 132 pages have heading issues. 153 noindex or canonicalized pages excluded.
    −2.5 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites12 issues
    12 destinations answered with an error, 24 could not be determined (timeouts, rate limits or refusals), of 50 destinations checked.
    −1.7 points
  • Redirects8 issues
    144 redirecting URLs, 7 of them chained.
    −0.1 points
  • Non-200 responses153 noted
    153 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability32 issues
    32 of 164 indexable pages have indexability warnings. 121 pages noindex by design.
    −1.1 points
  • Image alt text7 issues
    7 of 920 image references have no alt attribute. 585 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 983 fetched assets.
  • Orphan pages122 issues
    122 pages have no internal links pointing at them.
    −1.7 points
  • Sitemap coverage122 issues
    8 sitemaps listing 164 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 122 reachable only via the sitemap.
    −2.6 points
  • Internal link countsOK
    Internal link counts for 285 pages.
  • Thin content127 issues
    127 of 132 pages have fewer than 200 words. 153 noindex or canonicalized pages excluded.
    −3.6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

2057 sites, median 80%, average 78%

www.winnipegroofing.ca scores 79%, higher than 46% of the 2057 scanned sites. See the full ranking.

0521040%: 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%: 2 sites37%: 2 sites38%: 3 sites39%: 1 site40%: 1 site41%: 2 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 5 sites48%: 2 sites49%: 4 sites50%: 4 sites51%: 4 sites52%: 8 sites53%: 6 sites54%: 8 sites55%: 7 sites56%: 5 sites57%: 7 sites58%: 15 sites59%: 6 sites60%: 11 sites61%: 13 sites62%: 16 sites63%: 20 sites64%: 18 sites65%: 31 sites66%: 23 sites67%: 41 sites68%: 34 sites69%: 26 sites70%: 42 sites71%: 51 sites72%: 64 sites73%: 55 sites74%: 56 sites75%: 75 sites76%: 84 sites77%: 76 sites78%: 95 sites79%: 82 sites80%: 104 sites81%: 102 sites82%: 104 sites83%: 87 sites84%: 86 sites85%: 74 sites86%: 74 sites87%: 68 sites88%: 66 sites89%: 51 sites90%: 37 sites91%: 43 sites92%: 27 sites93%: 18 sites94%: 16 sites95%: 7 sites96%: 7 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 sites79% 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

Your site is generally healthy, but there are several important SEO issues to address, especially with titles, meta descriptions, and headings. Implement these changes to enhance visibility.

  1. 1

    Fix Redirects

    Why: 144 URLs are redirecting, which slows down site performance and could impact SEO.

    How: Review and update the URLs to avoid unnecessary redirects, particularly the 7 chains.

    Checks: redirects

  2. 2

    Create Meta Descriptions

    Why: 132 pages lack meta descriptions, hindering search visibility.

    How: Write unique meta descriptions for the affected pages to enhance click-through rates.

    Checks: meta-descriptions

  3. 3

    Optimize Title Tags

    Why: 117 pages have title issues, which can negatively impact search rankings.

    How: Update titles to be unique and relevant to each page’s content.

    Checks: titles

  4. 4

    Address Heading Issues

    Why: Heading structure impacts SEO and user experience; 117 pages need optimization.

    How: Ensure there's one H1 per page and update headings appropriately.

    Checks: headings

  5. 5

    Eliminate Orphan Pages

    Why: 122 pages lack internal links, making them hard to discover.

    How: Add internal links from related content to these orphan pages.

    Checks: orphan-pages

  6. 6

    Improve Thin Content

    Why: 127 pages have under 200 words, which indicates low value to users.

    How: Revise content to ensure each page has sufficient quality information.

    Checks: thin-content

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

Your website has a few important security issues that need addressing. These include missing headers to limit browser features and improve cookie security. Additionally, there are insecure HTTP resource loads and a Google API key exposed in the code. Implementing these fixes will enhance your site's protection against potential attacks.

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

    Cookies Missing Protective FlagsMedium

    Why it matters: Cookies lack security attributes, risking their exposure to attacks such as XSS.

    Fix: Set the cookie 'wordpress_test_cookie' with flags: HttpOnly; Secure; SameSite=Strict.

    Evidence: Cookie flags

  2. 2

    Exposed Google API KeyMedium

    Why it matters: An exposed API key may allow unauthorized access to your Google services.

    Fix: Restrict the API key by setting HTTP referrer restrictions in the Google Cloud console.

    Evidence: Keys and secrets in page code

  3. 3

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can lead to security risks and user trust issues.

    Fix: Ensure all resources use HTTPS instead of HTTP.

    Evidence: Mixed content

  4. 4

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from external sources without integrity checks can be compromised.

    Fix: Consider adding a Content-Security-Policy to restrict script sources or, if possible, utilize Subresource Integrity.

    Evidence: Third-party scripts

  5. 5

    Missing Permissions Policy HeaderInfo

    Why it matters: Without a Permissions-Policy header, the site is vulnerable to unwanted use of browser features by injected scripts.

    Fix: Add the header: Permissions-Policy: interest-cohort=() to all pages.

    Evidence: Permissions policy

What the checks found

  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://www.winnipegroofing.ca/ → no permissions-policy
    • https://www.winnipegroofing.ca/about/ → no permissions-policy
    • https://www.winnipegroofing.ca/services/ → no permissions-policy
    • https://www.winnipegroofing.ca/recent-work/ → no permissions-policy
    • https://www.winnipegroofing.ca/blog/ → no permissions-policy
    • https://www.winnipegroofing.ca/contact/ → no permissions-policy
    • https://www.winnipegroofing.ca/kenora-roofing/ → no permissions-policy
    • https://www.winnipegroofing.ca/request-a-quote/ → no permissions-policy
    • https://www.winnipegroofing.ca/services/roofing/ → no permissions-policy
    • https://www.winnipegroofing.ca/services/fencing/ → no permissions-policy
    • https://www.winnipegroofing.ca/services/commercial-snow-plowing/ → no permissions-policy
    • https://www.winnipegroofing.ca/services/parking-lot-sanding/ → no permissions-policy
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://www.winnipegroofing.ca/wp-login.php?redirect_to=https%3A%2F%2Fwww.winni…) lacks SameSite
  • FoundMixed contentLow

    82 resources on HTTPS pages are loaded over plain HTTP.

    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/1-1.jpg
    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/2.jpg
    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/5.jpg
    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/6.jpg
    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/3.jpg
    • https://www.winnipegroofing.ca/services/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/4.jpg
    • https://www.winnipegroofing.ca/kenora-roofing/ loads image http://winnipegroofing.ca/wp-content/uploads/2018/02/9.jpg
    • https://www.winnipegroofing.ca/portfolio-item/sloping-flat-roofs/ loads image http://www.kenoraroofing.ca/wp-content/uploads/2018/01/2-7.jpg
    • https://www.winnipegroofing.ca/portfolio-item/sloping-flat-roofs/ loads image http://www.kenoraroofing.ca/wp-content/uploads/2018/01/3-7.jpg
    • https://www.winnipegroofing.ca/portfolio-item/sloping-flat-roofs/ loads image http://www.kenoraroofing.ca/wp-content/uploads/2018/01/4-5.jpg
    • https://www.winnipegroofing.ca/portfolio-item/sloping-flat-roofs/ loads image http://www.kenoraroofing.ca/wp-content/uploads/2018/01/5-5.jpg
    • https://www.winnipegroofing.ca/portfolio-item/sloping-flat-roofs/ loads image http://www.kenoraroofing.ca/wp-content/uploads/2018/01/6-4.jpg
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…Qo (39 chars) in https://www.winnipegroofing.ca/contact/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • 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.google.com (2 script tags)
    • maps.googleapis.com (2 script tags)
11 checks passed
  • OKHTTPS

    All 285 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 285 HTML pages.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

    x-frame-options is set on all 285 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 285 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 285 HTML pages.

  • OKSoftware version disclosure

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

  • 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.

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.winnipegroofing.ca

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.winnipegroofing.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.winnipegroofing.ca?

  • 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.winnipegroofing.ca. Removal needs no account and no proof of purchase.
www.winnipegroofing.ca scan 2026-10-03-0217 | DIY SEO Hub