Scanned sites / www.pringlelaw.ca / 2026-10-01-1711

www.pringlelaw.ca scan from 2026-10-01 17:11:33 UTC DR 18

A newer scan exists. See the latest report for www.pringlelaw.ca.

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

Scan 2026-10-01-1711

Scanned 2026-10-01 17:11:33 UTC, finished 2026-10-01 17:50:45 UTC. Found on page 4 of brave web search results

Site: https://www.pringlelaw.ca/

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

81/ 100Good

On October 1, 2026 the Site Spider crawled 113 pages and 29 assets of www.pringlelaw.ca, starting from https://www.pringlelaw.ca/. It scored 81 out of 100, a good result. 10 of 27 checks found something to fix, led by title tags (48), meta descriptions (40), non-200 responses (19); 12 checks passed. Most of the points went to title tags (−6), meta descriptions (−4), non-200 responses (−2.4). 5 checks found something the score does not count, listed as noted. 10 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
113
Assets fetched
29
Status
Completed
Checks with issues
10 of 27
CoverageComplete crawl

142 of 142 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 60 link destinations on other sites were checked.

  • Title tags48 issues
    48 of 80 pages have title issues.
    −6 points
  • Meta descriptions40 issues
    40 of 80 pages have meta description issues.
    −4 points
  • Headings17 issues
    17 of 80 pages have heading issues.
    −1.3 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.3 points
  • Links to other sites3 issues
    3 destinations answered with an error, 24 could not be determined (timeouts, rate limits or refusals), of 60 destinations checked.
    −1.2 points
  • Redirects14 issues
    15 redirecting URLs, 0 of them chained.
    −0.7 points
  • Non-200 responses19 issues
    34 URLs did not return a 2xx response. 33 of them are pages, 19 with an error status; the rest are assets or redirects.
    −2.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 80 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 157 image references have no alt attribute. 109 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 29 fetched assets.
    −1.2 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage19 issues
    7 sitemaps listing 98 URLs: 0 crawled pages missing, 18 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −1.4 points
  • Internal link countsOK
    Internal link counts for 80 pages; none is a dead end or buried.
  • Thin contentOK
    0 of 80 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 113 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 80 pages have a canonical worth checking.
  • Robots directives80 noted
    80 pages carry a robots directive; 0 carry none.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure7 noted
    7 of 80 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomalies5 noted
    5 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 80 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 142 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 80 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 Insights5 noted
    Mobile performance 50 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2909 sites, median 80%, average 79%

www.pringlelaw.ca scores 81%, higher than 52% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 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

Written from an earlier version of the analysis (rules v4). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your website has a few key areas needing improvement, mainly involving broken links, redirects, and meta tags. Addressing these will enhance user experience and SEO effectiveness.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Update the link to point to a valid page or remove it.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 34 URLs returned errors impacting site accessibility.

    How: Fix errors or ensure all assets and pages return a valid 2xx status.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 48 pages have title issues, risking click-through rates.

    How: Create unique, concise titles that capture page content.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 40 pages have issues, limiting search visibility.

    How: Write accurate, engaging descriptions for the pages without them.

    Checks: meta-descriptions

  5. 5

    Standardize Headings

    Why: 17 pages have heading issues, reducing content clarity.

    How: Ensure each page has one H1 and relevant H2s for better structure.

    Checks: headings

  6. 6

    Shrink Heavy Assets

    Why: Large asset sizes can slow page load times.

    How: Optimize images and files to reduce size for better loading speeds.

    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

Your website has several security headers missing, increasing the risk of interception and attacks. Prioritize implementing HTTP Strict Transport Security, a Content Security Policy, and protections against clickjacking, among others, to enhance your site's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted when they use HTTP instead of HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, there are no restrictions on where scripts and resources can load from, increasing XSS risks.

    Fix: Add a CSP header such as 'Content-Security-Policy: default-src 'self';' to all HTML pages.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header allows clickjacking attacks by embedding pages in frames.

    Fix: Add 'X-Frame-Options: DENY' or use a CSP directive 'frame-ancestors' to mitigate this risk.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

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

    Fix: Add 'X-Content-Type-Options: nosniff' to improve MIME type security.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: A missing Referrer-Policy can leak sensitive URL information to third-party sites.

    Fix: Add 'Referrer-Policy: no-referrer-when-downgrade' to restrict referrer information.

    Evidence: Referrer policy

  6. 6

    Server Banner DisclosuresLow

    Why it matters: Exposing server details can aid attackers in targeting vulnerabilities.

    Fix: Consider removing or obscuring the 'X-Powered-By' header.

    Evidence: Software version disclosure

  7. 7

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Scripts from external sources can be compromised, affecting your site's integrity.

    Fix: Implement a CSP that controls which third-party scripts can run and consider using Subresource Integrity (SRI) where possible.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: This header limits browser features, reducing potential risks from injected scripts.

    Fix: Add 'Permissions-Policy: geolocation=(self), microphone=()' to control feature access.

    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.pringlelaw.ca/ → no strict-transport-security
    • https://www.pringlelaw.ca/our-lawyers/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 80 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.pringlelaw.ca/ → no content-security-policy
    • https://www.pringlelaw.ca/our-lawyers/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → 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.pringlelaw.ca/ → no x-frame-options
    • https://www.pringlelaw.ca/our-lawyers/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → 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.pringlelaw.ca/ → no x-content-type-options
    • https://www.pringlelaw.ca/our-lawyers/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → 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.pringlelaw.ca/ → no referrer-policy
    • https://www.pringlelaw.ca/our-lawyers/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → 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.pringlelaw.ca/ → no permissions-policy
    • https://www.pringlelaw.ca/our-lawyers/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → no permissions-policy
  • NoteSoftware version disclosure

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

    • server: nginx (142 responses)
    • x-powered-by: WP Engine (121 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.)

    • www.googletagmanager.com (36 script tags)
    • pcst.wpenginepowered.com (629 script tags)
    • www.google.com (36 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 80 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

  • Not applicableCookie flags

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

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

Own www.pringlelaw.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.pringlelaw.ca. Removal needs no account and no proof of purchase.