Wesco: a phone-and-desktop teardown
We loaded https://wesco.com 3 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each. No login, no insider access, no Harvv pixel needed. Here is what repeated visits already show, sorted by how we know it.
TL;DRWhat jumped out
Of everything we found on this scan, this is the one to start with: Tiny buttons are hard to tap on mobile. 28 of 33 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.
Below: what's already working, every finding ranked by impact and tagged with the screen it affects, the speed numbers on phone and desktop, and a checklist of what to fix first.
00What's already working
Start here so the problems below are in context. These held up across the test loads:
- Speed is good. The main content paints in about 0.2s 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 about 0.0 MB across 17 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.
- Accessible to most visitors. Lighthouse accessibility is 94/100, so screen-reader and contrast basics are largely handled.
- Layout holds on phone and desktop. Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobile 28 of 33 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again. | median across loads |
| High | Images without sizes set make the page jump as it loadsBoth 17 of 20 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make room. The visitor goes to tap one thing and ends up tapping another, and the cause is invisible to them. | identical every load |
| Medium | Google Analytics fails on some visitsBoth The GA request was cancelled on 1 of 3 test loads. Intermittent, but the sessions that fail are sessions GA can't count, and there's no warning that they were lost. Verify the real failure rate before trusting this page's numbers. | median across loads |
"How we know": identical every load = a deterministic fact (e.g. element sizes). 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) | 57 ms | 34 ms | Lab |
| FCP (lab median) | 200 ms | 162 ms | Lab |
| LCP (lab median) | 200 ms | 162 ms | Good |
| Page weight (median) | 0.0 MB | 0.0 MB | OK |
Google Lighthouse (lab): Performance 27 mobile / 34 desktop, SEO 92, Accessibility 94, Best Practices 69.
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
28 of 33 tappable items on this page come in below 44×44 pixels, the size Apple and Google both recommend for reliable tapping on a phone.
The buttons measuring below the minimum on this scan:
- a 238x22 "Communications and Networkin"
- a 246x22 "Power Generation and Distrib"
- a 158x22 "Electrical and Lighting"
- a 58x22 "Security"
- a 330x43 "View All Industries"
- a 161x43 "Learn More"
- a 150x43 "Investors"
- a 195x43 "Knowledge Hub"
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 | Supply Chain, Electrical, and Distribution Services | Wesco (59 chars) |
| Meta description | 142 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | VideoObject |
| 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
- Images without sizes set make the page jump as it loadsBothCSS only
- Google Analytics fails on some visitsBothDev afternoon
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, 16 KB, zero personal data, no engineering project) and within about 72 hours you'd know which buttons real customers tapped and missed, how often Google Analytics is missing visits, and exactly where mobile shoppers 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 wesco.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
- 3 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 16, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers (no field data was available for this run). 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.
- This page rotates its content load to load, which is on its own a reason a single-shot scan can't be the last word on it.
Prepared by Harvv. Last updated June 16, 2026.