Scanned sites / bryanlawpc.com / 2026-11-02-2330

bryanlawpc.com scan from 2026-11-02 23:30:24 UTC DR 10

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

Scan 2026-11-02-2330

Scanned 2026-11-02 23:30:24 UTC, finished 2026-11-03 01:01:14 UTC. Found on page 1 of brave web search results

Site: https://bryanlawpc.com/

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

86/ 100Good

On November 2, 2026 the Site Spider crawled 171 pages and 124 assets of bryanlawpc.com, starting from https://bryanlawpc.com/. It scored 86 out of 100, a good result. 10 of 33 checks found something to fix, led by meta descriptions (112), heavy assets (4), title tags (38); 12 checks passed. Most of the points went to meta descriptions (−5.3), heavy assets (−2.4), title tags (−2.2). 11 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: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
171
Assets fetched
124
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

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

  • Title tags38 issues
    38 of 118 pages have title issues. 52 noindex or canonicalized pages excluded.
    −2.2 points
  • Meta descriptions112 issues
    112 of 118 pages have meta description issues. 52 noindex or canonicalized pages excluded.
    −5.3 points
  • Headings55 issues
    55 of 118 pages have heading issues. 52 noindex or canonicalized pages excluded.
    −1.9 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 4 could not be determined (timeouts, rate limits or refusals), of 8 destinations checked.
    −0.2 points
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
  • Non-200 responses3 noted
    3 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability6 issues
    6 of 125 indexable pages have indexability warnings. 45 pages noindex by design.
    −0.4 points
  • Image alt textOK
    0 of 349 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 124 fetched assets.
    −2.4 points
  • Orphan pages16 issues
    16 pages have no internal links pointing at them.
    −0.4 points
  • Sitemap coverage37 issues
    5 sitemaps listing 97 URLs: 21 crawled pages missing, 0 listed URLs broken or redirecting, 16 reachable only via the sitemap.
    −1.3 points
  • Internal link counts66 noted
    Internal link counts for 170 pages; 66 worth a look.
  • Thin content3 issues
    3 of 118 pages have fewer than 200 words. 52 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format8 noted
    8 of 171 page URLs are harder to read, share or cache than they need to be.
  • Canonicals52 noted
    52 of 170 pages have a canonical worth checking.
  • Robots directives170 noted
    170 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure63 noted
    63 of 118 pages could use the title, heading and snippet space better. 52 noindex or canonicalized pages excluded.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationOK
    All 170 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    170 of 118 indexable pages carry structured data: WebSite (170), BreadcrumbList (164), ListItem (164), CollectionPage (91), WebPage (79). 0 pages with errors a rich result would fail on.
  • Near duplicates11 noted
    11 pages in 2 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 170 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 positions5 noted
    5 of 102 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    30 pages in pagination sequences; 0 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 12 response headers recorded across 295 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 170 pages; 90 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling12 noted
    12 words an English dictionary does not know, on 25 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2704 sites, median 80%, average 78%

bryanlawpc.com scores 86%, higher than 76% of the 2704 scanned sites. See the full ranking.

0631260%: 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%: 1 site37%: 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%: 6 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 9 sites56%: 7 sites57%: 16 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 40 sites67%: 40 sites68%: 39 sites69%: 50 sites70%: 46 sites71%: 78 sites72%: 74 sites73%: 82 sites74%: 77 sites75%: 87 sites76%: 96 sites77%: 107 sites78%: 123 sites79%: 109 sites80%: 124 sites81%: 120 sites82%: 123 sites83%: 118 sites84%: 126 sites85%: 102 sites86%: 90 sites87%: 91 sites88%: 77 sites89%: 72 sites90%: 52 sites91%: 56 sites92%: 40 sites93%: 28 sites94%: 23 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 76 sites86% 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

This site has some technical SEO issues that need fixing. Focus on optimizing title tags, meta descriptions, headings, and addressing indexability warnings first. Improving orphan pages, asset size, and thin content will also enhance performance.

  1. 1

    Optimize Title Tags

    Why: 38 pages have title issues impacting SEO.

    How: Revise overlong and too short titles to keep them under 60 characters. Add unique titles if missing.

    Checks: titles

  2. 2

    Improve Meta Descriptions

    Why: 112 pages lack effective meta descriptions affecting click-through rates.

    How: Write concise and relevant meta descriptions under 160 characters for the affected pages.

    Checks: meta-descriptions

  3. 3

    Fix Heading Issues

    Why: 55 pages have heading issues which can confuse both users and search engines.

    How: Ensure each page has one H1 tag. Adjust or add H1s where missing.

    Checks: headings

  4. 4

    Address Indexability Warnings

    Why: 6 pages with warnings might not rank well due to technical issues.

    How: Review canonical tags and sitemap entries for affected pages to ensure proper indexing.

    Checks: indexability

  5. 5

    Link Orphan Pages

    Why: 16 orphan pages lack internal links, reducing their visibility.

    How: Create contextual internal links to the orphan pages from relevant content throughout the site.

    Checks: orphan-pages

  6. 6

    Reduce Heavy Assets

    Why: Larger assets can slow your site's loading time.

    How: Optimize the listed heavy assets by compressing images and minimizing CSS/JS files.

    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

The website bryanlawpc.com has several security issues that need immediate attention, including missing protections against data interception and clickjacking, as well as inadequate content policies. Implementing recommended headers will enhance the site’s security posture significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, initial connections without HTTPS can be intercepted.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to your HTTP response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Without CSP, there are no restrictions on where scripts can be loaded from, risking XSS attacks.

    Fix: Include 'Content-Security-Policy: default-src 'self';' in your HTTP response headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header makes the site vulnerable to clickjacking attacks.

    Fix: Implement 'X-Frame-Options: DENY' in your HTTP response headers.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

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

    Fix: Add 'X-Content-Type-Options: nosniff' to your HTTP response headers.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Without this policy, full URLs are shared with other sites when links are clicked.

    Fix: Set 'Referrer-Policy: no-referrer' in your HTTP response headers.

    Evidence: Referrer policy

  6. 6

    Third-party Scripts Lack Subresource IntegrityLow

    Why it matters: Scripts from external domains could be modified, affecting site security.

    Fix: Consider implementing Subresource Integrity or a restrictive Content-Security-Policy.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header limits access to sensitive browser features, reducing injection risks.

    Fix: Implement 'Permissions-Policy: geolocation=(self), microphone=()' in your HTTP response headers.

    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://bryanlawpc.com/ → no strict-transport-security
    • https://bryanlawpc.com/our-attorneys/ → no strict-transport-security
    • https://bryanlawpc.com/our-staff/ → no strict-transport-security
    • https://bryanlawpc.com/estate-planning/ → no strict-transport-security
    • https://bryanlawpc.com/trust-administration/ → no strict-transport-security
    • https://bryanlawpc.com/blogs/ → no strict-transport-security
    • https://bryanlawpc.com/contact-us/ → no strict-transport-security
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no strict-transport-security
    • https://bryanlawpc.com/1385-2/ → no strict-transport-security
    • https://bryanlawpc.com/1348-2/ → no strict-transport-security
    • https://bryanlawpc.com/category/uncategorized/ → no strict-transport-security
    • https://bryanlawpc.com/category/estate-planning/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 170 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://bryanlawpc.com/ → no content-security-policy
    • https://bryanlawpc.com/our-attorneys/ → no content-security-policy
    • https://bryanlawpc.com/our-staff/ → no content-security-policy
    • https://bryanlawpc.com/estate-planning/ → no content-security-policy
    • https://bryanlawpc.com/trust-administration/ → no content-security-policy
    • https://bryanlawpc.com/blogs/ → no content-security-policy
    • https://bryanlawpc.com/contact-us/ → no content-security-policy
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no content-security-policy
    • https://bryanlawpc.com/1385-2/ → no content-security-policy
    • https://bryanlawpc.com/1348-2/ → no content-security-policy
    • https://bryanlawpc.com/category/uncategorized/ → no content-security-policy
    • https://bryanlawpc.com/category/estate-planning/ → 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://bryanlawpc.com/ → no x-frame-options
    • https://bryanlawpc.com/our-attorneys/ → no x-frame-options
    • https://bryanlawpc.com/our-staff/ → no x-frame-options
    • https://bryanlawpc.com/estate-planning/ → no x-frame-options
    • https://bryanlawpc.com/trust-administration/ → no x-frame-options
    • https://bryanlawpc.com/blogs/ → no x-frame-options
    • https://bryanlawpc.com/contact-us/ → no x-frame-options
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no x-frame-options
    • https://bryanlawpc.com/1385-2/ → no x-frame-options
    • https://bryanlawpc.com/1348-2/ → no x-frame-options
    • https://bryanlawpc.com/category/uncategorized/ → no x-frame-options
    • https://bryanlawpc.com/category/estate-planning/ → 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://bryanlawpc.com/ → no x-content-type-options
    • https://bryanlawpc.com/our-attorneys/ → no x-content-type-options
    • https://bryanlawpc.com/our-staff/ → no x-content-type-options
    • https://bryanlawpc.com/estate-planning/ → no x-content-type-options
    • https://bryanlawpc.com/trust-administration/ → no x-content-type-options
    • https://bryanlawpc.com/blogs/ → no x-content-type-options
    • https://bryanlawpc.com/contact-us/ → no x-content-type-options
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no x-content-type-options
    • https://bryanlawpc.com/1385-2/ → no x-content-type-options
    • https://bryanlawpc.com/1348-2/ → no x-content-type-options
    • https://bryanlawpc.com/category/uncategorized/ → no x-content-type-options
    • https://bryanlawpc.com/category/estate-planning/ → 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://bryanlawpc.com/ → no referrer-policy
    • https://bryanlawpc.com/our-attorneys/ → no referrer-policy
    • https://bryanlawpc.com/our-staff/ → no referrer-policy
    • https://bryanlawpc.com/estate-planning/ → no referrer-policy
    • https://bryanlawpc.com/trust-administration/ → no referrer-policy
    • https://bryanlawpc.com/blogs/ → no referrer-policy
    • https://bryanlawpc.com/contact-us/ → no referrer-policy
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no referrer-policy
    • https://bryanlawpc.com/1385-2/ → no referrer-policy
    • https://bryanlawpc.com/1348-2/ → no referrer-policy
    • https://bryanlawpc.com/category/uncategorized/ → no referrer-policy
    • https://bryanlawpc.com/category/estate-planning/ → 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://bryanlawpc.com/ → no permissions-policy
    • https://bryanlawpc.com/our-attorneys/ → no permissions-policy
    • https://bryanlawpc.com/our-staff/ → no permissions-policy
    • https://bryanlawpc.com/estate-planning/ → no permissions-policy
    • https://bryanlawpc.com/trust-administration/ → no permissions-policy
    • https://bryanlawpc.com/blogs/ → no permissions-policy
    • https://bryanlawpc.com/contact-us/ → no permissions-policy
    • https://bryanlawpc.com/inheritors-trusts-trusts-for-children-in-an-estate-plan/ → no permissions-policy
    • https://bryanlawpc.com/1385-2/ → no permissions-policy
    • https://bryanlawpc.com/1348-2/ → no permissions-policy
    • https://bryanlawpc.com/category/uncategorized/ → no permissions-policy
    • https://bryanlawpc.com/category/estate-planning/ → no permissions-policy
  • 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.)

    • www.googletagmanager.com (40 script tags)
    • cdn.elementor.com (40 script tags)
8 checks passed, 1 not applicable
  • OKHTTPS

    All 170 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

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

Own bryanlawpc.com?