Scanned sites / www.scase.ca / 2026-09-26-1708

www.scase.ca scan from 9/26/2026, 5:08:13 PM

Scan 2026-09-26-1708

Scanned 9/26/2026, 5:08:13 PM, finished 9/26/2026, 5:18:17 PM. 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 26, 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, 3 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

1289 sites, median 82%, average 80%

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

035700%: 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%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 4 sites51%: 4 sites52%: 4 sites53%: 5 sites54%: 4 sites55%: 2 sites56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 10 sites66%: 11 sites67%: 16 sites68%: 29 sites69%: 14 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 34 sites75%: 30 sites76%: 41 sites77%: 42 sites78%: 40 sites79%: 38 sites80%: 53 sites81%: 60 sites82%: 57 sites83%: 55 sites84%: 60 sites85%: 54 sites86%: 50 sites87%: 53 sites88%: 61 sites89%: 48 sites90%: 70 sites91%: 42 sites92%: 27 sites93%: 20 sites94%: 19 sites95%: 11 sites96%: 11 sites97%: 5 sites98%: 3 sites99%: 2 sites100%: 23 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 has several SEO issues that need addressing, particularly with title tags and meta descriptions. These fixes can significantly improve visibility and user engagement.

  1. 1

    Fix Title Tag Issues

    Why: 43 out of 46 pages have title issues affecting ranking.

    How: Shorten titles to fewer than 60 characters, ensuring they are concise and relevant.

    Checks: titles

  2. 2

    Add Missing Meta Descriptions

    Why: 39 out of 46 pages have meta description issues, impacting click-through rates.

    How: Create unique meta descriptions under 160 characters for all pages with missing descriptions.

    Checks: meta-descriptions

  3. 3

    Correct Heading Structure

    Why: 17 out of 46 pages have heading issues that can affect content clarity.

    How: Ensure each page has one H1 tag and use H2 tags appropriately for section headings.

    Checks: headings

  4. 4

    Optimize Heavy Assets

    Why: Large assets can slow page load times, affecting user experience and SEO.

    How: Compress images and scripts larger than 500 KB to improve performance.

    Checks: heavy-assets

  5. 5

    Update Sitemap Coverage

    Why: 45 pages are missing from the sitemap, affecting visibility in search engines.

    How: Add all crawled and indexable pages to the sitemap to ensure they are listed.

    Checks: sitemap-coverage

  6. 6

    Improve Thin Content

    Why: 7 pages contain fewer than 200 words, which can lower rankings.

    How: Add more relevant content to each page, ensuring they reach at least 200 words.

    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 lacks crucial security headers, making it vulnerable to various attacks, including clickjacking and XSS. Additionally, it uses an outdated JavaScript library that has known vulnerabilities. Implementing recommended headers and upgrading the library will significantly improve the security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users are at risk of man-in-the-middle attacks when accessing the site via HTTP.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: A lack of CSP allows any scripts and styles to load, increasing the risk of XSS attacks.

    Fix: Implement a Content Security Policy by adding 'Content-Security-Policy: default-src 'self';' to all responses.

    Evidence: Content Security Policy

  3. 3

    No Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Absence of this header permits iframe embedding, risking clickjacking attacks.

    Fix: Add 'X-Frame-Options: DENY' to all HTML page responses.

    Evidence: Clickjacking protection

  4. 4

    Use of Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 1.9.1 exposes the site to multiple known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers might execute files incorrectly, exposing users to content-type confusion attacks.

    Fix: Include 'X-Content-Type-Options: nosniff' in all HTML responses.

    Evidence: MIME sniffing protection

  6. 6

    No Referrer PolicyLow

    Why it matters: Without this policy, sensitive information in URLs may be leaked to third-party sites.

    Fix: Add 'Referrer-Policy: no-referrer' to all HTML responses.

    Evidence: Referrer policy

  7. 7

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Running scripts from other domains without integrity checks increases the risk of compromise.

    Fix: Implement Subresource Integrity (SRI) for third-party scripts where feasible.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: The absence of this header allows unauthorized access to browser features that aren't restricted.

    Fix: Include 'Permissions-Policy: interest-cohort=()' in all HTML responses.

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

Own www.scase.ca?

www.scase.ca scan 2026-09-26-1708 | DIY SEO Hub