Scanned sites / www.strategiccriminaldefence.com / 2026-10-05-0112

www.strategiccriminaldefence.com scan from 10/5/2026, 1:12:09 AM

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

Scan 2026-10-05-0112

Scanned 10/5/2026, 1:12:09 AM, finished 10/5/2026, 1:39:23 AM. Found with openstreetmap overpass

Site: https://www.strategiccriminaldefence.com/

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

79/ 100Good

On October 5, 2026 the Site Spider crawled 571 pages and 684 assets of www.strategiccriminaldefence.com, starting from https://www.strategiccriminaldefence.com/. It scored 79 out of 100, a good result. 11 of 22 checks found something to fix, led by title tags (275), heavy assets (36), meta descriptions (296); 3 checks passed. Most of the points went to title tags (−6.2), heavy assets (−6), meta descriptions (−5.3). 8 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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
571
Assets fetched
684
Status
Completed
Checks with issues
11 of 22
CoverageComplete crawl

1,255 of 1,255 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 1,085 link destinations on other sites have not been checked.

  • Title tags275 issues
    275 of 418 pages have title issues. 26 noindex or canonicalized pages excluded.
    −6.2 points
  • Meta descriptions296 issues
    296 of 418 pages have meta description issues. 26 noindex or canonicalized pages excluded.
    −5.3 points
  • Headings9 issues
    9 of 418 pages have heading issues. 26 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links5 issues
    5 internal links point at 5 broken URLs.
    −0.2 points
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects129 issues
    123 redirecting URLs, 8 of them chained.
    −1.2 points
  • Non-200 responses5 issues
    133 URLs did not return a 2xx response. 127 of them are pages, 5 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability22 issues
    22 of 444 indexable pages have indexability warnings.
    −0.5 points
  • Image alt textOK
    0 of 80 image references have no alt attribute. 35 use an empty alt (decorative), which is fine.
  • Heavy assets36 issues
    36 assets larger than 500 KB among 684 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages19 issues
    19 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage56 issues
    18 sitemaps listing 383 URLs: 36 crawled pages missing, 1 listed URL broken or redirecting, 19 reachable only via the sitemap.
    −0.8 points
  • Internal link counts108 noted
    Internal link counts for 444 pages; 108 worth a look.
  • Thin contentOK
    0 of 418 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.
  • Duplicate content5 issues
    1 group of pages with identical HTML.
    −0.1 points
  • URL format13 noted
    13 of 571 page URLs are harder to read, share or cache than they need to be.
  • Canonicals26 noted
    26 of 444 pages have a canonical worth checking.
  • Robots directives444 noted
    444 pages carry a robots directive; 0 carry none.
  • Anchor text35 noted
    35 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure106 noted
    106 of 418 pages could use the title, heading and snippet space better. 26 noindex or canonicalized pages excluded.
  • Image weight and alt length2 noted
    2 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.

Where this scan sits among all scanned sites

2072 sites, median 79%, average 78%

www.strategiccriminaldefence.com scores 79%, higher than 47% of the 2072 scanned sites. See the full ranking.

0521030%: 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%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 2 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 0 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 4 sites49%: 3 sites50%: 5 sites51%: 5 sites52%: 9 sites53%: 7 sites54%: 7 sites55%: 7 sites56%: 5 sites57%: 11 sites58%: 15 sites59%: 7 sites60%: 12 sites61%: 9 sites62%: 18 sites63%: 20 sites64%: 17 sites65%: 36 sites66%: 27 sites67%: 36 sites68%: 34 sites69%: 33 sites70%: 35 sites71%: 62 sites72%: 67 sites73%: 57 sites74%: 60 sites75%: 79 sites76%: 77 sites77%: 87 sites78%: 91 sites79%: 85 sites80%: 98 sites81%: 100 sites82%: 103 sites83%: 91 sites84%: 90 sites85%: 69 sites86%: 69 sites87%: 62 sites88%: 68 sites89%: 47 sites90%: 37 sites91%: 43 sites92%: 23 sites93%: 19 sites94%: 15 sites95%: 7 sites96%: 4 sites97%: 10 sites98%: 2 sites99%: 1 site100%: 57 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

The site has a good health score, but several critical issues need addressing for SEO improvements. Focus on fixing broken links, title tags, and meta descriptions for better search visibility.

  1. 1

    Fix Broken Links

    Why: Broken links negatively impact user experience and SEO.

    How: Update or remove the links from affected pages. Examples include the links on the pages for 'fine,' 'firearm offence,' etc.

    Checks: broken-links

  2. 2

    Address Title Tag Issues

    Why: Improper title tags hinder ranking potential and click-through rates.

    How: Rewrite titles for pages exceeding 60 characters, e.g., reduce length for URLs like 'https://www.strategiccriminaldefence.com/alberta-notice-of-administrative-penalty/'.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: Missing or duplicate meta descriptions can affect click-through rates.

    How: Create unique descriptions for pages with missing descriptions; prioritize the 245 pages identified.

    Checks: meta-descriptions

  4. 4

    Correct Redirects

    Why: Chained redirects can slow down page loading and dilute link equity.

    How: Reduce the number of hops by directly linking to the final URLs where possible, such as those for 'edmonton/assault/'.

    Checks: redirects

  5. 5

    Resolve Non-200 Responses

    Why: Non-200 responses can reduce indexability and frustrate users.

    How: Identify and fix or remove URLs returning error statuses or redirects. Ensure all accessible pages return a 2xx status.

    Checks: status-codes

  6. 6

    Handle Orphan Pages

    Why: Orphan pages lack internal linkage, reducing their visibility to search engines.

    How: Add links to orphan pages throughout the site where relevant, starting with high-importance pages.

    Checks: orphan-pages

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 lacks several important security headers and uses an outdated version of jQuery. Adding these headers enhances security against various threats. Updating libraries is important to mitigate potential vulnerabilities.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, connections initiated over HTTP can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows scripts, styles, and frames to load from any source.

    Fix: Add the header: Content-Security-Policy: default-src 'self';.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, your site is vulnerable to clickjacking attacks.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

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

    Fix: Upgrade jQuery to version 3.5.0 or newer.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This is essential to prevent browsers from interpreting files as scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without it, sensitive URLs may be sent to third-party sites.

    Fix: Add the header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header can limit unnecessary access to browser features.

    Fix: Add the header: Permissions-Policy: geolocation=(self).

    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.strategiccriminaldefence.com/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/reviews/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/our-firm/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/in-the-community/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/careers/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/lawyers/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/ian-savage/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no strict-transport-security
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 444 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.strategiccriminaldefence.com/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/reviews/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/our-firm/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/in-the-community/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/careers/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/lawyers/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/ian-savage/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no content-security-policy
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → 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.strategiccriminaldefence.com/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/reviews/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/our-firm/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/in-the-community/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/careers/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/lawyers/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/ian-savage/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no x-frame-options
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → 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.strategiccriminaldefence.com/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/reviews/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/our-firm/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/in-the-community/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/careers/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/lawyers/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/ian-savage/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no x-content-type-options
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → 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.strategiccriminaldefence.com/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/reviews/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/our-firm/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/in-the-community/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/careers/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/lawyers/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/ian-savage/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no referrer-policy
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → 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.strategiccriminaldefence.com/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/reviews/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/our-firm/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/in-the-community/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/careers/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/lawyers/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/michael-oykhman/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/ian-savage/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/joseph-beller/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/shaun-leochko/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/shervin-sabet/ → no permissions-policy
    • https://www.strategiccriminaldefence.com/cara-lebenzon/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.10.5 in https://www.strategiccriminaldefence.com/wp-content/plugins/gravityforms/js/pla…: 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
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (1255 responses)
    • x-powered-by: WP Engine (504 responses)
  • 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.)

    • analytics.ahrefs.com (40 script tags)
    • 471e3398d1e347219e0b7186b29f5cf2.js.ubembed.com (40 script tags)
    • www.google.com (39 script tags)
7 checks passed
  • OKHTTPS

    All 444 crawled pages were served over HTTPS.

  • 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

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

Own www.strategiccriminaldefence.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.strategiccriminaldefence.com. Removal needs no account and no proof of purchase.
www.strategiccriminaldefence.com scan 2026-10-05-0112 | DIY SEO Hub