Scanned sites / www.cresteyecare.com / 2026-10-02-0132

www.cresteyecare.com scan from 10/2/2026, 1:32:09 AM

Scan 2026-10-02-0132

Scanned 10/2/2026, 1:32:09 AM, finished 10/2/2026, 1:53:42 AM. Found on page 1 of brave web search results

Site: https://www.cresteyecare.com/

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

87/ 100Good

On October 2, 2026 the Site Spider crawled 173 pages and 164 assets of www.cresteyecare.com, starting from https://www.cresteyecare.com/. It scored 87 out of 100, a good result. 9 of 16 checks found something to fix, led by title tags (48), meta descriptions (55), sitemap coverage (57); 5 checks passed. Most of the points went to title tags (−3.4), meta descriptions (−3.1), heavy assets (−2.4). 2 checks 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, 3 low and 2 info findings. See the security findings ↓

Pages crawled
173
Assets fetched
164
Status
Completed
Checks with issues
9 of 16
CoverageComplete crawl

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

  • Title tags48 issues
    48 of 136 pages have title issues. 4 noindex or canonicalized pages excluded.
    −3.4 points
  • Meta descriptions55 issues
    55 of 136 pages have meta description issues. 4 noindex or canonicalized pages excluded.
    −3.1 points
  • HeadingsOK
    0 of 136 pages have heading issues. 4 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites2 issues
    2 destinations answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 21 destinations checked.
    −0.6 points
  • Redirects36 issues
    37 redirecting URLs, 10 of them chained.
    −1 points
  • Non-200 responses37 noted
    37 URLs did not return a 2xx response. 33 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.
  • Indexability2 issues
    2 of 138 indexable pages have indexability warnings. 2 pages noindex by design.
    −0.1 points
  • Image alt text49 issues
    49 of 971 image references have no alt attribute. 10 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets4 issues
    4 assets larger than 500 KB among 164 fetched assets.
    −2.4 points
  • Orphan pages19 issues
    19 pages have no internal links pointing at them.
    −0.5 points
  • Sitemap coverage57 issues
    1 sitemap listing 98 URLs: 38 crawled pages missing, 0 listed URLs broken or redirecting, 19 reachable only via the sitemap.
    −2.4 points
  • Internal link countsOK
    Internal link counts for 140 pages.
  • Thin contentOK
    0 of 136 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1688 sites, median 80%, average 79%

www.cresteyecare.com scores 87%, higher than 79% of the 1688 scanned sites. See the full ranking.

0511020%: 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%: 0 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 19 sites66%: 19 sites67%: 32 sites68%: 26 sites69%: 24 sites70%: 38 sites71%: 37 sites72%: 48 sites73%: 46 sites74%: 47 sites75%: 53 sites76%: 66 sites77%: 60 sites78%: 78 sites79%: 61 sites80%: 82 sites81%: 102 sites82%: 80 sites83%: 78 sites84%: 73 sites85%: 59 sites86%: 60 sites87%: 54 sites88%: 59 sites89%: 49 sites90%: 32 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 12 sites95%: 7 sites96%: 7 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 54 sites87% 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 website has a few issues that can be improved, including redirects, title and meta description issues, and missing sitemap coverage for several pages. Addressing these will enhance usability and SEO.

  1. 1

    Fix Redirects

    Why: 37 redirects, especially chained, can slow down page loading.

    How: Identify and eliminate unnecessary redirects, and ensure direct linking to final URLs.

    Checks: redirects

  2. 2

    Revise Title Tags

    Why: 48 pages have title tag issues; long titles hurt clarity and SEO.

    How: Ensure title tags are concise (preferably under 60 characters) and accurately reflect the page content.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 55 pages have issues with meta descriptions; they guide clicks from search results.

    How: Create unique, concise descriptions (within 160 characters) to better summarize page content.

    Checks: meta-descriptions

  4. 4

    Update Sitemap Coverage

    Why: 38 pages are missing from the sitemap; this affects their discoverability.

    How: Add these pages to your sitemap and ensure it's up-to-date.

    Checks: sitemap-coverage

  5. 5

    Add Image Alt Text

    Why: 49 images lack alt text, impacting accessibility and SEO.

    How: Add descriptive, concise alt text for all images not already using it.

    Checks: images-alt

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 issues that need addressing, including missing HTTP headers that could expose user data and allow man-in-the-middle attacks. Implementing recommended headers and restricting API keys will enhance your security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users connecting via HTTP are vulnerable to interception.

    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 can be exploited if it's not restricted.

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

    Evidence: Keys and secrets in page code

  3. 3

    Lack of Referrer PolicyLow

    Why it matters: Without a referrer-policy, users' navigation paths are unnecessarily exposed.

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

    Evidence: Referrer policy

  4. 4

    Server Version RevealedLow

    Why it matters: Revealing server information may expose known vulnerabilities to attackers.

    Fix: Modify server configuration to hide the version information, e.g., set "server_tokens off;" in Nginx.

    Evidence: Software version disclosure

  5. 5

    Third-Party Scripts without Integrity ChecksLow

    Why it matters: Using third-party scripts without subresource integrity exposes the site to potential alterations of those scripts.

    Fix: Implement a Content-Security-Policy that whitelists the domains of the third-party scripts.

    Evidence: Third-party scripts

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: The absence of a permissions policy can enable unnecessary features in the browser.

    Fix: Add the header: "Permissions-Policy: accelerometer=(), camera=(), microphone=(), geolocation=()".

    Evidence: Permissions policy

  7. 7

    Sensitive Paths in robots.txtInfo

    Why it matters: Sensitive paths listed in robots.txt can serve as a map for malicious users.

    Fix: Implement access controls for /wp-admin/ and /wp-login.php instead of relying on 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.cresteyecare.com/ → no strict-transport-security
    • https://www.cresteyecare.com/hours-location/ → no strict-transport-security
    • https://www.cresteyecare.com/hours-location/pembina/ → no strict-transport-security
    • https://www.cresteyecare.com/hours-location/regent-ave/ → no strict-transport-security
    • https://www.cresteyecare.com/our-eye-doctors/ → no strict-transport-security
    • https://www.cresteyecare.com/team/tavleen-singh/ → no strict-transport-security
    • https://www.cresteyecare.com/team/dr-louis-crust/ → no strict-transport-security
    • https://www.cresteyecare.com/team/dr-tola-opejin/ → no strict-transport-security
    • https://www.cresteyecare.com/eye-care-services/ → no strict-transport-security
    • https://www.cresteyecare.com/eye-care-services/dry-eye-disease-and-treatment/ → no strict-transport-security
    • https://www.cresteyecare.com/eyeglasses/ → no strict-transport-security
    • https://www.cresteyecare.com/eyeglasses/designer-frames/ → 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.cresteyecare.com/ → no referrer-policy
    • https://www.cresteyecare.com/hours-location/ → no referrer-policy
    • https://www.cresteyecare.com/hours-location/pembina/ → no referrer-policy
    • https://www.cresteyecare.com/hours-location/regent-ave/ → no referrer-policy
    • https://www.cresteyecare.com/our-eye-doctors/ → no referrer-policy
    • https://www.cresteyecare.com/team/tavleen-singh/ → no referrer-policy
    • https://www.cresteyecare.com/team/dr-louis-crust/ → no referrer-policy
    • https://www.cresteyecare.com/team/dr-tola-opejin/ → no referrer-policy
    • https://www.cresteyecare.com/eye-care-services/ → no referrer-policy
    • https://www.cresteyecare.com/eye-care-services/dry-eye-disease-and-treatment/ → no referrer-policy
    • https://www.cresteyecare.com/eyeglasses/ → no referrer-policy
    • https://www.cresteyecare.com/eyeglasses/designer-frames/ → 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.cresteyecare.com/ → no permissions-policy
    • https://www.cresteyecare.com/hours-location/ → no permissions-policy
    • https://www.cresteyecare.com/hours-location/pembina/ → no permissions-policy
    • https://www.cresteyecare.com/hours-location/regent-ave/ → no permissions-policy
    • https://www.cresteyecare.com/our-eye-doctors/ → no permissions-policy
    • https://www.cresteyecare.com/team/tavleen-singh/ → no permissions-policy
    • https://www.cresteyecare.com/team/dr-louis-crust/ → no permissions-policy
    • https://www.cresteyecare.com/team/dr-tola-opejin/ → no permissions-policy
    • https://www.cresteyecare.com/eye-care-services/ → no permissions-policy
    • https://www.cresteyecare.com/eye-care-services/dry-eye-disease-and-treatment/ → no permissions-policy
    • https://www.cresteyecare.com/eyeglasses/ → no permissions-policy
    • https://www.cresteyecare.com/eyeglasses/designer-frames/ → 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 (337 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.cresteyecare.com/hours-location/: 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 140 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKMixed content

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

  • OKForms over HTTPS

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

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