Scanned sites / www.bridlewoodeyecare.com / 2026-09-12-0012

www.bridlewoodeyecare.com scan from 2026-09-12 00:12:05 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-12-0012

Scanned 2026-09-12 00:12:05 UTC, finished 2026-09-12 01:17:20 UTC

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 12, 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 26 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). 10 checks found something the score does not count, listed as noted. 11 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 26
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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • 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

2326 sites, median 79%, average 78%

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

0571140%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 4 sites52%: 11 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 99 sites84%: 106 sites85%: 86 sites86%: 69 sites87%: 75 sites88%: 59 sites89%: 63 sites90%: 34 sites91%: 47 sites92%: 38 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 10 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 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's SEO health is excellent, but there are some redirect, title, meta description, heading, indexability, and sitemap issues to address. Prioritize the fixes listed below for the most impact.

  1. 1

    Fix Redirects and Non-200 Responses

    Why: Eliminating redirects and correcting URLs improves user experience and search engine crawling.

    How: Identify all redirect chains and update links directly to the final URL. Resolve non-200 responses by ensuring URLs return a 200 status.

    Checks: redirects, status-codes

  2. 2

    Optimize Title Tags

    Why: Shortening title tags will improve visibility in search engine results.

    How: Edit titles to be under 60 characters, focusing on primary keywords.

    Checks: titles

  3. 3

    Update Meta Descriptions

    Why: Effective meta descriptions encourage higher click-through rates from search results.

    How: Revise descriptions to be within 150-160 characters while summarizing the page content effectively.

    Checks: meta-descriptions

  4. 4

    Add Missing Headings

    Why: Proper headings structure improves both user navigation and SEO.

    How: Ensure each page has a relevant H1 heading and includes additional H2 headings as needed.

    Checks: headings

  5. 5

    Resolve Indexability Issues

    Why: Fixing canonical tags will ensure the correct URLs are indexed, preventing duplicate content problems.

    How: Update or remove incorrect canonical links on the affected pages.

    Checks: indexability

  6. 6

    Enhance Sitemap Coverage

    Why: Including all relevant URLs in the sitemap improves indexing by search engines.

    How: Update the sitemap to include all missing 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 website has several security concerns, including missing HTTP Strict Transport Security, revealing server version details, and use of a vulnerable jQuery library. Additionally, an exposed Google API key could lead to unauthorized access. Immediate remediation is recommended to enhance security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first request 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

    Use of Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 2.9.2 exposes your site to several security vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Exposed Google API KeyMedium

    Why it matters: An exposed API key can be misused if not properly restricted.

    Fix: Restrict the API key in the Google Cloud console by domain and referrer.

    Evidence: Keys and secrets in page code

  4. 4

    Exposed Server Version InformationLow

    Why it matters: Revealing the server version enables attackers to look for known vulnerabilities easily.

    Fix: Configure the server to not disclose the version; set 'server_tokens off;' in nginx.

    Evidence: Software version disclosure

  5. 5

    Lack of Subresource Integrity for Third-party ScriptsLow

    Why it matters: Without Subresource Integrity, third-party scripts can be altered maliciously.

    Fix: Implement a Content-Security-Policy that specifies trusted hosts for scripts.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths Listed in robots.txtInfo

    Why it matters: Exposing sensitive paths could assist attackers in probing for vulnerabilities.

    Fix: Ensure proper access controls are in place for the listed paths.

    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.