What your site is actually doing.

Audit of https://shreyeahhs.vercel.app/, run August 30, 2026. 13 issues were found. I want them fixed.

## Context
- Site: https://shreyeahhs.vercel.app/
- Mobile LCP (lab median): 386 ms
- Desktop LCP (lab median): 1400 ms
- Page weight (median): 0.4 MB
- Tap targets under 44px: 33% (9 of 27)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.4s 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.4 MB across 10 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.
- Accessible to most visitors: Lighthouse accessibility is 100/100, so screen-reader and contrast basics are largely handled.
- 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] A floating widget is covering a clickable element
Category: Conversion, Accessibility (WCAG)
Why it matters: 3 clickable elements are sitting underneath a fixed overlay (div.space-y-3 over a "See in 3D"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.
Exact elements found: a "See in 3D" under div.space-y-3, button "See in 3D" under div.space-y-3, a "Code" under div.text-[hsl(var(--accent))]

### 2. [HIGH] The site runs on a platform subdomain, not its own domain
Category: SEO, Conversion
Why it matters: Visitors see "shreyeahhs.vercel.app" in the address bar instead of a custom domain. It reads as unfinished, weakens brand recall and trust (especially for higher-value purchases), and splits SEO authority with the platform. Register a domain and set it as the primary so the vercel.app URL redirects to it.

### 3. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 9 of 27 tappable items on this page (33%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) 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: button 72x16 "Skip (Esc)", a 45x16 "Live", a 45x16 "Code", a 45x16 "Code", a 45x16 "Code", a 45x16 "Code", a 20x20 "GitHub", a 20x20 "LinkedIn"

### 4. [MEDIUM] Security headers are missing or weak
Category: Security
Why it matters: The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: Content-Security-Policy (the main defense against injected and cross-site scripts); clickjacking protection (X-Frame-Options or a CSP frame-ancestors rule); X-Content-Type-Options: nosniff (stops MIME-type sniffing attacks). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.

### 5. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 2 of 2 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: avatar.png "Avatar", living-ecosystem-simulator.png "Living Ecosystem Simulat"

### 6. [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 315 KiB.

### 7. [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 12 KiB.

### 8. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.

### 9. [LOW] Search-result title is leaving room on the table
Category: SEO
Why it matters: Google gives you about 60 characters of headline space in search results. This page is using 17. Adding the value proposition or a relevant keyword gives someone one more reason to click.

### 10. [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.

### 11. [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.

### 12. [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.

### 13. [LOW] Sitemap not listed in robots.txt
Why it matters: A sitemap exists but is not referenced in robots.txt. Adding a "Sitemap:" line to robots.txt helps crawlers find it reliably.

## 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://shreyeahhs.vercel.app/",
  "generated_at": "2026-08-30T03:41:15.231Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 386,
    "desktop_lcp_ms": 1400,
    "mobile_ttfb_ms": 22,
    "mobile_fcp_ms": 366,
    "page_weight_kb": 395
  },
  "finding_count": 13,
  "findings": [
    {
      "severity": "high",
      "title": "A floating widget is covering a clickable element",
      "detail": "3 clickable elements are sitting underneath a fixed overlay (div.space-y-3 over a \"See in 3D\"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)"
      ],
      "topic": "obscured_control",
      "confidence": "measured",
      "evidence": [
        "a \"See in 3D\" under div.space-y-3",
        "button \"See in 3D\" under div.space-y-3",
        "a \"Code\" under div.text-[hsl(var(--accent))]"
      ]
    },
    {
      "severity": "high",
      "title": "The site runs on a platform subdomain, not its own domain",
      "detail": "Visitors see \"shreyeahhs.vercel.app\" in the address bar instead of a custom domain. It reads as unfinished, weakens brand recall and trust (especially for higher-value purchases), and splits SEO authority with the platform. Register a domain and set it as the primary so the vercel.app URL redirects to it.",
      "device": "both",
      "tags": [
        "SEO",
        "Conversion"
      ],
      "topic": "no_custom_domain",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "9 of 27 tappable items on this page (33%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) 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": [
        "button 72x16 \"Skip (Esc)\"",
        "a 45x16 \"Live\"",
        "a 45x16 \"Code\"",
        "a 45x16 \"Code\"",
        "a 45x16 \"Code\"",
        "a 45x16 \"Code\"",
        "a 20x20 \"GitHub\"",
        "a 20x20 \"LinkedIn\""
      ]
    },
    {
      "severity": "medium",
      "title": "Security headers are missing or weak",
      "detail": "The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: Content-Security-Policy (the main defense against injected and cross-site scripts); clickjacking protection (X-Frame-Options or a CSP frame-ancestors rule); X-Content-Type-Options: nosniff (stops MIME-type sniffing attacks). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.",
      "device": "both",
      "tags": [
        "Security"
      ],
      "topic": "security_headers",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "2 of 2 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": [
        "avatar.png \"Avatar\"",
        "living-ecosystem-simulator.png \"Living Ecosystem Simulat\""
      ]
    },
    {
      "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 315 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 12 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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": "Search-result title is leaving room on the table",
      "detail": "Google gives you about 60 characters of headline space in search results. This page is using 17. Adding the value proposition or a relevant keyword gives someone one more reason to click.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "title",
      "confidence": "measured",
      "evidence": []
    },
    {
      "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 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": "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": "Sitemap not listed in robots.txt",
      "detail": "A sitemap exists but is not referenced in robots.txt. Adding a \"Sitemap:\" line to robots.txt helps crawlers find it reliably.",
      "device": "both",
      "tags": [],
      "topic": "sitemap_not_in_robots",
      "confidence": "measured",
      "evidence": []
    }
  ]
}