What your site is actually doing.
One page: what is working, what is costing you visitors, and what to fix next. 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.
The page is 589 KB across 39 requests. That keeps it quick on mobile data and cheap to load repeatedly.
Lighthouse scores SEO 92/100. The fundamentals Google looks for are present.
Lighthouse accessibility is 92/100, so screen-reader and contrast basics are largely handled.
Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.
Costing you
Ranked by what hurts conversion most. Full evidence below.
Tiny buttons are hard to tap on mobile
Some links cannot be followed by Google
Add quotations so AI engines cite this page
JavaScript crashed while the page was loading
The page has no main heading
Images have no width or height set (layout is stable for now)
2 small changes, on the pages people actually land on: Tiny buttons are hard to tap on mobile; Images have no width or height set (layout is stable for now). We re-measure the same samples after.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 1 of 1 tappable items on this page (100%) 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. 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 | median across loads |
| Medium | JavaScript crashed while the page was loadingBothConversionTracking 7 script errors fired during page load. When a script crashes, buttons sometimes stop working, analytics stop firing, and the visitor has no warning. Worth opening the browser console to find which script failed. The exact errors we found: paste into Claude, Cursor, or ChatGPT | median across loads |
| Low | Images have no width or height set (layout is stable for now)BothPerformanceSEO 2 of 3 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: 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,074 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 273 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth Around 15 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 | |
| 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 | Add 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 | |
| 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 | |
| Medium | The page has no main headingBoth There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose. 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 | 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 | There is very little text on this pageBoth The page has about 26 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 | Sitemap not listed in robots.txtBoth A sitemap exists but is not referenced in robots.txt. Adding a "Sitemap:" line to robots.txt helps crawlers find it reliably. paste into Claude, Cursor, or ChatGPT | |
| Low | Security 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: 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 |
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) | 159 ms | 182 ms | Lab |
| FCP (lab median) | 366 ms | 268 ms | Lab |
| LCP (lab median) | 366 ms | 268 ms | Good |
| Page weight (median) | 589 KB | 589 KB | OK |
Google Lighthouse (lab): Performance 29 mobile / 53 desktop, SEO 92, Accessibility 92, Best Practices 38.
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
1 of 1 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 buttons measuring below the minimum on this scan:
- a 166x15 "customer.service@uline.com"
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 | 184 chars |
| H1 | 0 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
- JavaScript crashed while the page was loadingBothDev afternoon
- Images have no width or height set (layout is stable for now)BothCSS only
- 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
- Some links cannot be followed by GoogleBothVaries
- Add quotations so AI engines cite this pageBothVaries
- Search-result title will be cut offBoth1 line
- The page has no main headingBothVaries
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- Links to this page will look bare when sharedBoth1 line
- No structured data for rich search resultsBothVaries
- There is very little text on this pageBothVaries
- Sitemap not listed in robots.txtBothVaries
- 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, 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
- 6 mobile + 3 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), September 28, 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.
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 (harvv.com), a behavioral UX analytics platform. Last updated September 28, 2026.