What your site is actually doing.

Audit of https://austincapitalmortgage.com/, run August 31, 2026. 12 issues were found. I want them fixed.

## Context
- Site: https://austincapitalmortgage.com/
- Mobile LCP (lab median): 168 ms
- Desktop LCP (lab median): 264 ms
- Page weight (median): 2.2 MB
- Tap targets under 44px: 54% (28 of 52)
- Evidence base: 4 mobile + 1 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: The main content paints in about 0.2s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- Layout stays put as it loads: Real visitors see only 0.00 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- 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: 28 of 52 tappable items on this page (54%) 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: a 20x10 "Skip to main content", a 20x10 "Skip to footer", button 20x16 "Open mobile menu", button 16x48 "Purchase Sub menu", button 16x48 "Refinance Sub menu", button 16x48 "Resources Sub menu", button 16x48 "About Sub menu", a 188x15 (no visible label)

### 2. [HIGH] Some links cannot be followed by Google
Category: SEO
Why it matters: Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.

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

### 4. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 2.2 megabytes, roughly 2189 KB of images and 0 KB of JavaScript across 33 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.
How we know: median across loads

### 5. [MEDIUM] Main content is slow to appear on phones
Why it matters: For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 3.6 seconds to show up. Google's "good" threshold is 2.5 seconds, and this misses it. That number is also one of the signals Google uses to decide where to rank your page in search.
How we know: real-user field data

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

### 7. [LOW] No advertising pixel detected
Category: Tracking
Why it matters: Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.

### 8. [LOW] 3 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: "Read more" (span.brxe-plabos), "Read more" (span.brxe-plabos), "Read more" (span.brxe-plabos).
Exact elements found: "Read more" (span.brxe-plabos), "Read more" (span.brxe-plabos), "Read more" (span.brxe-plabos)

### 9. [LOW] 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: a modern Referrer-Policy (the current one leaks full URLs to other sites). 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.

### 10. [LOW] 10 generic CTA links/buttons ("Click here", "Learn more", "Submit")
Category: Accessibility (WCAG), Conversion
Why it matters: Screen-reader users hear a list of "click here, click here, learn more" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination ("See pricing", "Read the case study").
Exact elements found: "Learn More" (a), "Learn More" (a), "Learn More" (a), "Learn More" (a), "Learn More" (a)

### 11. [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: "Read more" (span.brxe-plabos) (div/span used as a button, no role), "Read more" (span.brxe-plabos) (div/span used as a button, no role), "Read more" (span.brxe-plabos) (div/span used as a button, no role), (a.bricks-link-wrapper) (no accessible name)

### 12. [LOW] Headings skip levels
Category: Accessibility (WCAG)
Why it matters: Skipping a heading level breaks the document outline that screen readers and search engines rely on. On this page the outline jumps to an H3 without the level above it, at "$7B+". Lighthouse flagged 2 headings out of order.

## 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://austincapitalmortgage.com/",
  "generated_at": "2026-08-31T03:43:52.497Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 1,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 168,
    "desktop_lcp_ms": 264,
    "mobile_ttfb_ms": 54,
    "mobile_fcp_ms": 168,
    "page_weight_kb": 2298
  },
  "finding_count": 12,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "28 of 52 tappable items on this page (54%) 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": [
        "a 20x10 \"Skip to main content\"",
        "a 20x10 \"Skip to footer\"",
        "button 20x16 \"Open mobile menu\"",
        "button 16x48 \"Purchase Sub menu\"",
        "button 16x48 \"Refinance Sub menu\"",
        "button 16x48 \"Resources Sub menu\"",
        "button 16x48 \"About Sub menu\"",
        "a 188x15 (no visible label)"
      ]
    },
    {
      "severity": "high",
      "title": "Some links cannot be followed by Google",
      "detail": "Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "crawlable",
      "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": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 2.2 megabytes, roughly 2189 KB of images and 0 KB of JavaScript across 33 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Main content is slow to appear on phones",
      "detail": "For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 3.6 seconds to show up. Google's \"good\" threshold is 2.5 seconds, and this misses it. That number is also one of the signals Google uses to decide where to rank your page in search.",
      "device": "both",
      "tags": [],
      "topic": null,
      "confidence": "field",
      "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": "No advertising pixel detected",
      "detail": "Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "no_ad_pixel",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "3 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: \"Read more\" (span.brxe-plabos), \"Read more\" (span.brxe-plabos), \"Read more\" (span.brxe-plabos).",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "dead_clicks",
      "confidence": "measured",
      "evidence": [
        "\"Read more\" (span.brxe-plabos)",
        "\"Read more\" (span.brxe-plabos)",
        "\"Read more\" (span.brxe-plabos)"
      ]
    },
    {
      "severity": "low",
      "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: a modern Referrer-Policy (the current one leaks full URLs to other sites). 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": "10 generic CTA links/buttons (\"Click here\", \"Learn more\", \"Submit\")",
      "detail": "Screen-reader users hear a list of \"click here, click here, learn more\" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination (\"See pricing\", \"Read the case study\").",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "link_text",
      "confidence": "measured",
      "evidence": [
        "\"Learn More\" (a)",
        "\"Learn More\" (a)",
        "\"Learn More\" (a)",
        "\"Learn More\" (a)",
        "\"Learn More\" (a)"
      ]
    },
    {
      "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": [
        "\"Read more\" (span.brxe-plabos) (div/span used as a button, no role)",
        "\"Read more\" (span.brxe-plabos) (div/span used as a button, no role)",
        "\"Read more\" (span.brxe-plabos) (div/span used as a button, no role)",
        "(a.bricks-link-wrapper) (no accessible name)"
      ]
    },
    {
      "severity": "low",
      "title": "Headings skip levels",
      "detail": "Skipping a heading level breaks the document outline that screen readers and search engines rely on. On this page the outline jumps to an H3 without the level above it, at \"$7B+\". Lighthouse flagged 2 headings out of order.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    }
  ]
}