Hydraulic Supply: a phone-and-desktop teardown
We loaded https://hydraulic-supply.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. 104 of 178 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 1.8s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- No JavaScript errors on load. Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- 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 Uline, 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 104 of 178 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. | identical every load |
| High | Images without sizes set make the page jump as it loadsBothPerformanceSEO 163 of 184 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 |
| High | 11 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: "Add to cart" (div.kbmax-action-buttons), "Top fluid power solutions since 1947." (div.mantle-tag), "Aeroquip Custom Hose Assembly Our dedica" (div.link-cta). | identical every load |
| High | 40 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:
| identical every load |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 4.9 megabytes, roughly 3465 KB of images and 1051 KB of JavaScript across 418 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. | median across loads |
| Medium | The server is slow to respondBothPerformance The first byte took about 1.1 seconds to arrive across 4 loads on a clean connection. Everything else on the page waits behind that. It usually points at slow server-side rendering, an overloaded host, or a missing cache. | median across loads |
| Medium | Click activity may be invisible inside the Facebook in-app browserBothTracking Patterns on this page (449 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. | identical every load |
| Low | The page loads from a lot of third-party servicesBoth Around 18 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. | median across loads |
| Low | 11 generic CTA links/buttons ("Click here", "Learn more", "Submit")BothAccessibility (WCAG)Conversion Screen-reader users hear a list of "click here, click here, learn more" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination ("See pricing", "Read the case study"). The exact elements we found: | identical every load |
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": 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) | 1.1s | 908 ms | Lab |
| FCP (lab median) | 1.4s | 1.2s | Lab |
| LCP (lab median) | 1.8s | 1.5s | Good |
| Page weight (median) | 4.9 MB | 4.7 MB | Watch |
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
104 of 178 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 32x30 "Cart"
- button 36x36 "Search"
- a 106x37 "Sign In"
- a 105x20 "LEARN MORE"
- a 124x20 "FIND A BRANCH"
- a 131x20 "Hydraulic Cylinders"
- a 114x20 "Hydraulic Pumps"
- a 116x20 "Hydraulic Motors"
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 | Hydraulic Equipment, Parts & Services | Hydraulic Supply Co. (60 chars) |
| Meta description | 156 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | 2 block(s) |
| 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
- 11 potential dead-click targetsBothCSS only
- 40 interactive elements have no stable, accessible identityBothDev afternoon
- Page is heavy and slow on mobile dataBothSmall
- The server is slow to respondBothSmall
- Click activity may be invisible inside the Facebook in-app browserBothCSS only
- The page loads from a lot of third-party servicesBothDev afternoon
- 11 generic CTA links/buttons ("Click here", "Learn more", "Submit")BothVaries
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 hydraulic-supply.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), July 2, 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.
Prepared by Harvv. Last updated July 2, 2026.