Scanned sites / www.pringlelaw.ca / 2026-10-01-1711
www.pringlelaw.ca scan from 10/1/2026, 5:11:33 PM
A newer scan exists. See the latest report for www.pringlelaw.ca.
Scan 2026-10-01-1711
Scanned 10/1/2026, 5:11:33 PM, finished 10/1/2026, 5:50:45 PM. 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.
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 83 out of 100, a good result. 10 of 16 checks found something to fix, led by title tags (48), meta descriptions (40), links to other sites (7); 5 checks passed. Most of the points went to title tags (−6), meta descriptions (−4), links to other sites (−2.8). 1 check found something the score does not count, listed as noted. 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 16
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 issues48 of 80 pages have title issues.−6 points
- Meta descriptions40 issues40 of 80 pages have meta description issues.−4 points
- Headings17 issues17 of 80 pages have heading issues.−1.3 points
- Broken links1 issue1 internal link point at 1 broken URL.−0.3 points
- Links to other sites7 issues7 destinations answered with an error, 24 could not be determined (timeouts, rate limits or refusals), of 60 destinations checked.−2.8 points
- Redirects14 issues15 redirecting URLs, 0 of them chained.−0.7 points
- Non-200 responses19 issues34 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 limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 80 indexable pages have indexability warnings.
- Image alt textOK0 of 157 image references have no alt attribute. 109 use an empty alt (decorative), which is fine.
- Heavy assets2 issues2 assets larger than 500 KB among 29 fetched assets.−1.2 points
- Orphan pages1 issue1 page have no internal links pointing at them.−0.1 points
- Sitemap coverage19 issues7 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 countsOKInternal link counts for 80 pages.
- Thin contentOK0 of 80 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1645 sites, median 80%, average 79%
www.pringlelaw.ca scores 83%, higher than 63% of the 1645 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour 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
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
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
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
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
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
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 crawlYour 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
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
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
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
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
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
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
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
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.
- karmagroup.com64/100 · rank 1500 · 3,837 pages
- www.borealpeonies.com64/100 · rank 1500 · 12 pages
- slaaay.lol64/100 · rank 1500 · 40 pages
- www.delgadoaccounting.com63/100 · rank 1510 · 2 pages
- www.naturalenvironmentslandscaping.com63/100 · rank 1510 · 299 pages
- fossumelectric.com63/100 · rank 1510 · 59 pages
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.