Scanned sites / www.drwylie.com / 2026-10-01-1553

www.drwylie.com scan from 10/1/2026, 3:53:54 PM

Scan 2026-10-01-1553

Scanned 10/1/2026, 3:53:54 PM, finished 10/1/2026, 6:39:50 PM. Found on page 3 of brave web search results

Site: https://www.drwylie.com/

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

86/ 100Good

On October 1, 2026 the Site Spider crawled 350 pages and 153 assets of www.drwylie.com, starting from https://www.drwylie.com/. It scored 86 out of 100, a good result. 9 of 16 checks found something to fix, led by title tags (131), sitemap coverage (197), meta descriptions (111); 5 checks passed. Most of the points went to title tags (−4.1), sitemap coverage (−3.7), meta descriptions (−2.7). 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: Medium3 medium, 3 low and 2 info findings. See the security findings ↓

Pages crawled
350
Assets fetched
153
Status
Completed
Checks with issues
9 of 16
CoverageComplete crawl

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

  • Title tags131 issues
    131 of 285 pages have title issues. 38 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions111 issues
    111 of 285 pages have meta description issues. 38 noindex or canonicalized pages excluded.
    −2.7 points
  • HeadingsOK
    0 of 285 pages have heading issues. 38 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites6 issues
    6 destinations answered with an error, 38 could not be determined (timeouts, rate limits or refusals), of 99 destinations checked.
    −0.8 points
  • Redirects28 issues
    31 redirecting URLs, 5 of them chained.
    −0.3 points
  • Non-200 responses31 noted
    31 URLs did not return a 2xx response. 27 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.
  • Indexability12 issues
    12 of 302 indexable pages have indexability warnings. 21 pages noindex by design.
    −0.4 points
  • Image alt text1 issue
    1 of 1842 image references have no alt attribute. 25 use an empty alt (decorative), which is fine.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 153 fetched assets.
    −2.4 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage197 issues
    1 sitemap listing 96 URLs: 193 crawled pages missing, 3 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −3.7 points
  • Internal link countsOK
    Internal link counts for 323 pages.
  • Thin contentOK
    0 of 285 pages have fewer than 200 words. 38 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1596 sites, median 80%, average 79%

www.drwylie.com scores 86%, higher than 75% of the 1596 scanned sites. See the full ranking.

049980%: 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%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 6 sites55%: 3 sites56%: 5 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 17 sites66%: 18 sites67%: 30 sites68%: 25 sites69%: 22 sites70%: 34 sites71%: 35 sites72%: 47 sites73%: 37 sites74%: 46 sites75%: 53 sites76%: 58 sites77%: 55 sites78%: 72 sites79%: 56 sites80%: 78 sites81%: 98 sites82%: 78 sites83%: 77 sites84%: 70 sites85%: 54 sites86%: 57 sites87%: 52 sites88%: 56 sites89%: 46 sites90%: 31 sites91%: 34 sites92%: 21 sites93%: 10 sites94%: 13 sites95%: 7 sites96%: 6 sites97%: 6 sites98%: 1 site99%: 2 sites100%: 53 sites86% 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 requires attention on several SEO aspects to enhance performance. Prioritize fixing redirects, non-200 responses, and title and meta description issues for better indexability.

  1. 1

    Fix Redirects and Non-200 Responses

    Why: Improving these enhances user experience and crawl efficiency.

    How: Identify and eliminate unnecessary redirects, especially chains; ensure URLs return a 2xx status.

    Checks: redirects, status-codes

  2. 2

    Update Title Tags

    Why: Correcting title issues improves click-through rates from search results.

    How: Revise the 131 pages with title issues to fit length and relevance criteria.

    Checks: titles

  3. 3

    Enhance Meta Descriptions

    Why: Optimizing meta descriptions can increase visibility and click rates.

    How: Create and refine descriptions for 111 pages with issues; aim for compelling summaries under 160 characters.

    Checks: meta-descriptions

  4. 4

    Revise Sitemap Coverage

    Why: A complete sitemap ensures all important pages are indexed properly.

    How: Add the 193 pages missing from the sitemap; resolve any broken or redirecting sitemap URLs.

    Checks: sitemap-coverage

  5. 5

    Improve Indexability

    Why: Addressing indexability warnings ensures critical pages can be indexed by search engines.

    How: Review the 12 pages with indexability warnings and adjust canonical or robots settings as needed.

    Checks: indexability

  6. 6

    Fix Orphan Pages

    Why: Linking orphan pages increases their discoverability and SEO value.

    How: Create internal links to the single orphan page to make it accessible from other relevant content.

    Checks: orphan-pages

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 has vulnerabilities in its JavaScript library and exposed credentials. Implementing recommended fixes will enhance security, limit possible information leakage, and mitigate potential attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users are at risk of interception on their first request while typing the URL without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Outdated JavaScript Library with VulnerabilitiesMedium

    Why it matters: The use of jQuery 2.9.2 exposes the site to multiple known security vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or newer to avoid these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Exposed Google API KeyMedium

    Why it matters: The Google API key found in the code can be abused by anyone who sees the page, leading to unauthorized use.

    Fix: Restrict the API key in the Google Cloud console by HTTP referrer and consider additional security measures.

    Evidence: Keys and secrets in page code

  4. 4

    Missing Referrer PolicyLow

    Why it matters: Not using a Referrer Policy can expose users’ full URLs to third-party sites.

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

    Evidence: Referrer policy

  5. 5

    Revealing Server BannerLow

    Why it matters: Disclosing the server version aids attackers in identifying vulnerabilities.

    Fix: Remove or obscure server information in the header. Consider setting: Server: [Obscured Name].

    Evidence: Software version disclosure

  6. 6

    Mixed Content IssuesLow

    Why it matters: Resources are being loaded over HTTP on HTTPS pages, which can lead to man-in-the-middle attacks.

    Fix: Update the URLs to load all resources over HTTPS.

    Evidence: Mixed content

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: A missing Permissions-Policy allows vulnerable scripts more access to browser features.

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

    Evidence: Permissions policy

  8. 8

    Potentially Sensitive Paths in robots.txtInfo

    Why it matters: Listing private paths in robots.txt can provide a roadmap for attackers without access control.

    Fix: Apply proper access control to these paths 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.drwylie.com/ → no strict-transport-security
    • https://www.drwylie.com/our-eye-doctors/ → no strict-transport-security
    • https://www.drwylie.com/the-staff/ → no strict-transport-security
    • https://www.drwylie.com/contact-us/testimonials/ → no strict-transport-security
    • https://www.drwylie.com/insurance/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/vision-therapy-quiz/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/why-a-functional-vision-exam-matters/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/yoked-prisms-your-visual-system/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/amblyopia/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/add-adhd-and-vision-therapy/ → no strict-transport-security
    • https://www.drwylie.com/vision-therapy-optometrist/vision-problems-and-autism/ → 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.drwylie.com/ → no referrer-policy
    • https://www.drwylie.com/our-eye-doctors/ → no referrer-policy
    • https://www.drwylie.com/the-staff/ → no referrer-policy
    • https://www.drwylie.com/contact-us/testimonials/ → no referrer-policy
    • https://www.drwylie.com/insurance/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/vision-therapy-quiz/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/why-a-functional-vision-exam-matters/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/yoked-prisms-your-visual-system/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/amblyopia/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/add-adhd-and-vision-therapy/ → no referrer-policy
    • https://www.drwylie.com/vision-therapy-optometrist/vision-problems-and-autism/ → 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.drwylie.com/ → no permissions-policy
    • https://www.drwylie.com/our-eye-doctors/ → no permissions-policy
    • https://www.drwylie.com/the-staff/ → no permissions-policy
    • https://www.drwylie.com/contact-us/testimonials/ → no permissions-policy
    • https://www.drwylie.com/insurance/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/vision-therapy-quiz/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/why-a-functional-vision-exam-matters/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/yoked-prisms-your-visual-system/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/amblyopia/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/add-adhd-and-vision-therapy/ → no permissions-policy
    • https://www.drwylie.com/vision-therapy-optometrist/vision-problems-and-autism/ → 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 (503 responses)
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://www.drwylie.com/vision-therapy-optometrist/vision-therapy-qui… loads image http://assets.markallengroup.com/article-images/image-library/147/patternglare4.jpg
    • https://www.drwylie.com/vision-therapy-optometrist/vision-therapy-qui… loads image http://assets.markallengroup.com/article-images/image-library/147/patternglare4.jpg
  • 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.drwylie.com/wp-content/plugins/gravityforms/js/placeholders.jquery.…: 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.drwylie.com/contact-us/testimonials/: 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 1 other domain 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)
  • 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
6 checks passed, 1 not applicable
  • OKHTTPS

    All 323 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKForms over HTTPS

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

Own www.drwylie.com?

www.drwylie.com scan 2026-10-01-1553 | DIY SEO Hub