Scanned sites / www.bridlewoodeyecare.com / 2026-09-13-0207

www.bridlewoodeyecare.com scan from 2026-09-13 02:07:09 UTC DR 2

A newer scan exists. See the latest report for www.bridlewoodeyecare.com.

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

Scan 2026-09-13-0207

Scanned 2026-09-13 02:07:09 UTC, finished 2026-09-13 02:21:56 UTC. Found on page 1 of brave web search results

Site: https://www.bridlewoodeyecare.com/

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

89/ 100Good

On September 13, 2026 the Site Spider crawled 167 pages and 114 assets of www.bridlewoodeyecare.com, starting from https://www.bridlewoodeyecare.com/. It scored 89 out of 100, a good result. 7 of 27 checks found something to fix, led by meta descriptions (61), title tags (46), sitemap coverage (59); 9 checks passed. Most of the points went to meta descriptions (−3.4), title tags (−3.2), sitemap coverage (−2.5). 11 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
167
Assets fetched
114
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

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

  • Title tags46 issues
    46 of 133 pages have title issues. 11 noindex or canonicalized pages excluded.
    −3.2 points
  • Meta descriptions61 issues
    61 of 133 pages have meta description issues. 11 noindex or canonicalized pages excluded.
    −3.4 points
  • Headings3 issues
    3 of 133 pages have heading issues. 11 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites868 noted
    0 destinations answered with an error, 9 could not be determined (timeouts, rate limits or refusals), of 22 destinations checked.
  • Redirects23 issues
    23 redirecting URLs, 4 of them chained.
    −0.6 points
  • Non-200 responses23 noted
    23 URLs did not return a 2xx response. 23 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability8 issues
    8 of 141 indexable pages have indexability warnings. 3 pages noindex by design.
    −0.6 points
  • Image alt textOK
    0 of 4315 image references have no alt attribute. 1 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 114 fetched assets.
    −0.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage59 issues
    1 sitemap listing 74 URLs: 59 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −2.5 points
  • Internal link counts4 noted
    Internal link counts for 144 pages; 4 worth a look.
  • Thin contentOK
    0 of 133 pages have fewer than 200 words. 11 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format8 noted
    8 of 167 page URLs are harder to read, share or cache than they need to be.
  • Canonicals9 noted
    9 of 144 pages have a canonical worth checking.
  • Robots directives76 noted
    76 pages carry a robots directive; 68 carry none.
  • Anchor text39 noted
    39 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure53 noted
    53 of 133 pages could use the title, heading and snippet space better. 11 noindex or canonicalized pages excluded.
  • Image weight and alt length1 noted
    0 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomalies5 noted
    5 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 144 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; 14 response headers recorded across 281 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 144 pages; 3 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 71 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

2711 sites, median 80%, average 78%

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

0641270%: 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%: 119 sites82%: 125 sites83%: 118 sites84%: 127 sites85%: 102 sites86%: 91 sites87%: 91 sites88%: 77 sites89%: 73 sites90%: 53 sites91%: 56 sites92%: 40 sites93%: 28 sites94%: 23 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 78 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. 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 several issues to address, predominantly with redirects, title tags, and indexability. Prioritizing these fixes will improve user experience and SEO performance.

  1. 1

    Fix Redirects

    Why: Chained redirects can slow down site performance and confuse search engines.

    How: Reduce the 23 redirects, especially the 4 chained ones by updating links directly to final URLs.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: 23 URLs returning non-200 responses may lead to poor user experience and SEO.

    How: Update or remove the 23 URLs that return non-200 responses, ensuring they return a 200 status code.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: 46 pages with title issues can affect rankings and CTR.

    How: Shorten the title tags of affected pages to under 60 characters focusing on clarity.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: 17 pages have meta description issues which can impact click-through rates.

    How: Revise the meta descriptions to be under 160 characters, making them concise and engaging.

    Checks: meta-descriptions

  5. 5

    Address Missing Headings

    Why: Pages without an H1 affect both user readability and SEO.

    How: Add a proper H1 tag to the 3 pages identified as missing one.

    Checks: headings

  6. 6

    Update Sitemap Coverage

    Why: 59 crawled pages are not listed in the sitemap, limiting discoverability.

    How: Ensure that the sitemap includes all relevant URLs, and resubmit it to search engines.

    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

The security review for www.bridlewoodeyecare.com identified several issues. The main concerns are the lack of HTTP Strict Transport Security (HSTS) which can allow interception of user data, vulnerabilities in JavaScript libraries, and the exposure of a Google API key. Addressing these vulnerabilities will enhance the site's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users are vulnerable to man-in-the-middle attacks on initial requests.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all HTML responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: jQuery 2.9.2 has known vulnerabilities that could be exploited depending on usage.

    Fix: Upgrade jQuery to version 3.5.0 or newer to mitigate vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Exposed Google API KeyMedium

    Why it matters: Displaying a Google API key can allow unauthorized usage if not properly restricted.

    Fix: Restrict the API key by HTTP referrer and configure access in the Google Cloud Console.

    Evidence: Keys and secrets in page code

  4. 4

    Server Version DisclosureLow

    Why it matters: Disclosing server version information can help attackers find vulnerabilities.

    Fix: Configure the server to hide version information by setting 'server_tokens off;' in the Nginx configuration.

    Evidence: Software version disclosure

  5. 5

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from external domains could be altered and pose a security risk.

    Fix: Consider implementing a Content-Security-Policy that includes these domains to mitigate risks.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths Listed in robots.txtInfo

    Why it matters: The presence of sensitive paths can help an attacker probe the site more vigorously.

    Fix: Ensure access control is in place for /wp-admin/ and /wp-login.php; consider removing these from 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://www.bridlewoodeyecare.com/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/locations-hours/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/whats-new/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/our-team/job-opportunity/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/our-doctors/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/our-team/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/eye-care-services-calgary/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/eye-care-services-calgary/dry-eye-treatment/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/eye-care-services-calgary/myopia-control/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/eye-care-services-calgary/pediatric-eye-exams/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/eye-care-services-calgary/comprehensive-eye-exams/ → no strict-transport-security
    • https://www.bridlewoodeyecare.com/contact-lenses/ → no strict-transport-security
  • 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 (281 responses)
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.9.2 in https://www.bridlewoodeyecare.com/wp-content/plugins/gravityforms/js/placeholde…: 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
  • 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.bridlewoodeyecare.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 (80 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
7 checks passed, 3 not applicable
  • OKHTTPS

    All 144 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • Not applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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

Own www.bridlewoodeyecare.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.bridlewoodeyecare.com. Removal needs no account and no proof of purchase.