Scanned sites / lypkielaw.com / 2026-10-02-0346

lypkielaw.com scan from 2026-10-02 03:46:53 UTC DR 21

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

Scan 2026-10-02-0346

Scanned 2026-10-02 03:46:53 UTC, finished 2026-10-02 04:57:27 UTC. Found on page 3 of brave web search results

Site: https://lypkielaw.com/

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

89/ 100Good

On October 2, 2026 the Site Spider crawled 151 pages and 119 assets of lypkielaw.com, starting from https://lypkielaw.com/. It scored 89 out of 100, a good result. 10 of 27 checks found something to fix, led by meta descriptions (51), headings (63), heavy assets (2); 8 checks passed. Most of the points went to meta descriptions (−3.1), headings (−2.9), heavy assets (−1.2). 9 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, 3 low and 2 info findings. See the security findings ↓

Pages crawled
151
Assets fetched
119
Status
Completed
Checks with issues
10 of 27
CoverageComplete crawl

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

  • Title tags7 issues
    7 of 123 pages have title issues. 8 noindex or canonicalized pages excluded.
    −0.5 points
  • Meta descriptions51 issues
    51 of 123 pages have meta description issues. 8 noindex or canonicalized pages excluded.
    −3.1 points
  • Headings63 issues
    63 of 123 pages have heading issues. 8 noindex or canonicalized pages excluded.
    −2.9 points
  • Broken links4 issues
    4 internal links point at 4 broken URLs.
    −0.6 points
  • Links to other sites12 noted
    0 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 36 destinations checked.
  • Redirects16 issues
    17 redirecting URLs, 0 of them chained.
    −0.5 points
  • Non-200 responses4 issues
    21 URLs did not return a 2xx response. 20 of them are pages, 4 with an error status; the rest are assets or redirects.
    −0.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability8 issues
    8 of 131 indexable pages have indexability warnings.
    −0.6 points
  • Image alt textOK
    0 of 102 image references have no alt attribute. 95 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 119 fetched assets.
    −1.2 points
  • Orphan pages16 issues
    16 pages have no internal links pointing at them.
    −0.5 points
  • Sitemap coverage15 issues
    4 sitemaps listing 109 URLs: 14 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −0.7 points
  • Internal link counts23 noted
    Internal link counts for 131 pages; 23 worth a look.
  • Thin contentOK
    0 of 123 pages have fewer than 200 words. 8 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format3 noted
    3 of 151 page URLs are harder to read, share or cache than they need to be.
  • Canonicals8 noted
    8 of 131 pages have a canonical worth checking.
  • Robots directives131 noted
    131 pages carry a robots directive; 0 carry none.
  • Anchor text19 noted
    19 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure64 noted
    64 of 123 pages could use the title, heading and snippet space better. 8 noindex or canonicalized pages excluded.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomalies16 noted
    16 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 131 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; 12 response headers recorded across 270 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 131 pages; 72 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 51 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%

lypkielaw.com scores 89%, higher than 82% 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 sites89% 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 site has a good health score, but there are issues with broken links, redirects, and missing meta descriptions. Address these to improve SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and are detrimental to SEO.

    How: Update or remove links pointing to 404 pages, such as those on team member pages.

    Checks: broken-links

  2. 2

    Clean Up Redirects

    Why: Too many redirects can slow down page loading and impact SEO.

    How: Eliminate unnecessary 301 redirects, particularly for the blog pages.

    Checks: redirects

  3. 3

    Improve Meta Descriptions

    Why: Meta descriptions influence click-through rates and search visibility.

    How: Add missing meta descriptions for 23 pages to provide clear content previews.

    Checks: meta-descriptions

  4. 4

    Resolve Non-200 Responses

    Why: Broken pages send negative signals to search engines.

    How: Fix 21 URLs that don't return a 2xx response; focus on 4 that show errors.

    Checks: status-codes

  5. 6

    Focus on Orphan Pages

    Why: Orphan pages lack inbound links, reducing their visibility.

    How: Link to the 16 orphan pages from other relevant pages to boost engagement.

    Checks: orphan-pages

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 critical security headers missing, which can expose it to various attacks. Implementing HTTP Strict Transport Security, Content Security Policy, and other headers will strengthen your site's defenses against threats like data interception and clickjacking.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors can be intercepted on their first request without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of CSP allows scripts from any source, increasing XSS risks.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, pages can be embedded in an unauthorized frame.

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

    Evidence: Clickjacking protection

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without this header, browsers can execute files incorrectly based on contents.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Lack of referrer policy exposes full URLs when users navigate away.

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

    Evidence: Referrer policy

  6. 6

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Compromised external scripts can modify site functionality.

    Fix: Implement a CSP that restricts script sources while considering SRI where possible.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not limiting features increases potential risks from injected scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    Evidence: Permissions policy

  8. 8

    Sensitive Paths in robots.txtInfo

    Why it matters: Publicly accessible robots.txt reveals paths that could be private.

    Fix: Consider implementing real access control on /wp-admin/ instead of relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

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://lypkielaw.com/ → no strict-transport-security
    • https://lypkielaw.com/our-law-firm/ → no strict-transport-security
    • https://lypkielaw.com/our-lawyers/ → no strict-transport-security
    • https://lypkielaw.com/fee-schedule/ → no strict-transport-security
    • https://lypkielaw.com/careers/ → no strict-transport-security
    • https://lypkielaw.com/pay-invoice/ → no strict-transport-security
    • https://lypkielaw.com/contact-us/ → no strict-transport-security
    • https://lypkielaw.com/wills-estates/ → no strict-transport-security
    • https://lypkielaw.com/real-estate/ → no strict-transport-security
    • https://lypkielaw.com/business-corporate-law/ → no strict-transport-security
    • https://lypkielaw.com/notary-services/ → no strict-transport-security
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 131 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://lypkielaw.com/ → no content-security-policy
    • https://lypkielaw.com/our-law-firm/ → no content-security-policy
    • https://lypkielaw.com/our-lawyers/ → no content-security-policy
    • https://lypkielaw.com/fee-schedule/ → no content-security-policy
    • https://lypkielaw.com/careers/ → no content-security-policy
    • https://lypkielaw.com/pay-invoice/ → no content-security-policy
    • https://lypkielaw.com/contact-us/ → no content-security-policy
    • https://lypkielaw.com/wills-estates/ → no content-security-policy
    • https://lypkielaw.com/real-estate/ → no content-security-policy
    • https://lypkielaw.com/business-corporate-law/ → no content-security-policy
    • https://lypkielaw.com/notary-services/ → no content-security-policy
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → 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://lypkielaw.com/ → no x-frame-options
    • https://lypkielaw.com/our-law-firm/ → no x-frame-options
    • https://lypkielaw.com/our-lawyers/ → no x-frame-options
    • https://lypkielaw.com/fee-schedule/ → no x-frame-options
    • https://lypkielaw.com/careers/ → no x-frame-options
    • https://lypkielaw.com/pay-invoice/ → no x-frame-options
    • https://lypkielaw.com/contact-us/ → no x-frame-options
    • https://lypkielaw.com/wills-estates/ → no x-frame-options
    • https://lypkielaw.com/real-estate/ → no x-frame-options
    • https://lypkielaw.com/business-corporate-law/ → no x-frame-options
    • https://lypkielaw.com/notary-services/ → no x-frame-options
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → 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://lypkielaw.com/ → no x-content-type-options
    • https://lypkielaw.com/our-law-firm/ → no x-content-type-options
    • https://lypkielaw.com/our-lawyers/ → no x-content-type-options
    • https://lypkielaw.com/fee-schedule/ → no x-content-type-options
    • https://lypkielaw.com/careers/ → no x-content-type-options
    • https://lypkielaw.com/pay-invoice/ → no x-content-type-options
    • https://lypkielaw.com/contact-us/ → no x-content-type-options
    • https://lypkielaw.com/wills-estates/ → no x-content-type-options
    • https://lypkielaw.com/real-estate/ → no x-content-type-options
    • https://lypkielaw.com/business-corporate-law/ → no x-content-type-options
    • https://lypkielaw.com/notary-services/ → no x-content-type-options
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → 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://lypkielaw.com/ → no referrer-policy
    • https://lypkielaw.com/our-law-firm/ → no referrer-policy
    • https://lypkielaw.com/our-lawyers/ → no referrer-policy
    • https://lypkielaw.com/fee-schedule/ → no referrer-policy
    • https://lypkielaw.com/careers/ → no referrer-policy
    • https://lypkielaw.com/pay-invoice/ → no referrer-policy
    • https://lypkielaw.com/contact-us/ → no referrer-policy
    • https://lypkielaw.com/wills-estates/ → no referrer-policy
    • https://lypkielaw.com/real-estate/ → no referrer-policy
    • https://lypkielaw.com/business-corporate-law/ → no referrer-policy
    • https://lypkielaw.com/notary-services/ → no referrer-policy
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → 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://lypkielaw.com/ → no permissions-policy
    • https://lypkielaw.com/our-law-firm/ → no permissions-policy
    • https://lypkielaw.com/our-lawyers/ → no permissions-policy
    • https://lypkielaw.com/fee-schedule/ → no permissions-policy
    • https://lypkielaw.com/careers/ → no permissions-policy
    • https://lypkielaw.com/pay-invoice/ → no permissions-policy
    • https://lypkielaw.com/contact-us/ → no permissions-policy
    • https://lypkielaw.com/wills-estates/ → no permissions-policy
    • https://lypkielaw.com/real-estate/ → no permissions-policy
    • https://lypkielaw.com/business-corporate-law/ → no permissions-policy
    • https://lypkielaw.com/notary-services/ → no permissions-policy
    • https://lypkielaw.com/adult-guardianship-trusteeship/ → no permissions-policy
  • 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.)

    • www.googletagmanager.com (80 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path 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/
6 checks passed, 2 not applicable
  • OKHTTPS

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

  • OKForms over HTTPS

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

  • Not applicableCookie flags

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

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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 lypkielaw.com

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

Own lypkielaw.com?