Scanned sites / www.fargoeyecare.com / 2026-10-02-2227

www.fargoeyecare.com scan from 10/2/2026, 10:27:19 PM

Scan 2026-10-02-2227

Scanned 10/2/2026, 10:27:19 PM, finished 10/2/2026, 11:26:02 PM. Found on page 1 of brave web search results

Site: https://www.fargoeyecare.com/

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

91/ 100Excellent

On October 2, 2026 the Site Spider crawled 226 pages and 66 assets of www.fargoeyecare.com, starting from https://www.fargoeyecare.com/. It scored 91 out of 100, an excellent result. 9 of 16 checks found something to fix, led by title tags (54), meta descriptions (51), heavy assets (3); 6 checks passed. Most of the points went to title tags (−2.7), meta descriptions (−2), heavy assets (−1.8). 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
226
Assets fetched
66
Status
Completed
Checks with issues
9 of 16
CoverageComplete crawl

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

  • Title tags54 issues
    54 of 78 pages have title issues. 123 noindex or canonicalized pages excluded.
    −2.7 points
  • Meta descriptions51 issues
    51 of 78 pages have meta description issues. 123 noindex or canonicalized pages excluded.
    −2 points
  • Headings2 issues
    2 of 78 pages have heading issues. 123 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links3 issues
    203 internal links point at 3 broken URLs.
    −0.3 points
  • Links to other sites2 issues
    2 destinations answered with an error, 8 could not be determined (timeouts, rate limits or refusals), of 20 destinations checked.
    −0.4 points
  • Redirects19 issues
    18 redirecting URLs, 5 of them chained.
    −0.4 points
  • Non-200 responses7 issues
    29 URLs did not return a 2xx response. 25 of them are pages, 7 with an error status; the rest are assets or redirects.
    −0.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 78 indexable pages have indexability warnings. 123 pages noindex by design.
  • Image alt textOK
    0 of 1107 image references have no alt attribute.
  • Heavy assets3 issues
    3 assets larger than 500 KB among 66 fetched assets.
    −1.8 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage54 issues
    1 sitemap listing 24 URLs: 54 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −1.6 points
  • Internal link countsOK
    Internal link counts for 201 pages.
  • Thin contentOK
    0 of 78 pages have fewer than 200 words. 123 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1860 sites, median 80%, average 79%

www.fargoeyecare.com scores 91%, higher than 90% of the 1860 scanned sites. See the full ranking.

0541070%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 13 sites59%: 6 sites60%: 10 sites61%: 12 sites62%: 16 sites63%: 16 sites64%: 11 sites65%: 20 sites66%: 20 sites67%: 36 sites68%: 30 sites69%: 26 sites70%: 38 sites71%: 40 sites72%: 55 sites73%: 52 sites74%: 49 sites75%: 59 sites76%: 73 sites77%: 72 sites78%: 86 sites79%: 65 sites80%: 91 sites81%: 107 sites82%: 84 sites83%: 86 sites84%: 86 sites85%: 61 sites86%: 71 sites87%: 61 sites88%: 65 sites89%: 54 sites90%: 34 sites91%: 36 sites92%: 28 sites93%: 15 sites94%: 13 sites95%: 12 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites91% 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

Your site has several key issues affecting SEO performance, particularly with broken links and titles. Address these as a priority while also improving sitemap coverage for better crawlability.

  1. 1

    Fix Broken Links

    Why: 203 internal links point to 3 broken URLs, affecting user experience.

    How: Identify and update or remove links leading to 404 errors, especially on high-traffic pages.

    Checks: broken-links

  2. 2

    Simplify Redirects

    Why: 18 URLs are redirecting, with 5 chained. This can slow down page load times.

    How: Reduce redirection hops by updating the original links to the final destinations directly.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 29 URLs are returning non-200 responses, meaning they are not accessible.

    How: Fix or remove URLs returning errors. Focus on fixing those most linked or visited.

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: 54 of 78 pages have title issues, diminishing their search relevance.

    How: Review and update title tags to be descriptive, ideally between 30-60 characters in length.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: 51 of 78 pages have meta description issues, reducing click-through rates.

    How: Add or revise meta descriptions for clarity and appeal, aiming for around 150-160 characters.

    Checks: meta-descriptions

  6. 6

    Expand Sitemap Coverage

    Why: 54 URLs crawled are not listed in the sitemap, leading to missed indexing opportunities.

    How: Update the sitemap to include all relevant URLs ensuring comprehensive site coverage.

    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 lacks several important security headers and exposes a sensitive Google API key. Implementing HTTP Strict Transport Security (HSTS) is essential to protect against interception, while setting a referrer policy can enhance privacy. Additional security measures like configuring permissions and handling sensitive information will strengthen overall security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing the site address can be intercepted before securing the connection.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Sensitive Google API Key ExposedMedium

    Why it matters: An exposed key can allow unauthorized access to Google services and should be restricted.

    Fix: Restrict the API key in the Google Cloud console by setting an HTTP referrer.

    Evidence: Keys and secrets in page code

  3. 3

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive data may be leaked to other sites when users navigate away.

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

    Evidence: Referrer policy

  4. 4

    Server Version DisclosureLow

    Why it matters: Revealing the server version can aid attackers in targeting known vulnerabilities.

    Fix: Hide server version by updating Nginx configurations or using a reverse proxy.

    Evidence: Software version disclosure

  5. 5

    Missing Permissions PolicyInfo

    Why it matters: Not setting a permissions policy leaves browser features potentially open to abuse by malicious scripts.

    Fix: Add the header: Permissions-Policy: frame-ancestors 'none'; geolocation=(), 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.fargoeyecare.com/ → no strict-transport-security
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo/ → no strict-transport-security
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo-2/ → no strict-transport-security
    • https://www.fargoeyecare.com/contact-us/appointment-request-form/ → no strict-transport-security
    • https://www.fargoeyecare.com/our-eye-care-clinic/ → no strict-transport-security
    • https://www.fargoeyecare.com/our-eye-doctors/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/optos-retinal-screening/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/pediatric-eye-exams/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/management-of-ocular-diseases/ → no strict-transport-security
    • https://www.fargoeyecare.com/eye-care-services/eye-emergencies-pinkred-eyes/ → 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.fargoeyecare.com/ → no referrer-policy
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo/ → no referrer-policy
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo-2/ → no referrer-policy
    • https://www.fargoeyecare.com/contact-us/appointment-request-form/ → no referrer-policy
    • https://www.fargoeyecare.com/our-eye-care-clinic/ → no referrer-policy
    • https://www.fargoeyecare.com/our-eye-doctors/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/optos-retinal-screening/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/pediatric-eye-exams/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/management-of-ocular-diseases/ → no referrer-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-emergencies-pinkred-eyes/ → 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.fargoeyecare.com/ → no permissions-policy
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo/ → no permissions-policy
    • https://www.fargoeyecare.com/location/eye-care-associates-fargo-2/ → no permissions-policy
    • https://www.fargoeyecare.com/contact-us/appointment-request-form/ → no permissions-policy
    • https://www.fargoeyecare.com/our-eye-care-clinic/ → no permissions-policy
    • https://www.fargoeyecare.com/our-eye-doctors/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/optos-retinal-screening/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-exams/pediatric-eye-exams/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/management-of-ocular-diseases/ → no permissions-policy
    • https://www.fargoeyecare.com/eye-care-services/eye-emergencies-pinkred-eyes/ → 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 (292 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.fargoeyecare.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.googleadservices.com (40 script tags)
    • ecpbuilder.com (31 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 201 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKMixed content

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

  • OKForms over HTTPS

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

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