Uline: a phone-and-desktop teardown
We loaded https://uline.com 4 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. 23 of 38 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend 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.
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.9s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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.
This is one of several industrial supply sites we tore down the same way. The same friction repeats on Fastenal, and we pulled the cross-site pattern together in the industrial web report.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 23 of 38 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend 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: paste into Claude, Cursor, or ChatGPT | |
| High | Images without sizes set make the page jump as it loadsBothPerformanceSEO 32 of 33 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. The exact images we found: paste into Claude, Cursor, or ChatGPT | |
| High | 7 potential dead-click targetsBothConversionAccessibility (WCAG)Tracking 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). The exact elements we found: paste into Claude, Cursor, or ChatGPT | |
| High | 10 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 | |
| High | Some links cannot be followed by GoogleBothSEO Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed. paste into Claude, Cursor, or ChatGPT | |
| High | JavaScript errors were logged during loadBothConversionTracking Errors in the console often mean a feature silently broke: a button that does nothing, analytics that did not fire, a form that will not submit. paste into Claude, Cursor, or ChatGPT | |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 2.7 megabytes, roughly 132 KB of images and 2299 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. paste into Claude, Cursor, or ChatGPT | median across loads |
| Medium | 2 form fields have 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: paste into Claude, Cursor, or ChatGPT | |
| Medium | Click activity may be invisible inside the Facebook in-app browserBothTracking 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 (or the Harvv pixel) so you don't lose that audience entirely. 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 | Search-result title will be cut offBothSEO The title is 80 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped. paste into Claude, Cursor, or ChatGPT | |
| Low | There is very little text on this pageBoth 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. paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth 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. paste into Claude, Cursor, or ChatGPT | median across loads |
| Low | No email capture or newsletter detectedBothConversion No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. Email capture plus a welcome and abandoned-cart flow is consistently the highest-ROI addition for a small store, and it is owned audience you keep regardless of ad costs. 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 1,113 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 267 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | No llms.txt fileBothSEO No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site. 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.
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
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 192 ms | 380 ms | Lab |
| FCP (lab median) | 458 ms | 684 ms | Lab |
| LCP (lab median) | 864 ms | 692 ms | Good |
| Page weight (median) | 2.7 MB | 2.9 MB | Watch |
Google Lighthouse (lab): Performance 26 mobile / 47 desktop, SEO 92, Accessibility 92, Best Practices 62.
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
23 of 38 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 same ones came up small on every one of the 4 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 143x31 "Enable Accessibility"
- a 166x31 "Skip to Main Navigation"
- a 148x31 "Skip to Main Content"
- a 140x31 "Skip to My Account"
- a 103x31 "Skip to Footer"
- a 75x22 "Uline homepage"
- a 44x22 "My Account"
- a 44x22 "Call Uline"
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 | ULINE - Shipping Boxes, Shipping Supplies, Packaging Materials, Packing Supplies (80 chars) |
| Meta description | 202 chars |
| H1 | 1 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | Organization |
| Open Graph | Title + image |
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
- 7 potential dead-click targetsBothCSS only
- 10 interactive elements have no stable, accessible identityBothDev afternoon
- Some links cannot be followed by GoogleBothVaries
- JavaScript errors were logged during loadBothDev afternoon
- Page is heavy and slow on mobile dataBothSmall
- 2 form fields have no labelBothVaries
- Click activity may be invisible inside the Facebook in-app browserBothVaries
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- Search-result title will be cut offBoth1 line
- There is very little text on this pageBothVaries
- The page loads from a lot of third-party servicesBothDev afternoon
- No email capture or newsletter detectedBothVaries
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- No llms.txt fileBothVaries
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 uline.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
- 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 29, 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 29, 2026.