Scanned sites / www.capitaleyecare.com / 2026-10-01-0356

www.capitaleyecare.com scan from 10/1/2026, 3:56:35 AM

Scan 2026-10-01-0356

Scanned 10/1/2026, 3:56:35 AM, finished 10/1/2026, 4:55:43 AM. Found on page 1 of brave web search results

Site: https://www.capitaleyecare.com/

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

89/ 100Good

On October 1, 2026 the Site Spider crawled 197 pages and 52 assets of www.capitaleyecare.com, starting from https://www.capitaleyecare.com/. It scored 89 out of 100, a good result. 8 of 16 checks found something to fix, led by title tags (58), sitemap coverage (65), meta descriptions (44); 7 checks passed. Most of the points went to title tags (−3.6), sitemap coverage (−2.4), meta descriptions (−2.2). 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: Medium2 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
197
Assets fetched
52
Status
Completed
Checks with issues
8 of 16
CoverageComplete crawl

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

  • Title tags58 issues
    58 of 73 pages have title issues. 90 noindex or canonicalized pages excluded.
    −3.6 points
  • Meta descriptions44 issues
    44 of 73 pages have meta description issues. 90 noindex or canonicalized pages excluded.
    −2.2 points
  • Headings2 issues
    2 of 73 pages have heading issues. 90 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links11 issues
    561 internal links point at 11 broken URLs.
    −1.3 points
  • Links to other sites1 issue
    1 destination answered with an error, 8 could not be determined (timeouts, rate limits or refusals), of 17 destinations checked.
    −0.3 points
  • Redirects20 issues
    19 redirecting URLs, 5 of them chained.
    −0.5 points
  • Non-200 responses15 issues
    34 URLs did not return a 2xx response. 34 of them are pages, 15 with an error status; the rest are assets or redirects.
    −0.9 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 73 indexable pages have indexability warnings. 90 pages noindex by design.
  • Image alt textOK
    0 of 778 image references have no alt attribute. 4 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 52 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage65 issues
    1 sitemap listing 8 URLs: 65 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −2.4 points
  • Internal link countsOK
    Internal link counts for 163 pages.
  • Thin contentOK
    0 of 73 pages have fewer than 200 words. 90 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1436 sites, median 80%, average 79%

www.capitaleyecare.com scores 89%, higher than 85% of the 1436 scanned sites. See the full ranking.

043850%: 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%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 3 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 6 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 8 sites61%: 11 sites62%: 15 sites63%: 14 sites64%: 8 sites65%: 14 sites66%: 15 sites67%: 26 sites68%: 24 sites69%: 17 sites70%: 34 sites71%: 33 sites72%: 42 sites73%: 33 sites74%: 41 sites75%: 46 sites76%: 54 sites77%: 47 sites78%: 66 sites79%: 53 sites80%: 72 sites81%: 85 sites82%: 72 sites83%: 67 sites84%: 61 sites85%: 46 sites86%: 50 sites87%: 49 sites88%: 51 sites89%: 37 sites90%: 30 sites91%: 33 sites92%: 19 sites93%: 9 sites94%: 10 sites95%: 7 sites96%: 6 sites97%: 5 sites98%: 1 site99%: 2 sites100%: 51 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

You have a good health score, but several internal issues need attention, mainly broken links and meta descriptions. Address these to enhance user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: 561 internal links are broken, impacting user experience and SEO.

    How: Identify and remove links pointing to non-existent pages. Use the provided tasks to fix major broken URLs.

    Checks: broken-links

  2. 2

    Improve Meta Descriptions

    Why: 44 pages lack proper meta descriptions, which help improve click-through rates.

    How: Write unique and relevant meta descriptions for all pages that are missing them.

    Checks: meta-descriptions

  3. 3

    Resolve Redirect Issues

    Why: 19 URLs redirect, with some being chained, affecting site speed and user experience.

    How: Simplify redirects where possible by updating internal links to point to final URLs directly.

    Checks: redirects

  4. 4

    Address Title Tag Issues

    Why: 58 pages have title issues, affecting search visibility and relevance.

    How: Revise each title to ensure they are between 30 and 60 characters long and relevant.

    Checks: titles

  5. 5

    Fix Heading Structure

    Why: 2 pages have multiple H1 headings, which can confuse search engines and users.

    How: Ensure each page contains a single H1, then adjust other headings accordingly.

    Checks: headings

  6. 6

    Update Sitemap Coverage

    Why: 65 critical pages are not listed in the sitemap, limiting their discoverability.

    How: Add these pages to your sitemap to ensure search engines can crawl them effectively.

    Checks: sitemap-coverage

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 security vulnerabilities that should be addressed to protect user data and enhance privacy. Key issues include a lack of HTTP Strict Transport Security, missing referrer policies, and exposure of sensitive API keys. Prioritizing these fixes will help secure your users and improve overall security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors may be intercepted on their first request if they type the site address without https://.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Exposed Google API KeyMedium

    Why it matters: The Google API key found in your code needs restrictions to prevent misuse by unauthorized parties.

    Fix: Restrict the API key by HTTP referrer in the Google Cloud Console and ensure it’s not embedded in public code.

    Evidence: Keys and secrets in page code

  3. 3

    Missing Referrer PolicyLow

    Why it matters: Without a proper Referrer Policy, sensitive page information can be exposed to third-party sites upon navigation.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade.

    Evidence: Referrer policy

  4. 4

    Server Version DisclosureLow

    Why it matters: Disclosing server version information can help attackers identify vulnerabilities to exploit.

    Fix: Configure your web server to hide the version number, e.g., by setting server_tokens off in nginx.

    Evidence: Software version disclosure

  5. 5

    Missing Permissions PolicyInfo

    Why it matters: A Permissions Policy can limit potential risks from injected scripts accessing sensitive browser features.

    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.capitaleyecare.com/ → no strict-transport-security
    • https://www.capitaleyecare.com/contact-us/appointment-request-form/ → no strict-transport-security
    • https://www.capitaleyecare.com/patient-history-form/ → no strict-transport-security
    • https://www.capitaleyecare.com/contact-us/ → no strict-transport-security
    • https://www.capitaleyecare.com/hours-location/ → no strict-transport-security
    • https://www.capitaleyecare.com/our-eye-doctors/ → no strict-transport-security
    • https://www.capitaleyecare.com/the-staff/ → no strict-transport-security
    • https://www.capitaleyecare.com/eye-care-services/ → no strict-transport-security
    • https://www.capitaleyecare.com/eyeglasses-contacts/ → no strict-transport-security
    • https://www.capitaleyecare.com/insurance/ → no strict-transport-security
    • https://www.capitaleyecare.com/eye-care-services/management-of-ocular-diseases/glaucoma-testing-treatment/ → no strict-transport-security
    • https://www.capitaleyecare.com/eye-care-services/your-eye-health/eye-diseases/diabetes-and-eyesight/treatment-for-diabe… → no strict-transport-security
  • 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.capitaleyecare.com/ → no referrer-policy
    • https://www.capitaleyecare.com/contact-us/appointment-request-form/ → no referrer-policy
    • https://www.capitaleyecare.com/patient-history-form/ → no referrer-policy
    • https://www.capitaleyecare.com/contact-us/ → no referrer-policy
    • https://www.capitaleyecare.com/hours-location/ → no referrer-policy
    • https://www.capitaleyecare.com/our-eye-doctors/ → no referrer-policy
    • https://www.capitaleyecare.com/the-staff/ → no referrer-policy
    • https://www.capitaleyecare.com/eye-care-services/ → no referrer-policy
    • https://www.capitaleyecare.com/eyeglasses-contacts/ → no referrer-policy
    • https://www.capitaleyecare.com/insurance/ → no referrer-policy
    • https://www.capitaleyecare.com/eye-care-services/management-of-ocular-diseases/glaucoma-testing-treatment/ → no referrer-policy
    • https://www.capitaleyecare.com/eye-care-services/your-eye-health/eye-diseases/diabetes-and-eyesight/treatment-for-diabe… → 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.capitaleyecare.com/ → no permissions-policy
    • https://www.capitaleyecare.com/contact-us/appointment-request-form/ → no permissions-policy
    • https://www.capitaleyecare.com/patient-history-form/ → no permissions-policy
    • https://www.capitaleyecare.com/contact-us/ → no permissions-policy
    • https://www.capitaleyecare.com/hours-location/ → no permissions-policy
    • https://www.capitaleyecare.com/our-eye-doctors/ → no permissions-policy
    • https://www.capitaleyecare.com/the-staff/ → no permissions-policy
    • https://www.capitaleyecare.com/eye-care-services/ → no permissions-policy
    • https://www.capitaleyecare.com/eyeglasses-contacts/ → no permissions-policy
    • https://www.capitaleyecare.com/insurance/ → no permissions-policy
    • https://www.capitaleyecare.com/eye-care-services/management-of-ocular-diseases/glaucoma-testing-treatment/ → no permissions-policy
    • https://www.capitaleyecare.com/eye-care-services/your-eye-health/eye-diseases/diabetes-and-eyesight/treatment-for-diabe… → 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: nginx/1.26.3 (249 responses)
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…uY (39 chars) in https://www.capitaleyecare.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • 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)
    • www.googleadservices.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 paths 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/
    • Disallow: /wp-login.php
8 checks passed, 1 not applicable
  • OKHTTPS

    All 163 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

    x-frame-options is set on all 163 HTML pages.

  • OKMIME sniffing protection

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

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    116 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

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

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

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

Own www.capitaleyecare.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.capitaleyecare.com. Removal needs no account and no proof of purchase.
www.capitaleyecare.com scan 2026-10-01-0356 | DIY SEO Hub