Scanned sites / sullivanlawoffice.ca / 2026-10-01-0422

sullivanlawoffice.ca scan from 10/1/2026, 4:22:22 AM

Scan 2026-10-01-0422

Scanned 10/1/2026, 4:22:22 AM, finished 10/1/2026, 4:57:26 AM. Found on page 4 of brave web search results

Site: https://sullivanlawoffice.ca/

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

72/ 100Needs work

On October 1, 2026 the Site Spider crawled 28 pages and 158 assets of sullivanlawoffice.ca, starting from https://sullivanlawoffice.ca/. It scored 72 out of 100, a result that needs work. 12 of 16 checks found something to fix, led by meta descriptions (25), title tags (15), indexability (8); 2 checks passed. Most of the points went to meta descriptions (−8), title tags (−6), indexability (−3.2). 2 checks 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: Medium4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
28
Assets fetched
158
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

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

  • Title tags15 issues
    15 of 25 pages have title issues.
    −6 points
  • Meta descriptions25 issues
    25 of 25 pages have meta description issues.
    −8 points
  • Headings6 issues
    6 of 25 pages have heading issues.
    −1.4 points
  • Broken links3 issues
    3 internal links point at 3 broken URLs.
    −2.4 points
  • Links to other sites2 issues
    2 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 9 destinations checked.
    −0.8 points
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses3 issues
    10 URLs did not return a 2xx response. 3 of them are pages, 3 with an error status; the rest are assets or redirects.
    −1.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability8 issues
    8 of 25 indexable pages have indexability warnings.
    −3.2 points
  • Image alt textOK
    0 of 213 image references have no alt attribute. 88 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 158 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −1.2 points
  • Orphan pages5 issues
    5 pages have no internal links pointing at them.
    −0.8 points
  • Sitemap coverage10 issues
    7 sitemaps listing 20 URLs: 5 crawled pages missing, 0 listed URLs broken or redirecting, 5 reachable only via the sitemap.
    −2.4 points
  • Internal link countsOK
    Internal link counts for 25 pages.
  • Thin content2 issues
    2 of 25 pages have fewer than 200 words.
    −0.6 points
  • Duplicate content3 issues
    1 group of pages with identical HTML.
    −1 points

Where this scan sits among all scanned sites

1754 sites, median 80%, average 79%

sullivanlawoffice.ca scores 72%, higher than 20% of the 1754 scanned sites. See the full ranking.

0511020%: 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%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 12 sites65%: 20 sites66%: 19 sites67%: 34 sites68%: 27 sites69%: 25 sites70%: 39 sites71%: 37 sites72%: 49 sites73%: 49 sites74%: 48 sites75%: 57 sites76%: 71 sites77%: 63 sites78%: 83 sites79%: 60 sites80%: 85 sites81%: 102 sites82%: 82 sites83%: 82 sites84%: 77 sites85%: 59 sites86%: 64 sites87%: 55 sites88%: 60 sites89%: 53 sites90%: 32 sites91%: 34 sites92%: 24 sites93%: 14 sites94%: 12 sites95%: 10 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites72% 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

Your website has several SEO issues that need addressing to improve its health score. Prioritize fixing broken links, meta descriptions, and title tags for better performance.

  1. 1

    Fix Broken Links

    Why: Broken links negatively affect user experience and SEO.

    How: Update or remove links pointing to broken pages.

    Checks: broken-links

  2. 2

    Create Meta Descriptions

    Why: All pages lack meta descriptions, affecting search visibility.

    How: Write compelling meta descriptions for all pages.

    Checks: meta-descriptions

  3. 3

    Update Title Tags

    Why: Many pages have title tag issues, impacting SEO rankings.

    How: Ensure all pages have unique, descriptive title tags.

    Checks: titles

  4. 4

    Resolve Non-200 Responses

    Why: Broken pages and assets affect user access and SEO.

    How: Fix URL issues for the pages returning 404 or error statuses.

    Checks: status-codes

  5. 5

    Fix Heading Issues

    Why: Improper heading structure impacts content hierarchy.

    How: Leave one H1 on pages with multiple H1s.

    Checks: headings

  6. 6

    Address Thin Content

    Why: Pages with low word counts may rank poorly.

    How: Expand content on pages with fewer than 200 words.

    Checks: thin-content

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 lacks essential security headers, exposing it to various risks such as interception, clickjacking, and script injection. Addressing these findings and upgrading the vulnerable library will significantly improve security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Visitors may be intercepted by attackers if they access the site without HTTPS.

    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: No restrictions on where scripts and styles can load from increases the risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in malicious sites and overlaid with controlled elements.

    Fix: Add the header: 'X-Frame-Options: DENY' or a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using jQuery 1.12.4 exposes the site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or higher.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Server Version DisclosureLow

    Why it matters: Reveals server details that may aid attackers in exploiting known vulnerabilities.

    Fix: Disable server version details to not reveal on responses.

    Evidence: Software version disclosure

  6. 6

    Use of Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Scripts from other domains can be altered, posing risks to site security.

    Fix: Implement a Content Security Policy that allows only trusted domains.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Lack of a permissions policy increases risk if a script is injected.

    Fix: Add the header: 'Permissions-Policy: not given'.

    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://sullivanlawoffice.ca/ → no strict-transport-security
    • https://sullivanlawoffice.ca/legal-services/ → no strict-transport-security
    • https://sullivanlawoffice.ca/practice/business-law/ → no strict-transport-security
    • https://sullivanlawoffice.ca/practice/real-estate/ → no strict-transport-security
    • https://sullivanlawoffice.ca/practice/wills-estates/ → no strict-transport-security
    • https://sullivanlawoffice.ca/practice/other-areas/ → no strict-transport-security
    • https://sullivanlawoffice.ca/about-us/ → no strict-transport-security
    • https://sullivanlawoffice.ca/john-sullivan/ → no strict-transport-security
    • https://sullivanlawoffice.ca/news-2/ → no strict-transport-security
    • https://sullivanlawoffice.ca/contact/ → no strict-transport-security
    • https://sullivanlawoffice.ca/66-st-annes-road/ → no strict-transport-security
    • https://sullivanlawoffice.ca/official-re-opening/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 25 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://sullivanlawoffice.ca/ → no content-security-policy
    • https://sullivanlawoffice.ca/legal-services/ → no content-security-policy
    • https://sullivanlawoffice.ca/practice/business-law/ → no content-security-policy
    • https://sullivanlawoffice.ca/practice/real-estate/ → no content-security-policy
    • https://sullivanlawoffice.ca/practice/wills-estates/ → no content-security-policy
    • https://sullivanlawoffice.ca/practice/other-areas/ → no content-security-policy
    • https://sullivanlawoffice.ca/about-us/ → no content-security-policy
    • https://sullivanlawoffice.ca/john-sullivan/ → no content-security-policy
    • https://sullivanlawoffice.ca/news-2/ → no content-security-policy
    • https://sullivanlawoffice.ca/contact/ → no content-security-policy
    • https://sullivanlawoffice.ca/66-st-annes-road/ → no content-security-policy
    • https://sullivanlawoffice.ca/official-re-opening/ → 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://sullivanlawoffice.ca/ → no x-frame-options
    • https://sullivanlawoffice.ca/legal-services/ → no x-frame-options
    • https://sullivanlawoffice.ca/practice/business-law/ → no x-frame-options
    • https://sullivanlawoffice.ca/practice/real-estate/ → no x-frame-options
    • https://sullivanlawoffice.ca/practice/wills-estates/ → no x-frame-options
    • https://sullivanlawoffice.ca/practice/other-areas/ → no x-frame-options
    • https://sullivanlawoffice.ca/about-us/ → no x-frame-options
    • https://sullivanlawoffice.ca/john-sullivan/ → no x-frame-options
    • https://sullivanlawoffice.ca/news-2/ → no x-frame-options
    • https://sullivanlawoffice.ca/contact/ → no x-frame-options
    • https://sullivanlawoffice.ca/66-st-annes-road/ → no x-frame-options
    • https://sullivanlawoffice.ca/official-re-opening/ → no x-frame-options
  • 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://sullivanlawoffice.ca/ → no permissions-policy
    • https://sullivanlawoffice.ca/legal-services/ → no permissions-policy
    • https://sullivanlawoffice.ca/practice/business-law/ → no permissions-policy
    • https://sullivanlawoffice.ca/practice/real-estate/ → no permissions-policy
    • https://sullivanlawoffice.ca/practice/wills-estates/ → no permissions-policy
    • https://sullivanlawoffice.ca/practice/other-areas/ → no permissions-policy
    • https://sullivanlawoffice.ca/about-us/ → no permissions-policy
    • https://sullivanlawoffice.ca/john-sullivan/ → no permissions-policy
    • https://sullivanlawoffice.ca/news-2/ → no permissions-policy
    • https://sullivanlawoffice.ca/contact/ → no permissions-policy
    • https://sullivanlawoffice.ca/66-st-annes-road/ → no permissions-policy
    • https://sullivanlawoffice.ca/official-re-opening/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Flywheel/5.1.0 (186 responses)
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.12.4 in https://sullivanlawoffice.ca/wp-content/plugins/enable-jquery-migrate-helper/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
  • 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.)

    • maps.google.com (25 script tags)
    • www.google.com (3 script tags)
8 checks passed, 1 not applicable
  • OKHTTPS

    All 25 crawled pages were served over HTTPS.

  • OKMIME sniffing protection

    x-content-type-options is set on all 25 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 25 HTML pages.

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

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

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

Own sullivanlawoffice.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 sullivanlawoffice.ca. Removal needs no account and no proof of purchase.
sullivanlawoffice.ca scan 2026-10-01-0422 | DIY SEO Hub