Scanned sites / beattyeyes.com

SEO report for beattyeyes.com DR 1

The latest Site Spider scan of beattyeyes.com, with 1 scan on record. Each scan is at its own address, for example /domain/beattyeyes-com/2026-09-12-1202.

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

Latest scan

Scanned 2026-09-12 12:02:01 UTC, finished 2026-09-12 13:01:17 UTC

Site: https://beattyeyes.com/

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

82/ 100Good

On September 12, 2026 the Site Spider crawled 28 pages and 152 assets of beattyeyes.com, starting from https://beattyeyes.com/. It scored 82 out of 100, a good result. 7 of 27 checks found something to fix, led by meta descriptions (22), headings (28), heavy assets (4); 12 checks passed. Most of the points went to meta descriptions (−6.3), headings (−6), heavy assets (−2.4). 8 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, 3 low and 1 info findings. See the security findings ↓

Pages crawled
28
Assets fetched
152
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

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

  • Title tags4 issues
    4 of 28 pages have title issues.
    −1.4 points
  • Meta descriptions22 issues
    22 of 28 pages have meta description issues.
    −6.3 points
  • Headings28 issues
    28 of 28 pages have heading issues.
    −6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites58 noted
    0 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 13 destinations checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 0 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.
  • IndexabilityOK
    0 of 28 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 174 image references have no alt attribute. 28 use an empty alt (decorative), which is fine.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 152 fetched assets.
    −2.4 points
  • Orphan pages4 issues
    4 pages have no internal links pointing at them.
    −0.6 points
  • Sitemap coverage5 issues
    4 sitemaps listing 27 URLs: 1 crawled page missing, 0 listed URLs broken or redirecting, 4 reachable only via the sitemap.
    −1.1 points
  • Internal link counts4 noted
    Internal link counts for 28 pages; 4 worth a look.
  • Thin content1 issue
    1 of 28 pages have fewer than 200 words.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 28 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 28 pages have a canonical worth checking.
  • Robots directives28 noted
    28 pages carry a robots directive; 0 carry none.
  • Anchor text5 noted
    5 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure28 noted
    28 of 28 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • 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 28 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; 12 response headers recorded across 180 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 28 pages; 0 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 64 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 site sits among all scanned sites

2873 sites, median 80%, average 79%

beattyeyes.com scores 82%, higher than 56% of the 2873 scanned sites. See the full ranking.

0751500%: 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%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites82% 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 that need attention, particularly with redirects, titles, and meta descriptions. Addressing these will improve SEO and user experience significantly.

  1. 1

    Fix Redirects

    Why: One redirecting URL may confuse search engines and users.

    How: Ensure 'https://beattyeyes.com/sitemap.xml' directly links to its intended destination without a redirect.

    Checks: redirects

  2. 2

    Resolve Non-200 Response

    Why: A non-200 response can affect user access and SEO rankings.

    How: Check 'https://beattyeyes.com/sitemap.xml' for proper setup; correct any underlying issue to ensure it consistently returns a 2xx response.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Titles help in ranking and click-through rate; duplicates and length issues dilute their effectiveness.

    How: Revise duplicate titles for 'Services' category and shorten overly long titles to 60 characters or less.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Meta descriptions influence search visibility and clicks; fixing missing or duplicated descriptions is crucial.

    How: Create unique meta descriptions for missing entries, limit duplicates, and ensure they are under 160 characters.

    Checks: meta-descriptions

  5. 5

    Fix Heading Structure

    Why: Proper headings are crucial for SEO and accessibility; multiple H1s can confuse search engines.

    How: Limit each page to a single H1; use H2s for subsection titles where necessary.

    Checks: headings

  6. 6

    Link Orphan Pages Internally

    Why: Orphan pages are not accessible, which can hinder user experience and SEO.

    How: Add internal links to 'Coming Soon', 'Our Office', 'Request a Consultation', and 'Thank You' pages from relevant pages.

    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 beattyeyes.com has several security vulnerabilities, primarily lacking crucial HTTP headers. Implementing HTTP Strict Transport Security (HSTS), Content Security Policy (CSP), and X-Frame-Options is essential to enhance protection against various attacks. Addressing server version disclosure and MIME type issues will further strengthen security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the domain without HTTPS can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP means the browser can load scripts and resources from any source, risking XSS.

    Fix: Add the header: Content-Security-Policy: default-src 'self'; script-src 'self' https:; frame-ancestors 'none'

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site is vulnerable to clickjacking attacks.

    Fix: Add the header: X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: The absence of this header can lead to MIME sniffing vulnerabilities.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  5. 5

    Exposed Server VersionLow

    Why it matters: Revealing server version can help attackers identify vulnerabilities.

    Fix: Consider hiding the server version in responses or upgrading to Pagely-ARES/1.22.29 or higher.

    Evidence: Software version disclosure

  6. 6

    Lack of Subresource Integrity for Third-party ScriptsLow

    Why it matters: Risk of third-party script compromise affects site behavior.

    Fix: Implement a Content-Security-Policy that includes trusted domains or utilize Subresource Integrity for script tags.

    Evidence: Third-party scripts

  7. 7

    Sensitive Paths in robots.txtInfo

    Why it matters: Exposing private paths in robots.txt can guide attackers.

    Fix: Restrict access to /wp-admin/ using proper authentication measures.

    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://beattyeyes.com/ → no strict-transport-security
    • https://beattyeyes.com/about-us/ → no strict-transport-security
    • https://beattyeyes.com/meet-the-team/ → no strict-transport-security
    • https://beattyeyes.com/category/services/adults/ → no strict-transport-security
    • https://beattyeyes.com/contacts/ → no strict-transport-security
    • https://beattyeyes.com/glasses/ → no strict-transport-security
    • https://beattyeyes.com/beatty-eyes-exam/ → no strict-transport-security
    • https://beattyeyes.com/category/services/children/ → no strict-transport-security
    • https://beattyeyes.com/childrens-contact-lenses/ → no strict-transport-security
    • https://beattyeyes.com/childrens-glasses/ → no strict-transport-security
    • https://beattyeyes.com/childrens-eye-care/ → no strict-transport-security
    • https://beattyeyes.com/dry-eye/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 28 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://beattyeyes.com/ → no content-security-policy
    • https://beattyeyes.com/about-us/ → no content-security-policy
    • https://beattyeyes.com/meet-the-team/ → no content-security-policy
    • https://beattyeyes.com/category/services/adults/ → no content-security-policy
    • https://beattyeyes.com/contacts/ → no content-security-policy
    • https://beattyeyes.com/glasses/ → no content-security-policy
    • https://beattyeyes.com/beatty-eyes-exam/ → no content-security-policy
    • https://beattyeyes.com/category/services/children/ → no content-security-policy
    • https://beattyeyes.com/childrens-contact-lenses/ → no content-security-policy
    • https://beattyeyes.com/childrens-glasses/ → no content-security-policy
    • https://beattyeyes.com/childrens-eye-care/ → no content-security-policy
    • https://beattyeyes.com/dry-eye/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://beattyeyes.com/ → no x-frame-options
    • https://beattyeyes.com/about-us/ → no x-frame-options
    • https://beattyeyes.com/meet-the-team/ → no x-frame-options
    • https://beattyeyes.com/category/services/adults/ → no x-frame-options
    • https://beattyeyes.com/contacts/ → no x-frame-options
    • https://beattyeyes.com/glasses/ → no x-frame-options
    • https://beattyeyes.com/beatty-eyes-exam/ → no x-frame-options
    • https://beattyeyes.com/category/services/children/ → no x-frame-options
    • https://beattyeyes.com/childrens-contact-lenses/ → no x-frame-options
    • https://beattyeyes.com/childrens-glasses/ → no x-frame-options
    • https://beattyeyes.com/childrens-eye-care/ → no x-frame-options
    • https://beattyeyes.com/dry-eye/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://beattyeyes.com/ → no x-content-type-options
    • https://beattyeyes.com/about-us/ → no x-content-type-options
    • https://beattyeyes.com/meet-the-team/ → no x-content-type-options
    • https://beattyeyes.com/category/services/adults/ → no x-content-type-options
    • https://beattyeyes.com/contacts/ → no x-content-type-options
    • https://beattyeyes.com/glasses/ → no x-content-type-options
    • https://beattyeyes.com/beatty-eyes-exam/ → no x-content-type-options
    • https://beattyeyes.com/category/services/children/ → no x-content-type-options
    • https://beattyeyes.com/childrens-contact-lenses/ → no x-content-type-options
    • https://beattyeyes.com/childrens-glasses/ → no x-content-type-options
    • https://beattyeyes.com/childrens-eye-care/ → no x-content-type-options
    • https://beattyeyes.com/dry-eye/ → no x-content-type-options
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Pagely-ARES/1.22.28 (180 responses)
  • NoteThird-party scripts

    Scripts run from 4 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.)

    • s33929.pcdn.co (399 script tags)
    • www.googletagmanager.com (56 script tags)
    • www.google.com (3 script tags)
    • kit.fontawesome.com (28 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path 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/
6 checks passed, 3 not applicable
  • OKHTTPS

    All 28 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • 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.

Earlier scans of beattyeyes.com

No other scans of this site yet.

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

Own beattyeyes.com?