Scanned sites / www.dfslaw.ca / 2026-11-02-1412

www.dfslaw.ca scan from 2026-11-02 14:12:25 UTC DR 9

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-11-02-1412

Scanned 2026-11-02 14:12:25 UTC, finished 2026-11-02 14:41:56 UTC. Found on page 2 of brave web search results

Site: https://www.dfslaw.ca/

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

76/ 100Good

On November 2, 2026 the Site Spider crawled 41 pages and 67 assets of www.dfslaw.ca, starting from https://www.dfslaw.ca/. It scored 76 out of 100, a good result. 10 of 33 checks found something to fix, led by indexability (38), meta descriptions (38), title tags (5); 14 checks passed. Most of the points went to indexability (−10), meta descriptions (−8), title tags (−1.3). 9 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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: Medium5 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
41
Assets fetched
67
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

108 of 123 discovered URLs were fetched, 15 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 1 link destination on other sites was checked.

  • Title tags5 issues
    5 of 38 pages have title issues.
    −1.3 points
  • Meta descriptions38 issues
    38 of 38 pages have meta description issues.
    −8 points
  • Headings5 issues
    5 of 38 pages have heading issues.
    −0.8 points
  • Broken links2 issues
    2 internal links point at 2 broken URLs.
    −1.1 points
  • Links to other sitesOK
    0 destinations answered with an error, of 1 destination checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses3 issues
    4 URLs did not return a 2xx response. 3 of them are pages, 3 with an error status; the rest are assets or redirects.
    −0.8 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability38 issues
    38 of 38 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 135 image references have no alt attribute.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 67 fetched assets.
    −0.6 points
  • Orphan pages3 issues
    3 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage4 issues
    5 sitemaps listing 39 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 3 reachable only via the sitemap.
    −0.6 points
  • Internal link countsOK
    Internal link counts for 38 pages; none is a dead end or buried.
  • Thin content3 issues
    3 of 38 pages have fewer than 200 words.
    −0.6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format2 noted
    2 of 41 page URLs are harder to read, share or cache than they need to be.
  • CanonicalsOK
    0 of 38 pages have a canonical worth checking.
  • Robots directives37 noted
    37 pages carry a robots directive; 1 carries none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure33 noted
    33 of 38 pages could use the title, heading and snippet space better.
  • Image weight and alt length25 noted
    24 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 38 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    21 of 38 indexable pages carry structured data: WebSite (21), Corporation (21), Organization (18), Article (18), ImageObject (18). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 35 pages with enough text to compare.
  • Soft 404sOK
    None of 38 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions2 noted
    2 of 35 linked pages are linked only from the template, never from another page's content.
  • Pagination1 noted
    1 page in pagination sequences; 1 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 108 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 38 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling4 noted
    4 words an English dictionary does not know, on 3 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2607 sites, median 80%, average 78%

www.dfslaw.ca scores 76%, higher than 33% of the 2607 scanned sites. See the full ranking.

0601200%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 5 sites46%: 5 sites47%: 5 sites48%: 5 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 13 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 40 sites67%: 39 sites68%: 37 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 73 sites73%: 77 sites74%: 76 sites75%: 85 sites76%: 95 sites77%: 106 sites78%: 116 sites79%: 106 sites80%: 120 sites81%: 114 sites82%: 117 sites83%: 117 sites84%: 119 sites85%: 97 sites86%: 87 sites87%: 84 sites88%: 69 sites89%: 71 sites90%: 47 sites91%: 57 sites92%: 40 sites93%: 28 sites94%: 21 sites95%: 14 sites96%: 16 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 69 sites76% 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

Priority fixes needed for broken links, redirects, meta descriptions, and headings issues. Implementing these will enhance your site's SEO performance efficiently.

  1. 1

    Fix Broken Links

    Why: Improving user experience and preventing crawlers from encountering dead ends.

    How: Remove or replace links to https://www.dfslaw.ca/lawyers/randall-a-horton/ and https://www.dfslaw.ca/privacy-policy/[email protected].

    Checks: broken-links

  2. 2

    Resolve Redirect Issue

    Why: Redirects can dilute link equity and confuse users.

    How: Change the sitemap link from https://www.dfslaw.ca/sitemap.xml to https://www.dfslaw.ca/sitemap_index.xml.

    Checks: redirects

  3. 3

    Add Meta Descriptions

    Why: Essential for improving click-through rates and search engine visibility.

    How: Write and implement meta descriptions for all pages lacking them.

    Checks: meta-descriptions

  4. 4

    Fix Heading Issues

    Why: Proper headings enhance content structure and SEO.

    How: Add H1 tags to the four specified pages without them.

    Checks: headings

  5. 5

    Improve Indexability

    Why: Ensures pages are fully indexed, enhancing visibility.

    How: Add 'lang' attributes to the HTML of all pages.

    Checks: indexability

  6. 6

    Shrink Heavy Assets

    Why: Improving loading times and reducing bounce rates.

    How: Compress images larger than 500KB or consider offloading non-essential images.

    Checks: heavy-assets

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 issues, primarily related to missing security headers and the use of outdated libraries. These can expose users to potential attacks like clickjacking and cross-site scripting. Immediate fixes, such as implementing proper HTTP headers and updating libraries, are recommended to improve security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, initial connections can be hijacked.

    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 unrestricted resource loading, increasing XSS risk.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibraryMedium

    Why it matters: jQuery 1.9.1 has multiple known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Google API KeyMedium

    Why it matters: Public exposure of API keys increases risk of misuse.

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

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may misinterpret file types.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer PolicyLow

    Why it matters: No policy exposes sensitive URLs when navigating.

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

    Evidence: Referrer policy

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Lack of policy can lead to misuse of browser features.

    Fix: Add the header: Permissions-Policy: disable-accelerometer; disable-camera; disable-microphone

    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.dfslaw.ca/ → no strict-transport-security
    • https://www.dfslaw.ca/our-firm/ → no strict-transport-security
    • https://www.dfslaw.ca/our-lawyers/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/james-benson/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no strict-transport-security
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 38 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.dfslaw.ca/ → no content-security-policy
    • https://www.dfslaw.ca/our-firm/ → no content-security-policy
    • https://www.dfslaw.ca/our-lawyers/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/james-benson/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no content-security-policy
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → 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.dfslaw.ca/ → no x-frame-options
    • https://www.dfslaw.ca/our-firm/ → no x-frame-options
    • https://www.dfslaw.ca/our-lawyers/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/james-benson/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no x-frame-options
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → 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.dfslaw.ca/ → no x-content-type-options
    • https://www.dfslaw.ca/our-firm/ → no x-content-type-options
    • https://www.dfslaw.ca/our-lawyers/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/james-benson/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no x-content-type-options
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → 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.dfslaw.ca/ → no referrer-policy
    • https://www.dfslaw.ca/our-firm/ → no referrer-policy
    • https://www.dfslaw.ca/our-lawyers/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/james-benson/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no referrer-policy
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → 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.dfslaw.ca/ → no permissions-policy
    • https://www.dfslaw.ca/our-firm/ → no permissions-policy
    • https://www.dfslaw.ca/our-lawyers/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/brent-kaneski/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/john-m-reimer-epp/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/kerry-unruh/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/norman-r-piel/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/dana-r-kochan/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/erin-c-eisbrenner/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/james-benson/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/kevin-d-schur/ → no permissions-policy
    • https://www.dfslaw.ca/lawyers/jonathan-k-boettcher/ → 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.dfslaw.ca/wp-content/themes/DFSLawTheme/js/jquery-1.9.1.min.js: 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
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…tw (39 chars) in https://www.dfslaw.ca/: 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 2 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 (38 script tags)
    • maps.googleapis.com (38 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 3 paths that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin
    • Disallow: /wp-includes
    • Disallow: /wp-includes/js
4 checks passed, 2 not applicable
  • OKHTTPS

    All 38 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.

  • OKMixed content

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

  • OKExposed files and listings

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

  • Not applicableCookie flags

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

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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

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

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

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

Own www.dfslaw.ca?