What your site is actually doing.

Audit of https://mwjsautomations.com/, run September 2, 2026. 12 issues were found. I want them fixed.

## Context
- Site: https://mwjsautomations.com/
- Mobile LCP (lab median): 1662 ms
- Desktop LCP (lab median): 1008 ms
- Page weight (median): 0.1 MB
- Tap targets under 44px: 50% (10 of 20)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 1.7s 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.1 MB across 12 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: 10 of 20 tappable items on this page (50%) 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 258x17 "book an automation audit in ", a 231x17 "improve your local search ra", a 358x20 "max@mwjsautomations.com", a 358x20 "0479 149 841", a 78x17 "All Services", a 199x17 "Custom Website Development", a 164x17 "AI Chatbots & Workflows", a 155x17 "Local SEO Optimization"

### 2. [HIGH] 4 form fields have 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: name="name" (input), name="email" (input), name="phone" (input), name="message" (textarea)

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

### 5. [MEDIUM] No XML sitemap found
Why it matters: No sitemap.xml at the standard location and none listed in robots.txt. A sitemap tells search engines every page you want indexed; without it they rely on link discovery and may miss pages.

### 6. [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); a stronger HSTS policy (max-age at least 180 days plus includeSubDomains); 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.

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

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

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

### 10. [LOW] 3 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: name="name" (type=text), name="email" (type=email), name="phone" (type=tel)

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

### 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 H4 without the level above it, at "SERVICES". Lighthouse flagged 1 heading 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://mwjsautomations.com/",
  "generated_at": "2026-09-02T03:41:26.713Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 1662,
    "desktop_lcp_ms": 1008,
    "mobile_ttfb_ms": 129,
    "mobile_fcp_ms": 480,
    "page_weight_kb": 98
  },
  "finding_count": 12,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "10 of 20 tappable items on this page (50%) 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 258x17 \"book an automation audit in \"",
        "a 231x17 \"improve your local search ra\"",
        "a 358x20 \"max@mwjsautomations.com\"",
        "a 358x20 \"0479 149 841\"",
        "a 78x17 \"All Services\"",
        "a 199x17 \"Custom Website Development\"",
        "a 164x17 \"AI Chatbots & Workflows\"",
        "a 155x17 \"Local SEO Optimization\""
      ]
    },
    {
      "severity": "high",
      "title": "4 form fields have 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": [
        "name=\"name\" (input)",
        "name=\"email\" (input)",
        "name=\"phone\" (input)",
        "name=\"message\" (textarea)"
      ]
    },
    {
      "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": "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": "medium",
      "title": "No XML sitemap found",
      "detail": "No sitemap.xml at the standard location and none listed in robots.txt. A sitemap tells search engines every page you want indexed; without it they rely on link discovery and may miss pages.",
      "device": "both",
      "tags": [],
      "topic": "missing_sitemap",
      "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); a stronger HSTS policy (max-age at least 180 days plus includeSubDomains); 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": "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 50 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "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": "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": "3 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": [
        "name=\"name\" (type=text)",
        "name=\"email\" (type=email)",
        "name=\"phone\" (type=tel)"
      ]
    },
    {
      "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": "Skipping a heading level breaks the document outline that screen readers and search engines rely on. On this page the outline jumps to an H4 without the level above it, at \"SERVICES\". Lighthouse flagged 1 heading out of order.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    }
  ]
}