mcmaster.comSite teardownOctober 1, 2026Prepared by Harvv4 mobile + 2 desktop loadsDownload PDF

What your site is actually doing.

Don't want to read all this? Give this prompt to your AI tool.

Paste it into Claude, ChatGPT, Cursor, or any assistant that can see your site's code. It holds every finding below with its evidence. It was written only from what anyone can read on your public site today, so it tells your AI to check each item against the code before it changes anything.

Includes the site context, what is already working (so your assistant does not "fix" it), and every finding with its severity, evidence, and why it matters.
Audit of https://mcmaster.com, run October 1, 2026. 15 possible issues were found from outside the site. Check each one against the code, then fix what holds up.

## Context
- Site: https://mcmaster.com
- Mobile LCP (lab median): 330 ms
- Desktop LCP (lab median): 160 ms
- Page weight (median): 728 KB
- Tap targets under 44px: 6% (2 of 32)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.3s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- Light page weight: The page is 728 KB across 60 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- 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] 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.)

### 2. [HIGH] Some buttons have no accessible name
Category: Accessibility (WCAG), Tracking
Why it matters: A button with only an icon and no label is announced as "button" by screen readers, giving no idea what it does.

### 3. [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: (input) placeholder="Search"

### 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] AI search crawlers are blocked
Category: SEO
Why it matters: Your robots.txt blocks 9 AI crawlers (gptbot, google-extended, claudebot, cohere-ai, ccbot, bytespider, applebot-extended, amazonbot). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.
Exact examples found: gptbot, google-extended, claudebot, cohere-ai, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent

### 6. [MEDIUM] 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); 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.

### 7. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 30 of 30 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 30): MastheadLogo.svg "McMaster-Carr logo", searchIconRefreshedLightGray.svg, Fastening%20and%20Joining%[email protected], Sealing%[email protected], Raw%20Materials%[email protected], Pipe,%20Tubing,%20Hose%20and%20Fittings%[email protected]

### 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 227 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 35 KiB.

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

### 11. [LOW] Search-result title is leaving room on the table
Category: SEO
Why it matters: Google gives you about 60 characters of headline space in search results. This page is using 13. Adding the value proposition or a relevant keyword gives someone one more reason to click.

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

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

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

## How to respond
CHECK EACH ONE AGAINST YOUR CODE BEFORE YOU CHANGE ANYTHING

This list was made from outside, by loading the live page in a browser. It never saw your repository and does not know:
  - whether the element is written in your code or injected at runtime by a tag manager, CMS, app or A/B tool
  - whether a fix already exists behind a feature flag, a variant, or a server-side branch that did not render for us
  - what your framework generates versus what a developer wrote
  - which breakpoints, locales and logged-in states exist that we did not render
  - whether changing it breaks a test, a design-system rule, or an accessibility affordance
  - the history: whether it was a deliberate choice, or was already changed in a commit newer than the page we rendered

So for EACH item, in the repository, establish:
  a. Which file and line actually produces it. If you cannot find one, say so and stop on that item.
  b. Whether it is ours to change, or comes from a dependency, template or injected script.
  c. Whether it is already handled somewhere the rendered page did not show.
  d. Its history: read the recent git log and blame for that file. If it was changed on purpose, or a fix already landed, say so and leave it.
  e. What would break if you changed it: tests, types, a design token, an aria affordance.

WHAT TO DO

  1. Work only on items that survived the checks above.
  2. Make the smallest change that fixes each one, matching the existing style. No refactors, no reformatting.
     Where the fix is words only I can write (a description, a title, structured-data facts), draft them and
     mark them DRAFT. Do not invent facts about the business.
  3. Where several items share one root cause, say so and fix it once.
  4. Show me the diff per item, with the file and line, before applying anything.
  5. List separately every item you could NOT confirm, and why. Do not change those.

If an item cannot be checked or fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.
15 findings, ready to paste

One page: what is working, what to fix, and what to fix first. A phone-and-desktop teardown of the live site: 4 phone loads + 2 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.

0.3s

Speed is good.

728KB

The page is 728 KB across 60 requests. That keeps it quick on mobile data and cheap to load repeatedly.

0

No JavaScript errors on load.

92 of 100

Lighthouse scores SEO 92/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.

High

Add quotations so AI engines cite this page

High

Some buttons have no accessible name

1

1 form field has no label

Medium

Google is writing your search snippet for you

Medium

AI search crawlers are blocked

Medium

Security headers are missing or weak

Fixing next
meta description and image sizes.

2 small changes, on the pages people actually land on: Google is writing your search snippet for you; Images have no width or height set (layout is stable for now). We re-measure the same samples after.

2
hours
AI search visibility
How visible is mcmaster.com to AI search?
ChatGPT, Perplexity, and Google AI Overviews are the new front page. The AI checks in this report are a preview. A free account turns them into a live 0 to 100 score, tracked daily and benchmarked against your competitors.
See the full AI report, free

01Findings, most severe first

SeverityFindingHow we knowExpand
HighAdd quotations so AI engines cite this pageBothAI SearchSEO
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.)
paste into Claude, Cursor, or ChatGPT
HighSome buttons have no accessible nameBothAccessibility (WCAG)Tracking
A button with only an icon and no label is announced as "button" by screen readers, giving no idea what it does.
paste into Claude, Cursor, or ChatGPT
Medium1 form field has no labelBothAccessibility (WCAG)ConversionTracking
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.
The exact elements we found:
  • (input) placeholder="Search"
paste into Claude, Cursor, or ChatGPT
MediumGoogle is writing your search snippet for youBothSEO
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.
paste into Claude, Cursor, or ChatGPT
MediumAI search crawlers are blockedBothSEO
Your robots.txt blocks 9 AI crawlers (gptbot, google-extended, claudebot, cohere-ai, ccbot, bytespider, applebot-extended, amazonbot). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.
The exact examples we found:
  • gptbot
  • google-extended
  • claudebot
  • cohere-ai
  • ccbot
  • bytespider
  • applebot-extended
  • amazonbot
  • meta-externalagent
paste into Claude, Cursor, or ChatGPT
MediumSecurity headers are missing or weakBothSecurity
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); 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.
paste into Claude, Cursor, or ChatGPT
LowImages have no width or height set (layout is stable for now)BothPerformanceSEO
30 of 30 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.
The exact images we found (6 of 30):
paste into Claude, Cursor, or ChatGPT
LowUnused 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 227 KiB.
paste into Claude, Cursor, or ChatGPT
LowUnused 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 35 KiB.
paste into Claude, Cursor, or ChatGPT
LowNo 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
LowSearch-result title is leaving room on the tableBothSEO
Google gives you about 60 characters of headline space in search results. This page is using 13. Adding the value proposition or a relevant keyword gives someone one more reason to click.
paste into Claude, Cursor, or ChatGPT
LowNo third-party analytics tag detectedBothTracking
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.
paste into Claude, Cursor, or ChatGPT
LowNo 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
LowLinks 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
LowNo 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

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.

From finding to fix
Want fixes based on how real visitors use the site?
This report sees only the outside of the site. Install Harvv on one site and the prompts are written from what real visitors do there: where they click and nothing happens, where they stop reading, which forms they give up on.
Install on one site, free

"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.

Structural and AI-search checks crawl up to 8 pages from your sitemap (a sample, not your full site). "Broken" means a link returned 404, 410, or 5xx, or did not respond; access-controlled pages (401, 403) are not counted.

02Performance: phone, desktop, and real visitors

MetricMobileDesktopRead
TTFB (lab median)151 ms101 msLab
FCP (lab median)306 ms160 msLab
LCP (lab median)330 ms160 msGood
Page weight (median)728 KB1.7 MBOK

Google Lighthouse (lab): Performance 76 mobile / 74 desktop, SEO 92, Accessibility 92, Best Practices 96.

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

2 of 32 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 4 test loads, so this is the page itself, not a fluke.

A tap that misses is invisible on a desktop dashboard: it is the difference between a thumb and a cursor. How often it happens on this site can only be counted on real visits.

The buttons measuring below the minimum on this scan:

  • button 16x16 (no visible label)
  • a 246x12 "Terms and Conditions and Pri"

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

CheckResult
TitleMcMaster-Carr (13 chars)
Meta descriptionMissing
H11 on page
CanonicalMissing
Structured data (JSON-LD)None
Open GraphIncomplete

05The fix checklist

Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.

  1. Images have no width or height set (layout is stable for now)BothCSS only
  2. Unused JavaScript is being downloadedBothVaries
  3. Unused CSS is being downloadedBothVaries
  4. 1 form field has no labelBothVaries
  5. No email capture or newsletter detectedBothVaries
  6. Add quotations so AI engines cite this pageBothVaries
  7. Google is writing your search snippet for youBoth1 line
  8. AI search crawlers are blockedBothVaries
  9. Search-result title is leaving room on the tableBoth1 line
  10. No third-party analytics tag detectedBothDev afternoon
  11. No canonical tag, so duplicate URLs split the page's rankingBoth1 line
  12. Links to this page will look bare when sharedBoth1 line
  13. No structured data for rich search resultsBothVaries
  14. Some buttons have no accessible nameBothVaries
  15. Security headers are missing or weakBothVaries

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.

What to do next
See this same depth on your real visitors, every day.

Drop the Harvv pixel on mcmaster.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 free

07How we did this, and what it can't prove

  • 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), October 1, 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 October 1, 2026.