What your site is actually doing.

Audit of https://vibhinngautam.com/, run August 11, 2026. 15 issues were found. I want them fixed.

## Context
- Site: https://vibhinngautam.com/
- Mobile LCP (lab median): 142 ms
- Desktop LCP (lab median): 132 ms
- Page weight (median): 0.0 MB
- Tap targets under 44px: 0% (0 of 0)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: Google Lighthouse scores this page 97/100 for performance on mobile. Loading is not what is costing you visitors here.
- Light page weight: The page is about 0.0 MB across 6 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 91/100. The fundamentals Google looks for are present.
- Accessible to most visitors: Lighthouse accessibility is 95/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. [MEDIUM] Google is writing your search snippet for you
Category: SEO
Why it matters: This page has no meta description, so Google grabs whatever text it finds on the page and shows that under your title in search results. Usually it's not the pitch you'd write yourself. Adding a 120 to 160 character summary is one of the easier wins for search click-through.

### 2. [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); HSTS (Strict-Transport-Security, which forces HTTPS on return visits). 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.

### 3. [MEDIUM] The page has no main heading
Why it matters: There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.

### 4. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 1 of 1 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: me-Sr8iyQUU.png "Profile Icon"

### 5. [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 5. Adding the value proposition or a relevant keyword gives someone one more reason to click.

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

### 7. [LOW] Links to this page will look bare when shared
Why it matters: The page is missing its Open Graph title and image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no title and image. A flat grey link gets far fewer clicks than one with an image and headline.

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

### 9. [LOW] There is very little text on this page
Why it matters: The page has about 10 words. Thin pages give Google little to rank on and visitors little to act on. If this is a key landing page, it usually needs more substance.

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

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

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

### 14. [LOW] No robots.txt file
Why it matters: No /robots.txt. Search engines check it first for crawl rules and your sitemap location. Without one, crawlers fall back to defaults and may miss your sitemap.

### 15. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your 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://vibhinngautam.com/",
  "generated_at": "2026-08-21T19:25:49.528Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 142,
    "desktop_lcp_ms": 132,
    "mobile_ttfb_ms": 25,
    "mobile_fcp_ms": 120,
    "page_weight_kb": 33
  },
  "finding_count": 15,
  "findings": [
    {
      "severity": "medium",
      "title": "Google is writing your search snippet for you",
      "detail": "This page has no meta description, so Google grabs whatever text it finds on the page and shows that under your title in search results. Usually it's not the pitch you'd write yourself. Adding a 120 to 160 character summary is one of the easier wins for search click-through.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "meta_description",
      "confidence": "measured",
      "evidence": []
    },
    {
      "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); HSTS (Strict-Transport-Security, which forces HTTPS on return visits). 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": "medium",
      "title": "The page has no main heading",
      "detail": "There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.",
      "device": "both",
      "tags": [],
      "topic": "h1",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "1 of 1 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": [
        "me-Sr8iyQUU.png \"Profile Icon\""
      ]
    },
    {
      "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 5. 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 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": "Links to this page will look bare when shared",
      "detail": "The page is missing its Open Graph title and image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no title and image. A flat grey link gets far fewer clicks than one with an image and headline.",
      "device": "both",
      "tags": [],
      "topic": "og_tags",
      "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": "There is very little text on this page",
      "detail": "The page has about 10 words. Thin pages give Google little to rank on and visitors little to act on. If this is a key landing page, it usually needs more substance.",
      "device": "both",
      "tags": [],
      "topic": "thin_content",
      "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 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 96 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No robots.txt file",
      "detail": "No /robots.txt. Search engines check it first for crawl rules and your sitemap location. Without one, crawlers fall back to defaults and may miss your sitemap.",
      "device": "both",
      "tags": [],
      "topic": "robots_txt_missing",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No llms.txt file",
      "detail": "No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_llms_txt",
      "confidence": "measured",
      "evidence": []
    }
  ]
}