What your site is actually doing.

Audit of https://eco-host.net/, run August 15, 2026. 16 issues were found. I want them fixed.

## Context
- Site: https://eco-host.net/
- Mobile LCP (lab median): 1798 ms
- Desktop LCP (lab median): 1736 ms
- Page weight (median): 0.1 MB
- Tap targets under 44px: 0% (0 of 15)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 1.8s 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 53 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- Search basics are in place: Lighthouse scores SEO 91/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] 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: (input) placeholder="Your name", (input) placeholder="Username", (input) placeholder="Password (8+ characters)", (input) placeholder="Confirm password"

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

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

### 5. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 43 of 43 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: WkKAAAAAElFTkSuQmCC, GHwnIAAAAASUVORK5CYII=, oldIPbHkuzoAAAAASUVORK5CYII=, w7wBaD2r+djT4eOalc6jbWXKOnNPPxOOzdX8jnnjiiSeeeOKJJ554LtP5G6CQd6bnVmo5AAAAAElFTkSuQmCC, fyXt7Le3kv7+W9vovrv0qBIN9WcPdYAAAAAElFTkSuQmCC, wGT5BAIisg3vgAAAABJRU5ErkJggg==

### 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] Some text is too small to read on phones
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 12 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.
How we know: median across loads

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

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

### 10. [LOW] There is very little text on this page
Why it matters: The page has about 46 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.

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

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

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

### 15. [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 4,097 KiB.

### 16. [LOW] Sitemap not listed in robots.txt
Why it matters: A sitemap exists but is not referenced in robots.txt. Adding a "Sitemap:" line to robots.txt helps crawlers find it reliably.

## 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://eco-host.net/",
  "generated_at": "2026-08-21T19:25:49.045Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 1798,
    "desktop_lcp_ms": 1736,
    "mobile_ttfb_ms": 43,
    "mobile_fcp_ms": 246,
    "page_weight_kb": 79
  },
  "finding_count": 16,
  "findings": [
    {
      "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": [
        "(input) placeholder=\"Your name\"",
        "(input) placeholder=\"Username\"",
        "(input) placeholder=\"Password (8+ characters)\"",
        "(input) placeholder=\"Confirm password\""
      ]
    },
    {
      "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 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": "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": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "43 of 43 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": [
        "WkKAAAAAElFTkSuQmCC",
        "GHwnIAAAAASUVORK5CYII=",
        "oldIPbHkuzoAAAAASUVORK5CYII=",
        "w7wBaD2r+djT4eOalc6jbWXKOnNPPxOOzdX8jnnjiiSeeeOKJJ554LtP5G6CQd6bnVmo5AAAAAElFTkSuQmCC",
        "fyXt7Le3kv7+W9vovrv0qBIN9WcPdYAAAAAElFTkSuQmCC",
        "wGT5BAIisg3vgAAAABJRU5ErkJggg=="
      ]
    },
    {
      "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": "Some text is too small to read on phones",
      "detail": "12 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tiny_text",
      "confidence": "sampled",
      "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 46 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 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 11 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "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 4,097 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Sitemap not listed in robots.txt",
      "detail": "A sitemap exists but is not referenced in robots.txt. Adding a \"Sitemap:\" line to robots.txt helps crawlers find it reliably.",
      "device": "both",
      "tags": [],
      "topic": "sitemap_not_in_robots",
      "confidence": "measured",
      "evidence": []
    }
  ]
}