What your site is actually doing.

Audit of https://mihirnaik.com/, run August 19, 2026. 14 issues were found. I want them fixed.

## Context
- Site: https://mihirnaik.com/
- Mobile LCP (lab median): 984 ms
- Desktop LCP (lab median): 1024 ms
- Page weight (median): 0.0 MB
- Tap targets under 44px: 18% (12 of 65)
- Evidence base: 6 mobile + 3 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 1.0s 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.0 MB across 96 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- 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] JavaScript errors were logged during load
Category: Conversion, Tracking
Why it matters: Errors in the console often mean a feature silently broke: a button that does nothing, analytics that did not fire, a form that will not submit.

### 2. [HIGH] Add quotations so AI engines cite this page
Category: AI Search, SEO
Why it matters: Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

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

### 4. [MEDIUM] 5 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: "Resources" (span.header-nav-link), "Services" (span.header-nav-link), "Projects" (span.header-nav-link).
Exact elements found: "Resources" (span.header-nav-link), "Services" (span.header-nav-link), "Projects" (span.header-nav-link), "Perplexity" (div.hero-rotator-pill), "Share your challenge and we'll see if we're a fi" (div.ant-typography)

### 5. [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); 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.

### 6. [MEDIUM] 5 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: "Resources" (span.header-nav-link) (div/span used as a button, no role), "Services" (span.header-nav-link) (div/span used as a button, no role), "Projects" (span.header-nav-link) (div/span used as a button, no role), "Perplexity" (div.hero-rotator-pill) (div/span used as a button, no role), "Share your challenge and we'll see if we" (div.ant-typography) (div/span used as a button, no role)

### 7. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 46 of 72 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: perplexity.svg, airnewzealand.svg "Air New Zealand", att.svg "AT&T", bbc.svg "BBC", capgemini.svg "Capgemini", clickup.svg "ClickUp"

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

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

### 10. [LOW] Search-result title will be cut off
Category: SEO
Why it matters: The title is 74 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped.

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

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

### 13. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.

### 14. [LOW] Headings skip levels
Category: Accessibility (WCAG)
Why it matters: Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on.

## 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://mihirnaik.com/",
  "generated_at": "2026-08-21T19:25:47.787Z",
  "evidence_base": {
    "mobile_loads": 6,
    "desktop_loads": 3,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 984,
    "desktop_lcp_ms": 1024,
    "mobile_ttfb_ms": 589,
    "mobile_fcp_ms": 984,
    "page_weight_kb": 23
  },
  "finding_count": 14,
  "findings": [
    {
      "severity": "high",
      "title": "JavaScript errors were logged during load",
      "detail": "Errors in the console often mean a feature silently broke: a button that does nothing, analytics that did not fire, a form that will not submit.",
      "device": "both",
      "tags": [
        "Conversion",
        "Tracking"
      ],
      "topic": "js_errors",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Add quotations so AI engines cite this page",
      "detail": "Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (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": "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": "medium",
      "title": "5 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: \"Resources\" (span.header-nav-link), \"Services\" (span.header-nav-link), \"Projects\" (span.header-nav-link).",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "dead_clicks",
      "confidence": "measured",
      "evidence": [
        "\"Resources\" (span.header-nav-link)",
        "\"Services\" (span.header-nav-link)",
        "\"Projects\" (span.header-nav-link)",
        "\"Perplexity\" (div.hero-rotator-pill)",
        "\"Share your challenge and we'll see if we're a fi\" (div.ant-typography)"
      ]
    },
    {
      "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); 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": "medium",
      "title": "5 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": [
        "\"Resources\" (span.header-nav-link) (div/span used as a button, no role)",
        "\"Services\" (span.header-nav-link) (div/span used as a button, no role)",
        "\"Projects\" (span.header-nav-link) (div/span used as a button, no role)",
        "\"Perplexity\" (div.hero-rotator-pill) (div/span used as a button, no role)",
        "\"Share your challenge and we'll see if we\" (div.ant-typography) (div/span used as a button, no role)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "46 of 72 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": [
        "perplexity.svg",
        "airnewzealand.svg \"Air New Zealand\"",
        "att.svg \"AT&T\"",
        "bbc.svg \"BBC\"",
        "capgemini.svg \"Capgemini\"",
        "clickup.svg \"ClickUp\""
      ]
    },
    {
      "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 85 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 31 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Search-result title will be cut off",
      "detail": "The title is 74 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped.",
      "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 llms.txt file",
      "detail": "No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_llms_txt",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Headings skip levels",
      "detail": "Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    }
  ]
}