What your site is actually doing.

Audit of https://nexusats.shop/, run August 8, 2026. 20 issues were found. I want them fixed.

## Context
- Site: https://nexusats.shop/
- Mobile LCP (lab median): 516 ms
- Desktop LCP (lab median): 496 ms
- Page weight (median): 0.5 MB
- Tap targets under 44px: 45% (18 of 40)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.5s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- Light page weight: The page is about 0.5 MB across 35 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- Search basics are in place: Lighthouse scores SEO 100/100. The fundamentals Google looks for are present.
- Layout holds on phone and desktop: Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

## Issues, most damaging first

### 1. [HIGH] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 18 of 40 tappable items on this page (45%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.
Exact elements found: a 117x20 "NexusATS", a 79x22 "How It Works", a 42x22 "Pricing", a 25x22 "FAQ", a 46x22 "Discord", a 34x22 "Login", a 38x22 "Terms", a 45x22 "Privacy"

### 2. [HIGH] Some text is low-contrast and hard to read
Category: Accessibility (WCAG)
Why it matters: Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.

### 3. [HIGH] Broken internal links
Category: SEO, Conversion
Why it matters: 1 internal link target returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)
Exact examples found: https://nexusats.shop/cdn-cgi/l/email-protection (404)

### 4. [MEDIUM] 1 form field has no label
Category: Accessibility (WCAG), Conversion, Tracking
Why it matters: Screen readers can't announce these fields, and a sighted user who clears the placeholder can't recover the prompt. Wrap each input in <label>…</label> or add aria-label.
Exact elements found: (input) placeholder="Coupon code"

### 5. [MEDIUM] Expose a last-updated date (freshness)
Category: AI Search, SEO
Why it matters: ChatGPT cites recently-updated pages roughly 76% of the time and passes over stale, undated ones. These pages expose no machine-readable dateModified. Refresh the content and add dateModified (Article schema / meta). (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

### 6. [MEDIUM] AI search crawlers are blocked
Category: SEO
Why it matters: Your robots.txt blocks 8 AI crawlers (gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.
Exact examples found: gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent

### 7. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 38 of 38 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.
Exact elements found: nexuslogo_trans.png, nexuslogo_trans.png "NexusATS", nexuslogo_trans.png "NexusATS", nexuslogo_trans.png "NexusATS", nexuslogo_trans.png "NexusATS", nexuslogo_trans.png "NexusATS"

### 8. [LOW] No canonical tag, so duplicate URLs split the page's ranking
Why it matters: When the same content is reachable at multiple URLs (think tracking parameters or session IDs), Google can split your ranking signal across them. A single canonical tag tells Google which version counts.

### 9. [LOW] Some text is too small to read on phones
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 25 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.
How we know: median across loads

### 10. [LOW] The page has 2 top-level headings
Why it matters: Multiple <h1> tags blur which heading is the main one. Keep one H1 and demote the rest to H2 so the page's structure is clear.

### 11. [LOW] No structured data for rich search results
Why it matters: The page has no schema.org markup. Adding the right type (Product, Article, Organization, FAQ) lets Google show rich results like star ratings and prices, which lift click-through for free.

### 12. [LOW] 4 potential dead-click targets
Category: Conversion, Accessibility (WCAG), Tracking
Why it matters: Elements styled like buttons but with no anchor, no <button> wrapper, no role="button", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: "1 · Product" (div.step-pill), "2 · Billing" (div.step-pill), "3 · Payment" (div.step-pill).
Exact elements found: "1 · Product" (div.step-pill), "2 · Billing" (div.step-pill), "3 · Payment" (div.step-pill), "Monthly Access" (span.summary-plan-pill)

### 13. [LOW] 2 form fields missing autocomplete hint
Category: Conversion, Accessibility (WCAG)
Why it matters: Browsers can autofill name, email, phone, address from the user's saved profile only when you tell them which field is which via autocomplete="email", autocomplete="name", etc. Faster checkout, fewer typos.
Exact elements found: (type=email), (type=email)

### 14. [LOW] 4 interactive elements have no stable, accessible identity
Category: Accessibility (WCAG), Tracking
Why it matters: These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.
Exact elements found: "1 · Product" (div.step-pill) (div/span used as a button, no role), "2 · Billing" (div.step-pill) (div/span used as a button, no role), "3 · Payment" (div.step-pill) (div/span used as a button, no role), "Monthly Access" (span.summary-plan-pill) (div/span used as a button, no role)

### 15. [LOW] No third-party analytics tag detected
Category: Tracking
Why it matters: No Google Analytics, GA4, or other third-party analytics tag was found in the page. If you rely only on platform or server-side analytics that is fine; but if not, a third-party tag is the baseline way to see how many visitors arrive, where they come from, and what converts. First-party or server-side analytics are not detectable from the outside, so this may already be handled.

### 16. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.

### 17. [LOW] No visible contact details (email or phone)
Category: Conversion
Why it matters: The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer.

### 18. [LOW] Unused JavaScript is being downloaded
Category: Performance
Why it matters: Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 113 KiB.

### 19. [LOW] Unused CSS is being downloaded
Category: Performance
Why it matters: Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 18 KiB.

### 20. [LOW] No Organization or WebSite schema
Category: SEO
Why it matters: No site-wide Organization or WebSite structured data found on any crawled page. This is the schema that tells Google and AI engines who you are (name, logo, social profiles) for the knowledge panel and brand recognition in AI answers. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

## How to respond
Work through the issues in order. For each one give me the specific change that fixes it: real code or real copy, not advice. Keep changes minimal and match the existing style of the site.
Where several issues share one root cause, say so and fix it once rather than patching each symptom.
If an issue cannot be fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.

{
  "generated_by": "Harvv",
  "report_url": "https://nexusats.shop/",
  "generated_at": "2026-08-21T19:25:51.407Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 516,
    "desktop_lcp_ms": 496,
    "mobile_ttfb_ms": 62,
    "mobile_fcp_ms": 500,
    "page_weight_kb": 518
  },
  "finding_count": 20,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "18 of 40 tappable items on this page (45%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tap_targets",
      "confidence": "measured",
      "evidence": [
        "a 117x20 \"NexusATS\"",
        "a 79x22 \"How It Works\"",
        "a 42x22 \"Pricing\"",
        "a 25x22 \"FAQ\"",
        "a 46x22 \"Discord\"",
        "a 34x22 \"Login\"",
        "a 38x22 \"Terms\"",
        "a 45x22 \"Privacy\""
      ]
    },
    {
      "severity": "high",
      "title": "Some text is low-contrast and hard to read",
      "detail": "Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "contrast",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Broken internal links",
      "detail": "1 internal link target returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "SEO",
        "Conversion"
      ],
      "topic": "broken_internal_links",
      "confidence": "measured",
      "evidence": [
        "https://nexusats.shop/cdn-cgi/l/email-protection (404)"
      ]
    },
    {
      "severity": "medium",
      "title": "1 form field has no label",
      "detail": "Screen readers can't announce these fields, and a sighted user who clears the placeholder can't recover the prompt. Wrap each input in <label>…</label> or add aria-label.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion",
        "Tracking"
      ],
      "topic": "form_labels",
      "confidence": "measured",
      "evidence": [
        "(input) placeholder=\"Coupon code\""
      ]
    },
    {
      "severity": "medium",
      "title": "Expose a last-updated date (freshness)",
      "detail": "ChatGPT cites recently-updated pages roughly 76% of the time and passes over stale, undated ones. These pages expose no machine-readable dateModified. Refresh the content and add dateModified (Article schema / meta). (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "AI Search",
        "SEO"
      ],
      "topic": "geo",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "AI search crawlers are blocked",
      "detail": "Your robots.txt blocks 8 AI crawlers (gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "ai_crawler_blocked",
      "confidence": "measured",
      "evidence": [
        "gptbot",
        "google-extended",
        "claudebot",
        "ccbot",
        "bytespider",
        "applebot-extended",
        "amazonbot",
        "meta-externalagent"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "38 of 38 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.",
      "device": "both",
      "tags": [
        "Performance",
        "SEO"
      ],
      "topic": "image_dims",
      "confidence": "measured",
      "evidence": [
        "nexuslogo_trans.png",
        "nexuslogo_trans.png \"NexusATS\"",
        "nexuslogo_trans.png \"NexusATS\"",
        "nexuslogo_trans.png \"NexusATS\"",
        "nexuslogo_trans.png \"NexusATS\"",
        "nexuslogo_trans.png \"NexusATS\""
      ]
    },
    {
      "severity": "low",
      "title": "No canonical tag, so duplicate URLs split the page's ranking",
      "detail": "When the same content is reachable at multiple URLs (think tracking parameters or session IDs), Google can split your ranking signal across them. A single canonical tag tells Google which version counts.",
      "device": "both",
      "tags": [],
      "topic": "canonical",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Some text is too small to read on phones",
      "detail": "25 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tiny_text",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page has 2 top-level headings",
      "detail": "Multiple <h1> tags blur which heading is the main one. Keep one H1 and demote the rest to H2 so the page's structure is clear.",
      "device": "both",
      "tags": [],
      "topic": "h1",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No structured data for rich search results",
      "detail": "The page has no schema.org markup. Adding the right type (Product, Article, Organization, FAQ) lets Google show rich results like star ratings and prices, which lift click-through for free.",
      "device": "both",
      "tags": [],
      "topic": "schema",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "4 potential dead-click targets",
      "detail": "Elements styled like buttons but with no anchor, no <button> wrapper, no role=\"button\", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: \"1 · Product\" (div.step-pill), \"2 · Billing\" (div.step-pill), \"3 · Payment\" (div.step-pill).",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "dead_clicks",
      "confidence": "measured",
      "evidence": [
        "\"1 · Product\" (div.step-pill)",
        "\"2 · Billing\" (div.step-pill)",
        "\"3 · Payment\" (div.step-pill)",
        "\"Monthly Access\" (span.summary-plan-pill)"
      ]
    },
    {
      "severity": "low",
      "title": "2 form fields missing autocomplete hint",
      "detail": "Browsers can autofill name, email, phone, address from the user's saved profile only when you tell them which field is which via autocomplete=\"email\", autocomplete=\"name\", etc. Faster checkout, fewer typos.",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)"
      ],
      "topic": "form_autocomplete",
      "confidence": "measured",
      "evidence": [
        "(type=email)",
        "(type=email)"
      ]
    },
    {
      "severity": "low",
      "title": "4 interactive elements have no stable, accessible identity",
      "detail": "These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "untrackable_elements",
      "confidence": "measured",
      "evidence": [
        "\"1 · Product\" (div.step-pill) (div/span used as a button, no role)",
        "\"2 · Billing\" (div.step-pill) (div/span used as a button, no role)",
        "\"3 · Payment\" (div.step-pill) (div/span used as a button, no role)",
        "\"Monthly Access\" (span.summary-plan-pill) (div/span used as a button, no role)"
      ]
    },
    {
      "severity": "low",
      "title": "No third-party analytics tag detected",
      "detail": "No Google Analytics, GA4, or other third-party analytics tag was found in the page. If you rely only on platform or server-side analytics that is fine; but if not, a third-party tag is the baseline way to see how many visitors arrive, where they come from, and what converts. First-party or server-side analytics are not detectable from the outside, so this may already be handled.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "no_analytics",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_email_capture",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No visible contact details (email or phone)",
      "detail": "The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_contact",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused JavaScript is being downloaded",
      "detail": "Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 113 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused CSS is being downloaded",
      "detail": "Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 18 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No Organization or WebSite schema",
      "detail": "No site-wide Organization or WebSite structured data found on any crawled page. This is the schema that tells Google and AI engines who you are (name, logo, social profiles) for the knowledge panel and brand recognition in AI answers. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_org_schema",
      "confidence": "measured",
      "evidence": []
    }
  ]
}