Invincibowl: a phone-and-desktop teardown
We loaded https://invincibowl.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, then cross-checked it against real Chrome users from Google's field data. 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: Add quotations so AI engines cite this page. 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 8 pages from your sitemap, a partial crawl rather than your full site.)
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. Real Chrome visitors see the main content in 1.0s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Layout stays put as it loads. Real visitors see only 0.00 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- 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 100/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.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| Medium | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 27 of 95 tappable items on this page (28%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels 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 | |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 8.8 megabytes, roughly 200 KB of images and 1976 KB of JavaScript across 371 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 |
| Low | Images have no width or height set (layout is stable for now)BothPerformanceSEO 21 of 27 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.00, 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 984 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 22 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth Around 41 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 |
| 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 8 pages from your sitemap, a partial crawl rather than your full site.) paste into Claude, Cursor, or ChatGPT | |
| Medium | Social share image is served over insecure HTTPBothSEO The Open Graph image is an http:// URL. Facebook, iMessage, Discord, LinkedIn and others often refuse to render an insecure preview image, so shared links can appear with no image even though one is set. Serve it over https. paste into Claude, Cursor, or ChatGPT | |
| Medium | Click activity may be invisible inside the Facebook in-app browserBothTracking Patterns on this page (65 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 so you don't lose that audience entirely. paste into Claude, Cursor, or ChatGPT | |
| High | Some text is low-contrast and hard to readBothAccessibility (WCAG) 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 | Some buttons have no accessible nameBothAccessibility (WCAG)Tracking 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 | 8 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 | |
| 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). 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) | 22 ms | 19 ms | Lab |
| FCP (lab median) | 332 ms | 248 ms | Lab |
| LCP (lab median) | 332 ms | 248 ms | Good |
| Page weight (median) | 8.8 MB | 10.9 MB | Watch |
| Real LCP (p75, url) | 1.0 s | Good | |
| Real INP (p75) | 96 ms | Good | |
| Real CLS (p75) | 0.00 | Good | |
Google Lighthouse (lab): Performance 53 mobile / 87 desktop, SEO 100, Accessibility 89, Best Practices 50.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience.
03Tiny buttons are hard to tap on mobile
27 of 95 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:
- button 20x20 "Search our site"
- a 42x21 (no visible label)
- a 65x21 (no visible label)
- a 32x21 (no visible label)
- a 78x21 (no visible label)
- a 74x21 (no visible label)
- a 84x21 (no visible label)
- a 83x21 (no visible label)
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 | Invincibowl | The cleanest, indestructable cannabis accessories (63 chars) |
| Meta description | 188 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | Organization, WebSite |
| 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
- Page is heavy and slow on mobile dataBothSmall
- 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
- Add quotations so AI engines cite this pageBothVaries
- Social share image is served over insecure HTTPBothVaries
- Click activity may be invisible inside the Facebook in-app browserBothVaries
- Some text is low-contrast and hard to readBothVaries
- Some buttons have no accessible nameBothVaries
- 8 interactive elements have no stable, accessible identityBothDev afternoon
- 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 invincibowl.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), August 19, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers, except the CrUX rows, which are real Chrome users. 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 August 19, 2026.