Semperfi Comics Myshopify: a phone-and-desktop teardown
We loaded https://semperfi-comics.myshopify.com/ 6 times on a simulated iPhone and 3 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: Some text is low-contrast and hard to read. Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.
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.5s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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 Shopify stores we tore down the same way. The same friction repeats on Forgeyourpathai, and we pulled the cross-site pattern together in the Shopify friction tax.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Some text is low-contrast and hard to readBoth Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. paste into Claude, Cursor, or ChatGPT | |
| High | JavaScript errors were logged during loadBoth 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 | |
| High | Some buttons have no accessible nameBoth 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 | |
| Medium | Google is writing your search snippet for youBoth 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–160 character summary is one of the easier wins for search click-through. paste into Claude, Cursor, or ChatGPT | |
| Medium | Page is heavy and slow on mobile dataBoth Each visit downloads about 5.2 megabytes — roughly 3723 KB of images and 416 KB of JavaScript across 323 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 | 1 potential dead-click targetBoth 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: ".gfa-content__button-container.button-Om" (div.gfa-content__button-container). paste into Claude, Cursor, or ChatGPT | |
| Medium | Click activity may be invisible inside the Facebook in-app browserBoth Patterns on this page (104 custom-element tags) 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 | |
| Medium | No analytics installed, so you cannot see your own trafficBoth No Google Analytics, GA4, or any analytics tag was detected. There is no way to know how many visitors arrive, where they come from, or what converts, and no data to retarget or measure a campaign against. Installing GA4 (free) is the baseline. paste into Claude, Cursor, or ChatGPT | |
| Low | Search-result title is leaving room on the tableBoth Google gives you about 60 characters of headline space in search results. This page is using 15. Adding the value proposition or a relevant keyword gives someone one more reason to click. paste into Claude, Cursor, or ChatGPT | |
| Low | Links to this page will look bare when sharedBoth The page is missing its Open Graph image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no image. A flat grey link gets far fewer clicks than one with an image and headline. paste into Claude, Cursor, or ChatGPT | |
| Low | No email capture or newsletter detectedBoth 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 | No favicon (browser-tab icon) is setBoth Browser tabs, bookmarks, and history show a blank placeholder instead of the brand mark. It is a small thing that makes a site look unfinished. Most platforms have a one-click favicon upload in theme/site settings. paste into Claude, Cursor, or ChatGPT | |
| Low | No visible contact details (email or phone)Both The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer. paste into Claude, Cursor, or ChatGPT | |
| Low | Unused JavaScript is being downloadedBoth 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 50 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | Unused CSS is being downloadedBoth Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 48 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | Images are missing alt textBoth Screen readers skip or read the filename of images without alt text, and search engines lose the context. Describe content images; mark decorative ones alt="". paste into Claude, Cursor, or ChatGPT | |
| Low | Headings skip levelsBoth Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on. paste into Claude, Cursor, or ChatGPT |
"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.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 119 ms | 101 ms | Lab |
| FCP (lab median) | 522 ms | 524 ms | Lab |
| LCP (lab median) | 522 ms | 588 ms | Good |
| Page weight (median) | 5.2 MB | 3.3 MB | Watch |
Google Lighthouse (lab): Performance 62 mobile / 86 desktop, SEO 85, Accessibility 79, Best Practices 92.
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
8 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 6 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 147x32 "Skip to content"
- a 51x22 "View all"
- button 32x32 (no visible label)
- button 32x32 (no visible label)
- button 42x42 "Sign up"
- a 101x15 "Semperfi Comics"
- a 114x15 "Powered by Shopify"
- button 107x15 "Terms and Policies"
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 | Semperfi Comics (15 chars) |
| Meta description | Missing |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | Organization |
| 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.
- Some text is low-contrast and hard to readBothVaries
- JavaScript errors were logged during loadBothDev afternoon
- Some buttons have no accessible nameBothVaries
- Google is writing your search snippet for youBoth1 line
- Page is heavy and slow on mobile dataBothSmall
- 1 potential dead-click targetBothCSS only
- Click activity may be invisible inside the Facebook in-app browserBothVaries
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- Search-result title is leaving room on the tableBoth1 line
- Links to this page will look bare when sharedBothVaries
- No email capture or newsletter detectedBothVaries
- No favicon (browser-tab icon) is setBothVaries
- No visible contact details (email or phone)BothVaries
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- Images are missing alt textBothVaries
- Headings skip levelsBothVaries
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 semperfi-comics.myshopify.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), June 20, 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 June 20, 2026.