Scanned sites / www.litcolaw.com / 2026-11-02-0316
www.litcolaw.com scan from 2026-11-02 03:16:28 UTC DR 39
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-02-0316
Scanned 2026-11-02 03:16:28 UTC, finished 2026-11-02 05:13:20 UTC. Found on page 5 of brave web search results
Site: https://www.litcolaw.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On November 2, 2026 the Site Spider crawled 491 pages and 1000 assets of www.litcolaw.com, starting from https://www.litcolaw.com/. It scored 88 out of 100, a good result. 10 of 33 checks found something to fix, led by heavy assets (23), title tags (130), meta descriptions (116); 10 checks passed. Most of the points went to heavy assets (−6), title tags (−2.7), meta descriptions (−1.9). 13 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
- 491
- Assets fetched
- 1000
- Status
- Completed
- Checks with issues
- 10 of 33
1,491 of 1,491 discovered URLs were fetched, 35 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 220 left unchecked.
- Title tags130 issues130 of 474 pages have title issues. 11 noindex or canonicalized pages excluded.−2.7 points
- Meta descriptions116 issues116 of 474 pages have meta description issues. 11 noindex or canonicalized pages excluded.−1.9 points
- Headings1 issue1 of 474 pages have heading issues. 11 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites1 issue1 destination answered with an error, 117 could not be determined (timeouts, rate limits or refusals), 220 were left unchecked by the per-scan cap, of 300 destinations checked.−0.1 points
- Redirects4 issues6 redirecting URLs, 0 of them chained.
- Non-200 responses1 issue7 URLs did not return a 2xx response. 6 of them are pages, 1 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability11 issues11 of 485 indexable pages have indexability warnings.−0.2 points
- Image alt textOK0 of 5908 image references have no alt attribute. 15 use an empty alt (decorative), which is fine.
- Heavy assets23 issues23 assets larger than 500 KB among 1000 fetched assets.−6 points
- Orphan pages12 issues12 pages have no internal links pointing at them.−0.1 points
- Sitemap coverage47 issues10 sitemaps listing 441 URLs: 34 crawled pages missing, 1 listed URL broken or redirecting, 12 reachable only via the sitemap.−0.6 points
- Internal link counts415 notedInternal link counts for 485 pages; 415 worth a look.
- Thin contentOK0 of 474 pages have fewer than 200 words. 11 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format6 noted6 of 491 page URLs are harder to read, share or cache than they need to be.
- Canonicals11 noted11 of 485 pages have a canonical worth checking.
- Robots directives485 noted485 pages carry a robots directive; 0 carry none.
- Anchor text184 noted184 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure114 noted114 of 474 pages could use the title, heading and snippet space better. 11 noindex or canonicalized pages excluded.
- Image weight and alt length44 noted44 images over 100 KB; 0 with alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationOKAll 485 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured data108 noted485 of 474 indexable pages carry structured data: BreadcrumbList (485), ListItem (485), WebSite (485), Organization (485), WebPage (438). 108 pages with errors a rich result would fail on.
- Near duplicates5 noted5 pages in 2 groups read almost the same as another page (95% alike or more).
- Soft 404sOKNone of 485 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions38 noted38 of 462 linked pages are linked only from the template, never from another page's content.
- Pagination2 noted40 pages in pagination sequences; 2 with problems.
- Headers and cookies3 noted5 cookies set by the site, 3 missing a protective flag; 13 response headers recorded across 1491 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 485 pages; 148 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling81 noted81 words an English dictionary does not know, on 206 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2549 sites, median 80%, average 78%
www.litcolaw.com scores 88%, higher than 83% of the 2549 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 findingsThe website has some important areas for improvement, particularly with redirects, titles, and meta descriptions. Addressing these issues will enhance both user experience and SEO performance.
- 1
Fix Redirects
Why: There are broken redirects leading to 404 errors, which harm user experience and SEO.
How: Update the redirect rules or eliminate unnecessary redirects on the given URLs.
Checks: redirects
- 2
Correct Title Tags
Why: 130 pages have title issues, affecting click-through rates and ranking potential.
How: Revise titles to be unique and between 30-60 characters for optimal display in search results.
Checks: titles
- 3
Optimize Meta Descriptions
Why: 116 pages have meta description issues, which can lead to reduced visibility in search results.
How: Enhance descriptions to be engaging and between 50-160 characters, ensuring no duplicates.
Checks: meta-descriptions
- 4
Add Missing H1 Heading
Why: Having an H1 is essential for SEO and user clarity on pages.
How: Add a descriptive H1 heading to the page lacking one.
Checks: headings
- 5
Address Orphan Pages
Why: 12 pages have no internal links, making them less discoverable and reducing SEO value.
How: Link these pages internally from relevant existing pages to enhance visibility.
Checks: orphan-pages
- 6
Shrink Heavy Assets
Why: Heavy assets can slow page loads, negatively impacting user experience.
How: Compress or move these assets to enhance loading performance.
Evidence: 285 KB of script, loaded by 485 pages, so every visitor to any of them downloads it.
485 pages affected
Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.
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 important security issues that need to be addressed. Implementing security headers like HSTS and Content Security Policy will improve protection against attacks. Additionally, ensuring that cookies have proper safety flags set and updating vulnerable libraries are crucial steps to enhance overall security.
- 0 high
- 5 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors can be intercepted when they type the address without HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Lack of CSP allows scripts and styles to load from any source, increasing the risk of attacks.
Fix: Add the header: Content-Security-Policy: default-src 'self';.
Evidence: Content Security Policy
- 3
Missing Clickjacking Protection (X-Frame-Options)Medium
Why it matters: Without this protection, your site can be embedded in frames and overlaid with invisible controls.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 4
Missing Cookie Security FlagsMedium
Why it matters: Cookies lacking protective flags are vulnerable to security exploits.
Fix: Set HttpOnly, Secure, and SameSite attributes on the cookies.
Evidence: Cookie flags
- 5
Vulnerable JavaScript Library - jQueryMedium
Why it matters: Using jQuery 3.1.3 exposes the site to known vulnerabilities.
Fix: Upgrade jQuery to at least version 3.5.0.
Evidence: Vulnerable JavaScript libraries
- 6
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers may incorrectly interpret files based on their contents.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 7
Missing Referrer PolicyLow
Why it matters: No referrer policy means sensitive URL information is sent to other sites.
Fix: Add the header: Referrer-Policy: no-referrer.
Evidence: Referrer policy
- 8
Missing Permissions PolicyInfo
Why it matters: Lack of this header leaves browser features unrestricted on your site.
Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=().
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.litcolaw.com/ → no strict-transport-security
- https://www.litcolaw.com/about-us/ → no strict-transport-security
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no strict-transport-security
- https://www.litcolaw.com/about-us/our-team/ → no strict-transport-security
- https://www.litcolaw.com/about-us/client-testimonials/ → no strict-transport-security
- https://www.litcolaw.com/about-us/guiding-principles/ → no strict-transport-security
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no strict-transport-security
- https://www.litcolaw.com/litcocares/ → no strict-transport-security
- https://www.litcolaw.com/awards/ → no strict-transport-security
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no strict-transport-security
- https://www.litcolaw.com/news/ → no strict-transport-security
- https://www.litcolaw.com/calgary/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 485 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.litcolaw.com/ → no content-security-policy
- https://www.litcolaw.com/about-us/ → no content-security-policy
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no content-security-policy
- https://www.litcolaw.com/about-us/our-team/ → no content-security-policy
- https://www.litcolaw.com/about-us/client-testimonials/ → no content-security-policy
- https://www.litcolaw.com/about-us/guiding-principles/ → no content-security-policy
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no content-security-policy
- https://www.litcolaw.com/litcocares/ → no content-security-policy
- https://www.litcolaw.com/awards/ → no content-security-policy
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no content-security-policy
- https://www.litcolaw.com/news/ → no content-security-policy
- https://www.litcolaw.com/calgary/ → 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.litcolaw.com/ → no x-frame-options
- https://www.litcolaw.com/about-us/ → no x-frame-options
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no x-frame-options
- https://www.litcolaw.com/about-us/our-team/ → no x-frame-options
- https://www.litcolaw.com/about-us/client-testimonials/ → no x-frame-options
- https://www.litcolaw.com/about-us/guiding-principles/ → no x-frame-options
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no x-frame-options
- https://www.litcolaw.com/litcocares/ → no x-frame-options
- https://www.litcolaw.com/awards/ → no x-frame-options
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no x-frame-options
- https://www.litcolaw.com/news/ → no x-frame-options
- https://www.litcolaw.com/calgary/ → 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.litcolaw.com/ → no x-content-type-options
- https://www.litcolaw.com/about-us/ → no x-content-type-options
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no x-content-type-options
- https://www.litcolaw.com/about-us/our-team/ → no x-content-type-options
- https://www.litcolaw.com/about-us/client-testimonials/ → no x-content-type-options
- https://www.litcolaw.com/about-us/guiding-principles/ → no x-content-type-options
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no x-content-type-options
- https://www.litcolaw.com/litcocares/ → no x-content-type-options
- https://www.litcolaw.com/awards/ → no x-content-type-options
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no x-content-type-options
- https://www.litcolaw.com/news/ → no x-content-type-options
- https://www.litcolaw.com/calgary/ → 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.litcolaw.com/ → no referrer-policy
- https://www.litcolaw.com/about-us/ → no referrer-policy
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no referrer-policy
- https://www.litcolaw.com/about-us/our-team/ → no referrer-policy
- https://www.litcolaw.com/about-us/client-testimonials/ → no referrer-policy
- https://www.litcolaw.com/about-us/guiding-principles/ → no referrer-policy
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no referrer-policy
- https://www.litcolaw.com/litcocares/ → no referrer-policy
- https://www.litcolaw.com/awards/ → no referrer-policy
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no referrer-policy
- https://www.litcolaw.com/news/ → no referrer-policy
- https://www.litcolaw.com/calgary/ → 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.litcolaw.com/ → no permissions-policy
- https://www.litcolaw.com/about-us/ → no permissions-policy
- https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no permissions-policy
- https://www.litcolaw.com/about-us/our-team/ → no permissions-policy
- https://www.litcolaw.com/about-us/client-testimonials/ → no permissions-policy
- https://www.litcolaw.com/about-us/guiding-principles/ → no permissions-policy
- https://www.litcolaw.com/about-us/lawyers-youll-love/ → no permissions-policy
- https://www.litcolaw.com/litcocares/ → no permissions-policy
- https://www.litcolaw.com/awards/ → no permissions-policy
- https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no permissions-policy
- https://www.litcolaw.com/news/ → no permissions-policy
- https://www.litcolaw.com/calgary/ → no permissions-policy
- FoundCookie flagsMedium
4 of 6 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.
- SRsNAYkWrVjnLG (set by https://www.litcolaw.com/) lacks HttpOnly
- wBpZTG (set by https://www.litcolaw.com/) lacks HttpOnly
- nRhvtc-Yqo (set by https://www.litcolaw.com/) lacks HttpOnly
- 02 Nov 2026 05:31:43 GMT (set by https://www.litcolaw.com/news/behind-the-mask-with-todd-litwiniuk/) lacks Secure, HttpOnly, SameSite
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.1.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.1.3 in https://www.litcolaw.com/wp-content/plugins/gravityforms/js/placeholders.jquery…: 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 (1491 responses)
- x-powered-by: WP Engine (503 responses)
- NoteThird-party scripts
Scripts run from 1 other domain 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.)
- cdn.callrail.com (39 script tags)
6 checks passed
- OKHTTPS
All 485 crawled pages were served over HTTPS.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
63 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.litcolaw.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- baxtercreekvet.comDR 289/100 · rank 307 · 75 pages
- downtowndentalcentre.comDR 1789/100 · rank 307 · 197 pages
- ryanlenk.comDR 3089/100 · rank 307 · 48 pages
- wpganchor.caDR 188/100 · rank 378 · 1 page
- truecanadianelectric.caDR 388/100 · rank 378 · 3 pages
- barrllp.comDR 2088/100 · rank 378 · 109 pages
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.litcolaw.com from its pages as published, the way a search engine does. It shows summary figures only.
Own www.litcolaw.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.litcolaw.com. Removal needs no account and no proof of purchase.