Scanned sites / www.scase.ca / 2026-09-20-1125

www.scase.ca scan from 9/20/2026, 11:25:23 AM

Scan 2026-09-20-1125

Scanned 9/20/2026, 11:25:23 AM, finished 9/20/2026, 11:32:05 AM. Found with openstreetmap overpass

Site: https://www.scase.ca/

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

81/ 100Good

On September 20, 2026 the Site Spider crawled 66 pages and 103 assets of www.scase.ca, starting from https://www.scase.ca/. It scored 81 out of 100, a good result. 6 of 14 checks found something to fix, led by sitemap coverage (45), title tags (43), meta descriptions (39); 8 checks passed. 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: Medium4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
66
Assets fetched
103
Status
Completed
Checks with issues
6 of 14
  • Title tags43 issues
    43 of 46 pages have title issues. 20 noindex or canonicalized pages excluded.
  • Meta descriptions39 issues
    39 of 46 pages have meta description issues. 20 noindex or canonicalized pages excluded.
  • Headings17 issues
    17 of 46 pages have heading issues. 20 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    0 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 46 indexable pages have indexability warnings. 20 pages noindex by design.
  • Image alt textOK
    0 of 84 image references have no alt attribute. 18 use an empty alt (decorative), which is fine.
  • Heavy assets3 issues
    3 assets larger than 500 KB among the 100 heaviest.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage45 issues
    1 sitemap listing 1 URL: 45 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Thin content7 issues
    7 of 46 pages have fewer than 200 words. 20 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1121 sites, median 82%, average 80%

www.scase.ca scores 81%, higher than 44% of the 1121 scanned sites. See the full ranking.

029570%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 7 sites59%: 3 sites60%: 6 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 9 sites66%: 8 sites67%: 15 sites68%: 28 sites69%: 13 sites70%: 24 sites71%: 22 sites72%: 25 sites73%: 24 sites74%: 31 sites75%: 26 sites76%: 39 sites77%: 38 sites78%: 35 sites79%: 34 sites80%: 44 sites81%: 54 sites82%: 52 sites83%: 46 sites84%: 56 sites85%: 48 sites86%: 47 sites87%: 48 sites88%: 57 sites89%: 38 sites90%: 52 sites91%: 39 sites92%: 24 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 10 sites97%: 4 sites98%: 3 sites99%: 1 site100%: 12 sites81% 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's health is good, but there are some critical SEO issues to fix involving titles, meta descriptions, headings, and sitemap coverage. Addressing these will improve your site's search visibility.

  1. 1

    Fix Title Tag Issues

    Why: 43 of 46 pages have title issues; fixing these can improve SEO rankings.

    How: Shorten titles to under 60 characters. Edit in your CMS or HTML files.

    Checks: titles

  2. 2

    Create Missing Meta Descriptions

    Why: 39 of 46 pages have meta description problems; missing descriptions impact click-through rates.

    How: Add unique meta descriptions under 160 characters for all pages; edit in your CMS.

    Checks: meta-descriptions

  3. 3

    Resolve Heading Issues

    Why: 17 pages have heading problems, including multiple H1s or missing H1s, affecting content structure.

    How: Ensure only one H1 per page and create an H1 for missing headings; edit in your CMS.

    Checks: headings

  4. 4

    Address Heavy Assets

    Why: 3 assets over 500 KB can slow your site, affecting performance and user experience.

    How: Compress images and scripts using an online tool or plugin, or consider lazy loading.

    Checks: heavy-assets

  5. 5

    Update Sitemap Coverage

    Why: 45 pages are missing from the sitemap, reducing their visibility to search engines.

    How: Regenerate your sitemap to include all relevant pages and submit it to Google Search Console.

    Checks: sitemap-coverage

  6. 6

    Enhance Thin Content Pages

    Why: 7 pages have less than 200 words; adding content can improve relevance and rankings.

    How: Add informative content to those pages to exceed 200 words; consider blog posts or resources.

    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

The website has several security headers missing, which could expose it to various attacks. It is essential to implement proper security headers like HSTS, CSP, and frame options to enhance security. Additionally, the use of a vulnerable JavaScript library needs immediate attention.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted during their first request if they do not use HTTPS.

    Fix: Add the 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 any script or resource to load from any origin, increasing XSS risks.

    Fix: Add a CSP header: `Content-Security-Policy: default-src 'self';` with adjustments based on site requirements.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking attacks.

    Fix: Add the header: `X-Frame-Options: SAMEORIGIN`.

    Evidence: Clickjacking protection

  4. 4

    Use of Vulnerable jQuery VersionMedium

    Why it matters: jQuery 1.9.1 has known vulnerabilities that could potentially be exploited.

    Fix: Upgrade to jQuery version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers can execute files as scripts based on content type.

    Fix: Add the header: `X-Content-Type-Options: nosniff`.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-PolicyLow

    Why it matters: Without this policy, full URLs including sensitive information can be sent to third-party sites.

    Fix: Add the header: `Referrer-Policy: no-referrer` or another appropriate option.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: No Permissions-Policy restricts unused browser features, potentially exposing more attack vectors.

    Fix: Add the header: `Permissions-Policy: geolocation=(self), camera=()`, and customize as needed.

    Evidence: Permissions policy

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.scase.ca/ → no strict-transport-security
    • https://www.scase.ca/about/ → no strict-transport-security
    • https://www.scase.ca/about/karleen-scase/ → no strict-transport-security
    • https://www.scase.ca/about/darryl-scase/ → no strict-transport-security
    • https://www.scase.ca/services/ → no strict-transport-security
    • https://www.scase.ca/community/ → no strict-transport-security
    • https://www.scase.ca/links/ → no strict-transport-security
    • https://www.scase.ca/blog/ → no strict-transport-security
    • https://www.scase.ca/faq/ → no strict-transport-security
    • https://www.scase.ca/contact-us/ → no strict-transport-security
    • https://www.scase.ca/services/bookkeeping-service/ → no strict-transport-security
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 66 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.scase.ca/ → no content-security-policy
    • https://www.scase.ca/about/ → no content-security-policy
    • https://www.scase.ca/about/karleen-scase/ → no content-security-policy
    • https://www.scase.ca/about/darryl-scase/ → no content-security-policy
    • https://www.scase.ca/services/ → no content-security-policy
    • https://www.scase.ca/community/ → no content-security-policy
    • https://www.scase.ca/links/ → no content-security-policy
    • https://www.scase.ca/blog/ → no content-security-policy
    • https://www.scase.ca/faq/ → no content-security-policy
    • https://www.scase.ca/contact-us/ → no content-security-policy
    • https://www.scase.ca/services/bookkeeping-service/ → no content-security-policy
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → 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.scase.ca/ → no x-frame-options
    • https://www.scase.ca/about/ → no x-frame-options
    • https://www.scase.ca/about/karleen-scase/ → no x-frame-options
    • https://www.scase.ca/about/darryl-scase/ → no x-frame-options
    • https://www.scase.ca/services/ → no x-frame-options
    • https://www.scase.ca/community/ → no x-frame-options
    • https://www.scase.ca/links/ → no x-frame-options
    • https://www.scase.ca/blog/ → no x-frame-options
    • https://www.scase.ca/faq/ → no x-frame-options
    • https://www.scase.ca/contact-us/ → no x-frame-options
    • https://www.scase.ca/services/bookkeeping-service/ → no x-frame-options
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → 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.scase.ca/ → no x-content-type-options
    • https://www.scase.ca/about/ → no x-content-type-options
    • https://www.scase.ca/about/karleen-scase/ → no x-content-type-options
    • https://www.scase.ca/about/darryl-scase/ → no x-content-type-options
    • https://www.scase.ca/services/ → no x-content-type-options
    • https://www.scase.ca/community/ → no x-content-type-options
    • https://www.scase.ca/links/ → no x-content-type-options
    • https://www.scase.ca/blog/ → no x-content-type-options
    • https://www.scase.ca/faq/ → no x-content-type-options
    • https://www.scase.ca/contact-us/ → no x-content-type-options
    • https://www.scase.ca/services/bookkeeping-service/ → no x-content-type-options
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → 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.scase.ca/ → no referrer-policy
    • https://www.scase.ca/about/ → no referrer-policy
    • https://www.scase.ca/about/karleen-scase/ → no referrer-policy
    • https://www.scase.ca/about/darryl-scase/ → no referrer-policy
    • https://www.scase.ca/services/ → no referrer-policy
    • https://www.scase.ca/community/ → no referrer-policy
    • https://www.scase.ca/links/ → no referrer-policy
    • https://www.scase.ca/blog/ → no referrer-policy
    • https://www.scase.ca/faq/ → no referrer-policy
    • https://www.scase.ca/contact-us/ → no referrer-policy
    • https://www.scase.ca/services/bookkeeping-service/ → no referrer-policy
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → no referrer-policy
  • 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.scase.ca/ → no permissions-policy
    • https://www.scase.ca/about/ → no permissions-policy
    • https://www.scase.ca/about/karleen-scase/ → no permissions-policy
    • https://www.scase.ca/about/darryl-scase/ → no permissions-policy
    • https://www.scase.ca/services/ → no permissions-policy
    • https://www.scase.ca/community/ → no permissions-policy
    • https://www.scase.ca/links/ → no permissions-policy
    • https://www.scase.ca/blog/ → no permissions-policy
    • https://www.scase.ca/faq/ → no permissions-policy
    • https://www.scase.ca/contact-us/ → no permissions-policy
    • https://www.scase.ca/services/bookkeeping-service/ → no permissions-policy
    • https://www.scase.ca/services/corporate-accounting-and-tax/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 1.9.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://www.scase.ca/wp-content/themes/di-multipurpose/assets/js/bootstrap.min.…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • 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 (80 script tags)
    • pagead2.googlesyndication.com (40 script tags)
    • cdn.trustedsite.com (40 script tags)
8 checks passed
  • OKHTTPS

    All 66 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

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

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

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.scase.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.scase.ca from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

www.scase.ca scan 2026-09-20-1125 | DIY SEO Hub