What your site is actually doing.

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

## Context
- Site: https://fastenal.com
- Mobile LCP (lab median): 662 ms
- Desktop LCP (lab median): 664 ms
- Page weight (median): 4.9 MB
- Tap targets under 44px: 68% (36 of 53)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.7s 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 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] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 36 of 53 tappable items on this page (68%) 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 (8 of 36): a 163x19 "Industrial Services", a 163x19 "Green Resources", a 163x19 "Blue Lane Freight", a 163x19 "International Orders", a 124x19 "Safety", a 124x19 "Metalworking", a 124x19 "Engineering", a 124x19 "Government"

### 2. [HIGH] A floating widget is covering a clickable element
Category: Conversion, Accessibility (WCAG)
Why it matters: 5 clickable elements are sitting underneath a fixed overlay (img.mw-100 over a "Engineering"), 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: a "Engineering" under img.mw-100, a "Government" under nav.navbar, a "Accessibility" under p.ps-3, a "Blue Lane Freight" under p.ps-3, a "Safety Data Sheets" under div.col-xs-12

### 3. [HIGH] Meta Pixel (Facebook) is installed but misconfigured
Category: Tracking
Why it matters: Meta Pixel installed but no Lead/Purchase/Checkout event fires on this page, only PageView. Your Meta ad sessions can't be optimized for conversions until you track at least one downstream event.

### 4. [HIGH] Google Analytics tracking broken
Category: Tracking, Conversion
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.

### 5. [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: h1 "Supply ChainsSimplified.": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), em "Featuring Body Guard": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), p "DIGITAL TOOLS": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), h2 "Simplifying procurement,unlo": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), span "unlocking analytics": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255)), p "Digital toolboxes should hav": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255))

### 6. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 4.9 MB, roughly 2834 KB of images and 1528 KB of JavaScript across 89 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

### 7. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 13 of 14 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 13): fastenal.png "FASTENAL", Nut.svg "NutIcon", shop-now.svg "Shop Now", chevron-left-solid%20.svg "Scroll Left", d2-fasteners.webp "Fasteners", d2-safety.webp "Safety"

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

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

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

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

### 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] The page has 3 top-level headings
Why it matters: Multiple <h1> tags blur which heading is the main one. Keep one H1 and demote the rest to H2 so the page's structure is clear.

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

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

### 16. [LOW] 4 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.text-decoration-none) (no accessible name), (a.text-decoration-none) (no accessible name), (a.text-decoration-none) (no accessible name), (a.text-decoration-none) (no accessible name)

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

### 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 H6 without the level above it, at "Get a closer look at our services". Lighthouse flagged 2 headings 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://fastenal.com",
  "generated_at": "2026-09-09T03:43:32.747Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 662,
    "desktop_lcp_ms": 664,
    "mobile_ttfb_ms": 189,
    "mobile_fcp_ms": 342,
    "page_weight_kb": 4988
  },
  "finding_count": 18,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "36 of 53 tappable items on this page (68%) 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 163x19 \"Industrial Services\"",
        "a 163x19 \"Green Resources\"",
        "a 163x19 \"Blue Lane Freight\"",
        "a 163x19 \"International Orders\"",
        "a 124x19 \"Safety\"",
        "a 124x19 \"Metalworking\"",
        "a 124x19 \"Engineering\"",
        "a 124x19 \"Government\""
      ]
    },
    {
      "severity": "high",
      "title": "A floating widget is covering a clickable element",
      "detail": "5 clickable elements are sitting underneath a fixed overlay (img.mw-100 over a \"Engineering\"), 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": [
        "a \"Engineering\" under img.mw-100",
        "a \"Government\" under nav.navbar",
        "a \"Accessibility\" under p.ps-3",
        "a \"Blue Lane Freight\" under p.ps-3",
        "a \"Safety Data Sheets\" under div.col-xs-12"
      ]
    },
    {
      "severity": "high",
      "title": "Meta Pixel (Facebook) is installed but misconfigured",
      "detail": "Meta Pixel installed but no Lead/Purchase/Checkout event fires on this page, only PageView. Your Meta ad sessions can't be optimized for conversions until you track at least one downstream event.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "tracker_misconfig:Meta Pixel (Facebook)",
      "confidence": "measured",
      "evidence": []
    },
    {
      "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": [
        "Tracking",
        "Conversion"
      ],
      "topic": "tracking",
      "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": [
        "h1 \"Supply ChainsSimplified.\": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255))",
        "em \"Featuring Body Guard\": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255))",
        "p \"DIGITAL TOOLS\": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255))",
        "h2 \"Simplifying procurement,unlo\": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255))",
        "span \"unlocking analytics\": 1:1, needs 3:1 (rgb(255, 255, 255) on rgb(255, 255, 255))",
        "p \"Digital toolboxes should hav\": 1:1, needs 4.5:1 (rgb(255, 255, 255) on rgb(255, 255, 255))"
      ]
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 4.9 MB, roughly 2834 KB of images and 1528 KB of JavaScript across 89 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": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "13 of 14 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": [
        "fastenal.png \"FASTENAL\"",
        "Nut.svg \"NutIcon\"",
        "shop-now.svg \"Shop Now\"",
        "chevron-left-solid%20.svg \"Scroll Left\"",
        "d2-fasteners.webp \"Fasteners\"",
        "d2-safety.webp \"Safety\""
      ]
    },
    {
      "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 726 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 57 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 16 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": "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": "The page has 3 top-level headings",
      "detail": "Multiple <h1> tags blur which heading is the main one. Keep one H1 and demote the rest to H2 so the page's structure is clear.",
      "device": "both",
      "tags": [],
      "topic": "h1",
      "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": "4 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.text-decoration-none) (no accessible name)",
        "(a.text-decoration-none) (no accessible name)",
        "(a.text-decoration-none) (no accessible name)",
        "(a.text-decoration-none) (no accessible name)"
      ]
    },
    {
      "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": "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 H6 without the level above it, at \"Get a closer look at our services\". Lighthouse flagged 2 headings out of order.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    }
  ]
}