What your site is actually doing.

Audit of https://hfsinclair.com, run August 16, 2026. 23 issues were found. I want them fixed.

## Context
- Site: https://hfsinclair.com
- Mobile LCP (lab median): 828 ms
- Desktop LCP (lab median): 804 ms
- Page weight (median): 2.0 MB
- Tap targets under 44px: 80% (20 of 25)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.8s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.

## Issues, most damaging first

### 1. [HIGH] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 20 of 25 tappable items on this page (80%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend 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 85x22 "Homepage", a 62x23 "93.67", a 225x22 (no visible label), a 225x22 (no visible label), a 225x22 (no visible label), a 225x22 (no visible label), a 225x22 (no visible label), a 29x22 (no visible label)

### 2. [HIGH] Google Analytics tracking broken
Why it matters: The Google Analytics request failed to complete on every one of the 4 test loads. If real visitors hit the same failure, GA is missing those visits and the dashboard has no way to flag it. Conversion numbers, audience counts, and channel attribution are all undercounting. Worth checking the tag loading order and any consent banner that might be blocking the request.

### 3. [HIGH] Page contains unrendered {{ template }} variable
Category: Conversion, SEO
Why it matters: Real visitors see this rendered text. It almost always means a template variable, localization string, or third-party widget failed to render. Search the page for the exact pattern and fix the source.

### 4. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 2.0 megabytes, roughly 655 KB of images and 1017 KB of JavaScript across 76 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] Page is wider than the phone screen
Affects: mobile only
Why it matters: Something on this page extends past the right edge on mobile. The visitor has to drag sideways to see it, which they won't, and anything tappable over there is essentially invisible. Usually a wide image or a fixed-width container that didn't get a max-width.

### 6. [MEDIUM] The page has no main heading
Why it matters: There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.

### 7. [MEDIUM] 1 form field has 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="_ctrl0$ctl24$txtsearchinput" (input)

### 8. [MEDIUM] 7 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: (a) (no accessible name), (a) (no accessible name), (a) (no accessible name), (a) (no accessible name), (a) (no accessible name), (a) (no accessible name), (a) (no accessible name)

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

### 10. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 11 of 11 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: search_icon.png "search", logo.png "Homepage", Logo_Mobile.png, Logo_Mobile.png, CheyenneRefinery.jpg, SinclairStation.jpg

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

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

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

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

### 15. [LOW] The page loads from a lot of third-party services
Why it matters: Around 12 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.
How we know: median across loads

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

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

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

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

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

### 21. [LOW] Images are missing alt text
Category: Accessibility (WCAG), SEO
Why it matters: Screen readers skip or read the filename of images without alt text, and search engines lose the context. Describe content images; mark decorative ones alt="".

### 22. [LOW] Some links do not describe where they go
Category: Accessibility (WCAG), Conversion
Why it matters: Links like "click here" or "read more" tell screen-reader users and search engines nothing about the destination. Lighthouse measured: 1 link found.

### 23. [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://hfsinclair.com",
  "generated_at": "2026-08-21T19:25:48.596Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 828,
    "desktop_lcp_ms": 804,
    "mobile_ttfb_ms": 109,
    "mobile_fcp_ms": 768,
    "page_weight_kb": 2020
  },
  "finding_count": 23,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "20 of 25 tappable items on this page (80%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend 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 85x22 \"Homepage\"",
        "a 62x23 \"93.67\"",
        "a 225x22 (no visible label)",
        "a 225x22 (no visible label)",
        "a 225x22 (no visible label)",
        "a 225x22 (no visible label)",
        "a 225x22 (no visible label)",
        "a 29x22 (no visible label)"
      ]
    },
    {
      "severity": "high",
      "title": "Google Analytics tracking broken",
      "detail": "The Google Analytics request failed to complete on every one of the 4 test loads. If real visitors hit the same failure, GA is missing those visits and the dashboard has no way to flag it. Conversion numbers, audience counts, and channel attribution are all undercounting. Worth checking the tag loading order and any consent banner that might be blocking the request.",
      "device": "both",
      "tags": [],
      "topic": null,
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Page contains unrendered {{ template }} variable",
      "detail": "Real visitors see this rendered text. It almost always means a template variable, localization string, or third-party widget failed to render. Search the page for the exact pattern and fix the source.",
      "device": "both",
      "tags": [
        "Conversion",
        "SEO"
      ],
      "topic": "placeholder",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 2.0 megabytes, roughly 655 KB of images and 1017 KB of JavaScript across 76 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": "Page is wider than the phone screen",
      "detail": "Something on this page extends past the right edge on mobile. The visitor has to drag sideways to see it, which they won't, and anything tappable over there is essentially invisible. Usually a wide image or a fixed-width container that didn't get a max-width.",
      "device": "mobile",
      "tags": [],
      "topic": null,
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "The page has no main heading",
      "detail": "There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.",
      "device": "both",
      "tags": [],
      "topic": "h1",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "1 form field has 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=\"_ctrl0$ctl24$txtsearchinput\" (input)"
      ]
    },
    {
      "severity": "medium",
      "title": "7 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": [
        "(a) (no accessible name)",
        "(a) (no accessible name)",
        "(a) (no accessible name)",
        "(a) (no accessible name)",
        "(a) (no accessible name)",
        "(a) (no accessible name)",
        "(a) (no accessible name)"
      ]
    },
    {
      "severity": "medium",
      "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": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "11 of 11 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": [
        "search_icon.png \"search\"",
        "logo.png \"Homepage\"",
        "Logo_Mobile.png",
        "Logo_Mobile.png",
        "CheyenneRefinery.jpg",
        "SinclairStation.jpg"
      ]
    },
    {
      "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": "There is very little text on this page",
      "detail": "The page has about 112 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": "The page loads from a lot of third-party services",
      "detail": "Around 12 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.",
      "device": "both",
      "tags": [],
      "topic": "third_party",
      "confidence": "sampled",
      "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 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 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 536 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 107 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Images are missing alt text",
      "detail": "Screen readers skip or read the filename of images without alt text, and search engines lose the context. Describe content images; mark decorative ones alt=\"\".",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "SEO"
      ],
      "topic": "image_alt",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Some links do not describe where they go",
      "detail": "Links like \"click here\" or \"read more\" tell screen-reader users and search engines nothing about the destination. Lighthouse measured: 1 link found.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "link_text",
      "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": []
    }
  ]
}