What your site is actually doing.
One page: what is working, what to fix, and what to fix first. A phone-and-desktop teardown of the live site: 6 phone loads + 3 desktop loads. No login, no insider access, no Harvv pixel needed. The full evidence is at the bottom.
Working
What's already working. These held up across every load.
Speed is good.
No JavaScript errors on load.
Lighthouse scores SEO 91/100. The fundamentals Google looks for are present.
Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.
To fix
Ordered by where a visitor meets it first. Full evidence below.
Tiny buttons are hard to tap on mobile
A floating widget is covering a clickable element
Images without sizes set make the page jump as it loads
Some text is low-contrast and hard to read
Page is heavy and slow on mobile data
Meta Pixel sends only PageView on this page
3 small changes, on the pages people actually land on: Tiny buttons are hard to tap on mobile; A floating widget is covering a clickable element; Images without sizes set make the page jump as it loads. We re-measure the same samples after.
01Findings, most severe first
| Severity | Finding | How we know | Expand |
|---|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 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. The exact elements we found (8 of 36):
paste into Claude, Cursor, or ChatGPT | ||
| High | A floating widget is covering a clickable elementBothConversionAccessibility (WCAG) 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. The exact elements we found:
paste into Claude, Cursor, or ChatGPT | ||
| High | Images without sizes set make the page jump as it loadsBothPerformanceSEO 13 of 14 images on this page don't have width and height set, and the layout actually shifts as they load (measured Cumulative Layout Shift 1; Google's "needs work" starts at 0.1, "poor" at 0.25). As each image finishes loading, content below it slides down, so a visitor goes to tap one thing and ends up tapping another. The exact images we found (6 of 13):
paste into Claude, Cursor, or ChatGPT | ||
| High | Some text is low-contrast and hard to readBothAccessibility (WCAG) Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. The exact elements we found:
paste into Claude, Cursor, or ChatGPT | ||
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 4.6 MB, roughly 2834 KB of images and 1293 KB of JavaScript across 86 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. paste into Claude, Cursor, or ChatGPT | median across loads | |
| Medium | Meta Pixel sends only PageView on this pageBothTracking On this page the Meta Pixel sends only PageView. That is expected on a homepage, but check that a conversion event (a standard one like Lead, Schedule or Purchase, or a custom event) fires when a visitor actually converts, or that a custom conversion is set up in Events Manager. This scan loads pages and never submits a form or books a call, so it cannot see events that fire on those actions. If nothing fires there, Meta can optimise your ads for page views only. paste into Claude, Cursor, or ChatGPT | ||
| Low | Unused JavaScript is being downloadedBothPerformance 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 616 KiB. paste into Claude, Cursor, or ChatGPT | ||
| Low | Unused CSS is being downloadedBothPerformance 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | The page loads from a lot of third-party servicesBoth Around 14 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. paste into Claude, Cursor, or ChatGPT | median across loads | |
| Low | No email capture or newsletter detectedBothConversion 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | No canonical tag, so duplicate URLs split the page's rankingBoth 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | The page has 3 top-level headingsBoth 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | Links to this page will look bare when sharedBoth 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | No structured data for rich search resultsBoth 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. paste into Claude, Cursor, or ChatGPT | ||
| Low | 4 interactive elements have no stable, accessible identityBothAccessibility (WCAG)Tracking 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. The exact elements we found:
paste into Claude, Cursor, or ChatGPT | ||
| Low | Images are missing alt textBothAccessibility (WCAG)SEO 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="". paste into Claude, Cursor, or ChatGPT | ||
| Low | Headings skip levelsBothAccessibility (WCAG) 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. paste into Claude, Cursor, or ChatGPT |
Accessibility findings are automated checks against Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2. They flag potential barriers and legal risk, not a certification or a determination of compliance with the ADA, Section 508, or EN 301 549. Automated testing catches only a subset of issues; a full conformance review needs manual and assistive-technology testing by a qualified reviewer.
"How we know": unlabeled = a deterministic fact, identical on every load (e.g. element sizes). Most findings are this kind, so we only mark the exceptions: median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 234 ms | 218 ms | Lab |
| FCP (lab median) | 628 ms | 804 ms | Lab |
| LCP (lab median) | 1.3s | 1.1s | Good |
| Page weight (median) | 4.6 MB | 6.8 MB | Watch |
Google Lighthouse (lab): Performance 37 mobile / 49 desktop, SEO 91, Accessibility 74, Best Practices 92.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience. Add a Google API key to light up real-user field data (CrUX) and Lighthouse scores.
03Tiny buttons are hard to tap on mobile
36 of 53 tappable items on this page come in below the platform minimums for reliable tapping on a phone (Apple recommends 44pt, Android 48dp; WCAG 2.5.8 sets 24px as the hard accessibility floor). The same ones came up small on every one of the 6 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- 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"
The fix is CSS-only on most sites: add padding around the icon (don't just change the icon size) so the actual tap area is at least 44×44 pixels. No redesign, no new assets.
04Technical SEO & structured data
| Check | Result |
|---|---|
| Title | Fastenal Industrial Supplies, OEM Fasteners, Safety Products & More (67 chars) |
| Meta description | 146 chars |
| H1 | 3 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | None |
| Open Graph | Incomplete |
05The fix checklist
Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.
- Tiny buttons are hard to tap on mobileMobileCSS only
- A floating widget is covering a clickable elementBothCSS only
- Images without sizes set make the page jump as it loadsBothCSS only
- Page is heavy and slow on mobile dataBothSmall
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- The page loads from a lot of third-party servicesBothDev afternoon
- No email capture or newsletter detectedBothVaries
- Meta Pixel sends only PageView on this pageBothVaries
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- The page has 3 top-level headingsBothVaries
- Links to this page will look bare when sharedBoth1 line
- No structured data for rich search resultsBothVaries
- Some text is low-contrast and hard to readBothVaries
- 4 interactive elements have no stable, accessible identityBothDev afternoon
- Images are missing alt textBothVaries
- Headings skip levelsBothVaries
Effort is a rough read from the outside: "CSS only" means no new assets or backend work, "1 line" means a single tag, "Dev afternoon" means a developer needs to touch tracking or scripts.
06What this report cannot tell you
Everything above is from the outside, looking at the page on a simulated phone and desktop. The questions that actually decide revenue need real visitors. Install the Harvv pixel (one script tag, 43 KB gzipped, no names or emails collected, no engineering project) and within about 72 hours you'd know which buttons real visitors tapped and missed, how often your analytics misses visits, and exactly where mobile visitors stalled and left. This report shows you where to look. The pixel shows you how often it happens, and to whom.
Drop the Harvv pixel on fastenal.com and we turn this one-off scan into ongoing measured behavior: which taps miss, where sessions stall, and the real drop rates. Free to start, no card needed.
Add the pixel free07How we did this, and what it can't prove
- 6 mobile + 3 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), September 23, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers (Google has no real-visitor data for this page or site). Real devices on real networks run slower.
- Friction is inferred, not counted. We can prove a button is small. We can't, from the outside, count how often it causes a missed tap. That requires the pixel on a live page.
About Harvv, the source of this teardown
Harvv is a behavioral UX analytics platform (harvv.com). A lightweight JavaScript pixel captures how real visitors behave on a site (dead clicks, rage clicks, scroll depth, Core Web Vitals, JavaScript errors, and 50+ other signals) and the engine turns them into prioritized, plain-English findings. This teardown is the outside-in version of that: the same detectors run against a public page, with no pixel installed.
How to read it. Every finding here is a reproducible, automated measurement, not an opinion: element sizes, contrast ratios, load metrics, and structured-data checks that anyone can re-run against the same URL. The method is stated in full above. Automated testing catches a subset of issues, so this is a starting point, not a certification.
Full disclosure. Harvv makes the pixel that would measure the friction these findings imply, so we have a commercial interest. That is exactly why the findings are kept to things a reader can verify independently, and why nothing here is inflated: an unreproducible claim would undermine the tool it is meant to demonstrate.
Prepared by Harvv, a behavioral UX analytics platform. Last updated September 23, 2026.