What your site is actually doing.

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

## Context
- Site: https://delekus.com
- Mobile LCP (lab median): 410 ms
- Desktop LCP (lab median): 434 ms
- Page weight (median): 13.5 MB
- Tap targets under 44px: 33% (20 of 61)
- Evidence base: 4 mobile + 2 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: Real Chrome visitors see the main content in 2.1s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Layout stays put as it loads: Real visitors see only 0.01 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- 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] A floating widget is covering a clickable element
Category: Conversion, Accessibility (WCAG)
Why it matters: 12 clickable elements are sitting underneath a fixed overlay (div#cm_disclaimer-header over button "Previous slide"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.
Exact elements found: button "Previous slide" under div#cm_disclaimer-header, button "Next slide" under div#cm_disclaimer-header, a "SIGN UP FOR EMAIL ALERTS 
(O" under div#cm_disclaimer-header, a "About Us" under p, a "Business Operations" under p, a "Investors" under p

### 2. [HIGH] Page contains "Lorem ipsum" placeholder text
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.

### 3. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 20 of 61 tappable items on this page (33%) 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: button 30x20 "close disclaimer", button 30x20 (no visible label), a 93x20 (no visible label), a 93x20 (no visible label), button 8x8 "Go to slide 1", button 8x8 "Go to slide 2", button 8x8 "Go to slide 3", a 88x18 "READ MORE 
REFINING"

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

### 5. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 13.5 megabytes, roughly 12150 KB of images and 1353 KB of JavaScript across 115 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

### 6. [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: $(...).counterUp is not a function
How we know: median across loads

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

### 8. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 18 of 18 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.01, 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: Delek-Logo-Long-cropped.png "Delek US Logo", Delek-Logo-Long-cropped.png "Delek US company logo", about-us-nav.png, business-operations-nav.png, investors-nav.png, careers-nav.png

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

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

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

### 13. [LOW] The page loads from a lot of third-party services
Why it matters: Around 18 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

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

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

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

### 17. [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 1,085 KiB.

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

### 19. [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: 4 links found.

### 20. [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://delekus.com",
  "generated_at": "2026-08-21T19:25:48.197Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 410,
    "desktop_lcp_ms": 434,
    "mobile_ttfb_ms": 65,
    "mobile_fcp_ms": 396,
    "page_weight_kb": 13787
  },
  "finding_count": 20,
  "findings": [
    {
      "severity": "high",
      "title": "A floating widget is covering a clickable element",
      "detail": "12 clickable elements are sitting underneath a fixed overlay (div#cm_disclaimer-header over button \"Previous slide\"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)"
      ],
      "topic": "obscured_control",
      "confidence": "measured",
      "evidence": [
        "button \"Previous slide\" under div#cm_disclaimer-header",
        "button \"Next slide\" under div#cm_disclaimer-header",
        "a \"SIGN UP FOR EMAIL ALERTS \n(O\" under div#cm_disclaimer-header",
        "a \"About Us\" under p",
        "a \"Business Operations\" under p",
        "a \"Investors\" under p"
      ]
    },
    {
      "severity": "high",
      "title": "Page contains \"Lorem ipsum\" placeholder text",
      "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": "Tiny buttons are hard to tap on mobile",
      "detail": "20 of 61 tappable items on this page (33%) 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": [
        "button 30x20 \"close disclaimer\"",
        "button 30x20 (no visible label)",
        "a 93x20 (no visible label)",
        "a 93x20 (no visible label)",
        "button 8x8 \"Go to slide 1\"",
        "button 8x8 \"Go to slide 2\"",
        "button 8x8 \"Go to slide 3\"",
        "a 88x18 \"READ MORE \nREFINING\""
      ]
    },
    {
      "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": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 13.5 megabytes, roughly 12150 KB of images and 1353 KB of JavaScript across 115 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": "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": [
        "$(...).counterUp is not a function"
      ]
    },
    {
      "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": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "18 of 18 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.01, 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": [
        "Delek-Logo-Long-cropped.png \"Delek US Logo\"",
        "Delek-Logo-Long-cropped.png \"Delek US company logo\"",
        "about-us-nav.png",
        "business-operations-nav.png",
        "investors-nav.png",
        "careers-nav.png"
      ]
    },
    {
      "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": "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). 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": "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": "The page loads from a lot of third-party services",
      "detail": "Around 18 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 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 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 1,085 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 210 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "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: 4 links 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": []
    }
  ]
}