What your site is actually doing.

Audit of https://uline.com, run September 1, 2026. 18 issues were found. I want them fixed.

## Context
- Site: https://uline.com
- Mobile LCP (lab median): 1172 ms
- Desktop LCP (lab median): 1614 ms
- Page weight (median): 2.7 MB
- Tap targets under 44px: 39% (15 of 38)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 1.2s 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.
- Search basics are in place: Lighthouse scores SEO 92/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] Some links cannot be followed by Google
Category: SEO
Why it matters: Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.

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

### 3. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 15 of 38 tappable items on this page (39%) 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 75x22 "Uline homepage", a 44x22 "My Account", a 44x22 "Call Uline", a 44x22 "Cart: 0 Items", a 30x19 "Help", a 67x19 "Contact Us", a 49x19 "Careers", a 92x19 "Shipping Boxes"

### 4. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 2.7 megabytes, roughly 137 KB of images and 2282 KB of JavaScript across 134 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] 2 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), name="txtproductsearch" (input) placeholder="Search"

### 6. [MEDIUM] 7 potential dead-click targets
Category: Conversion, Accessibility (WCAG), Tracking
Why it matters: Elements styled like buttons but with no anchor, no <button> wrapper, no role="button", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: "Help" (span.hide), "Contact Us" (span.hide), "Shipping Boxes" (span.hide).
Exact elements found: "Help" (span.hide), "Contact Us" (span.hide), "Shipping Boxes" (span.hide), "Plastic Bags" (span.hide), "Catalog Request" (span.hide)

### 7. [MEDIUM] Click activity may be invisible inside the Facebook in-app browser
Category: Tracking
Why it matters: Patterns on this page (42 inline onclick handlers) tend to suppress click events inside Android Webview and iOS in-app browsers. Visitors arriving from Meta ads may register as zero-interaction sessions even when they're actively using the page. Add a server-side landing tracker so you don't lose that audience entirely.

### 8. [MEDIUM] 10 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: "Click to view Uline Private Label produc" (div.imageClick1) (div/span used as a button, no role), "Click to view Uline Private Label produc" (div.imageClick2) (div/span used as a button, no role), (a.modal_close) (no accessible name), "Help" (span.hide) (div/span used as a button, no role), "Contact Us" (span.hide) (div/span used as a button, no role), "Shipping Boxes" (span.hide) (div/span used as a button, no role), "Plastic Bags" (span.hide) (div/span used as a button, no role), "Catalog Request" (span.hide) (div/span used as a button, no role)

### 9. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 32 of 33 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: mobile-spinner.gif, gnr_logo_blue "Uline", gnr_mobile_phoneicon, gnr_mobile_emailtrackingicon, gnr_mobile_chatbubblesicon "contact chat", gnr_logo_blue "Uline Logo"

### 10. [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,068 KiB.

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

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

### 13. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.

### 14. [LOW] Search-result title will be cut off
Category: SEO
Why it matters: The title is 80 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped.

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

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

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

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

## 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://uline.com",
  "generated_at": "2026-09-01T03:42:16.666Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 1172,
    "desktop_lcp_ms": 1614,
    "mobile_ttfb_ms": 158,
    "mobile_fcp_ms": 768,
    "page_weight_kb": 2782
  },
  "finding_count": 18,
  "findings": [
    {
      "severity": "high",
      "title": "Some links cannot be followed by Google",
      "detail": "Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "crawlable",
      "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": "Tiny buttons are hard to tap on mobile",
      "detail": "15 of 38 tappable items on this page (39%) 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 75x22 \"Uline homepage\"",
        "a 44x22 \"My Account\"",
        "a 44x22 \"Call Uline\"",
        "a 44x22 \"Cart: 0 Items\"",
        "a 30x19 \"Help\"",
        "a 67x19 \"Contact Us\"",
        "a 49x19 \"Careers\"",
        "a 92x19 \"Shipping Boxes\""
      ]
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 2.7 megabytes, roughly 137 KB of images and 2282 KB of JavaScript across 134 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": "2 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)",
        "name=\"txtproductsearch\" (input) placeholder=\"Search\""
      ]
    },
    {
      "severity": "medium",
      "title": "7 potential dead-click targets",
      "detail": "Elements styled like buttons but with no anchor, no <button> wrapper, no role=\"button\", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: \"Help\" (span.hide), \"Contact Us\" (span.hide), \"Shipping Boxes\" (span.hide).",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "dead_clicks",
      "confidence": "measured",
      "evidence": [
        "\"Help\" (span.hide)",
        "\"Contact Us\" (span.hide)",
        "\"Shipping Boxes\" (span.hide)",
        "\"Plastic Bags\" (span.hide)",
        "\"Catalog Request\" (span.hide)"
      ]
    },
    {
      "severity": "medium",
      "title": "Click activity may be invisible inside the Facebook in-app browser",
      "detail": "Patterns on this page (42 inline onclick handlers) tend to suppress click events inside Android Webview and iOS in-app browsers. Visitors arriving from Meta ads may register as zero-interaction sessions even when they're actively using the page. Add a server-side landing tracker so you don't lose that audience entirely.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "webview",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "10 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": [
        "\"Click to view Uline Private Label produc\" (div.imageClick1) (div/span used as a button, no role)",
        "\"Click to view Uline Private Label produc\" (div.imageClick2) (div/span used as a button, no role)",
        "(a.modal_close) (no accessible name)",
        "\"Help\" (span.hide) (div/span used as a button, no role)",
        "\"Contact Us\" (span.hide) (div/span used as a button, no role)",
        "\"Shipping Boxes\" (span.hide) (div/span used as a button, no role)",
        "\"Plastic Bags\" (span.hide) (div/span used as a button, no role)",
        "\"Catalog Request\" (span.hide) (div/span used as a button, no role)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "32 of 33 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": [
        "mobile-spinner.gif",
        "gnr_logo_blue \"Uline\"",
        "gnr_mobile_phoneicon",
        "gnr_mobile_emailtrackingicon",
        "gnr_mobile_chatbubblesicon \"contact chat\"",
        "gnr_logo_blue \"Uline Logo\""
      ]
    },
    {
      "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,068 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 270 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page loads from a lot of third-party services",
      "detail": "Around 26 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 email capture or newsletter detected",
      "detail": "No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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": "Search-result title will be cut off",
      "detail": "The title is 80 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "title",
      "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": "There is very little text on this page",
      "detail": "The page has about 58 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 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": "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: 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": []
    }
  ]
}