What your site is actually doing.

Audit of https://mission-gateway.missiondigital.co.uk/, run September 8, 2026. 18 issues were found. I want them fixed.

## Context
- Site: https://mission-gateway.missiondigital.co.uk/
- Mobile LCP (lab median): 412 ms
- Desktop LCP (lab median): 1090 ms
- Tap targets under 44px: 67% (4 of 6)
- 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.
- 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: 4 of 6 tappable items on this page (67%) 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 25x18 "here", a 48x20 "Instagram", a 48x20 "LinkedIn", a 98x15 "missiondigital.co.uk"

### 2. [HIGH] 3 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="fullname" (input) placeholder="Full name*", name="email" (input) placeholder="Email*", name="phone" (input) placeholder="Phone number*"

### 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 1 pages from your sitemap, a partial crawl rather than your full site.)

### 4. [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.
Exact elements found: a.login-btn "Login": 2.53:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(0, 174, 239)), p.fade-item "Mission is proud to be certi": 2.99:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(10, 160, 216))

### 5. [MEDIUM] JavaScript crashed while the page was loading
Category: Conversion, Tracking
Why it matters: 1 script error fired during page load. When a script crashes, buttons sometimes stop working, analytics stop firing, and the visitor has no warning. Worth opening the browser console to find which script failed.
Exact elements found: NAV: Navigation timeout of 45000 ms exceeded
How we know: median across loads

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

### 7. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 29 of 29 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 (6 of 29): mission_logo_blue_2000px_kx2nxi.png "Mission logo", ipad_updated_graphic_mgrsia.png "iPad", Iphone_asset_xkqqhu.png "iPhone", diagram_Asset_ttlsmv.png "Gateway diagram", globe_spin_animation_asset_fhqbbd_sphwpb.webp, TPN_Logo_yacuje.png "TPN Logo"

### 8. [LOW] The page is heavy to download
Category: Performance
Why it matters: Total page weight is high. On a phone with patchy data, that is extra seconds of blank screen before the page is usable. Lighthouse measured: Total size was 11,626 KiB.

### 9. [LOW] No visible contact details (email or phone)
Category: Conversion
Why it matters: This page exposes no email address, no phone link, no contact form and no link to a contact page. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. A contact route that only appears after JavaScript runs, or that lives on a page not checked here, will not be visible to this check. Add an email or phone link in the header or footer.

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

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

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

### 15. [LOW] 2 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="email" (type=email), name="phone" (type=tel)

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

### 17. [LOW] 2 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: "here" (a), "Send" (button)

### 18. [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 "Keeping you connected". 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://mission-gateway.missiondigital.co.uk/",
  "generated_at": "2026-09-30T17:43:33.901Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 412,
    "desktop_lcp_ms": 1090,
    "mobile_ttfb_ms": 102,
    "mobile_fcp_ms": 286,
    "page_weight_kb": null
  },
  "finding_count": 18,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "4 of 6 tappable items on this page (67%) 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 25x18 \"here\"",
        "a 48x20 \"Instagram\"",
        "a 48x20 \"LinkedIn\"",
        "a 98x15 \"missiondigital.co.uk\""
      ]
    },
    {
      "severity": "high",
      "title": "3 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=\"fullname\" (input) placeholder=\"Full name*\"",
        "name=\"email\" (input) placeholder=\"Email*\"",
        "name=\"phone\" (input) placeholder=\"Phone number*\""
      ]
    },
    {
      "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 1 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": [
        "a.login-btn \"Login\": 2.53:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(0, 174, 239))",
        "p.fade-item \"Mission is proud to be certi\": 2.99:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(10, 160, 216))"
      ]
    },
    {
      "severity": "medium",
      "title": "JavaScript crashed while the page was loading",
      "detail": "1 script error fired during page load. When a script crashes, buttons sometimes stop working, analytics stop firing, and the visitor has no warning. Worth opening the browser console to find which script failed.",
      "device": "both",
      "tags": [
        "Conversion",
        "Tracking"
      ],
      "topic": "js_errors",
      "confidence": "sampled",
      "evidence": [
        "NAV: Navigation timeout of 45000 ms exceeded"
      ]
    },
    {
      "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": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "29 of 29 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": [
        "mission_logo_blue_2000px_kx2nxi.png \"Mission logo\"",
        "ipad_updated_graphic_mgrsia.png \"iPad\"",
        "Iphone_asset_xkqqhu.png \"iPhone\"",
        "diagram_Asset_ttlsmv.png \"Gateway diagram\"",
        "globe_spin_animation_asset_fhqbbd_sphwpb.webp",
        "TPN_Logo_yacuje.png \"TPN Logo\""
      ]
    },
    {
      "severity": "low",
      "title": "The page is heavy to download",
      "detail": "Total page weight is high. On a phone with patchy data, that is extra seconds of blank screen before the page is usable. Lighthouse measured: Total size was 11,626 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No visible contact details (email or phone)",
      "detail": "This page exposes no email address, no phone link, no contact form and no link to a contact page. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. A contact route that only appears after JavaScript runs, or that lives on a page not checked here, will not be visible to this check. Add an email or phone link in the header or footer.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_contact",
      "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 15. 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": "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": "2 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=\"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": "2 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": [
        "\"here\" (a)",
        "\"Send\" (button)"
      ]
    },
    {
      "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 \"Keeping you connected\". Lighthouse flagged 1 heading out of order.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    }
  ]
}