Mobile speed report · June 23, 2026
How www.snorkel.com loads on a phone
We loaded 6 of your pages on a typical phone over a normal cellular connection and recorded each one frame by frame - 99 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 23, 2026 - a snapshot of the live site that day. If the site has changed since, this report may no longer reflect it.
In plain terms, a visitor on a phone waits about 4.8s before the typical page here is usable, and 2 of your pages visibly jump around under their thumb while loading.
How to read this. Each strip is one of your pages loading on a phone, left to right in real time. We pulled the moments that matter out of every frame we captured. Tap any frame to enlarge it.
Product detail: cedar barrel
/shop/cedar-barrel-2?lh=1The page jumps around as it loads
The page scores 0.93 on Google's layout-shift scale, where anything above 0.25 is poor - so things move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
Frame-by-frame breakdown 15 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
Blue = the first content lands. Orange = the moment the biggest piece of the page lands. Red boxes = parts of the page that move after a visitor is already reading. A near-blank frame is a phone still showing an empty screen.
The page loads in about 3 seconds and responds with a slight delay when you click, but the biggest problem is that content jumps around a lot while loading, which feels janky.
Inspiration gallery
/inspiration/gallery?lh=1The page jumps around as it loads
The page scores 0.56 on Google's layout-shift scale, where anything above 0.25 is poor - so things move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
Frame-by-frame breakdown 31 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page takes 5 seconds to show what you want, and content shifts around annoyingly, though it does respond quickly once it's fully loaded.
Shop landing
/shopping?lh=1The biggest piece of the page takes 9.5s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 9.5s a phone visitor waits, in real time.
Frame-by-frame breakdown 15 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page starts loading right away, but you'll wait nearly 10 seconds to see the main content, which makes it feel frustratingly slow.
Homepage lh=1 worst case
/?lh=1The biggest piece of the page takes 4.7s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 4.7s a phone visitor waits, in real time.
Frame-by-frame breakdown 12 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page starts fast but takes nearly 5 seconds for the main content to appear, and feels sluggish when you interact with it.
Product line: wood-fired hot tubs
/wood-fired-hot-tubs?lh=1The biggest piece of the page takes 3.7s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.7s a phone visitor waits, in real time.
Frame-by-frame breakdown 15 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
This page responds smoothly when you use it, but takes a few seconds to show its main content and is fairly heavy on data usage.
The rest of your pages, same pattern
- In the Media index /in-the-media?lh=1 The biggest piece of the page takes 3.0s to appear
That is the full read on your live site, captured frame by frame. Any questions on it, just reply to the email it came with.
Measured on June 23, 2026 on an emulated mid-range phone over the Slow-4G throttling profile Google PageSpeed uses - the conditions a real mobile visitor faces, not a developer's fast laptop. "Speed score" is the same 0-100 scale Google PageSpeed uses for mobile (90 and up is fast, under 50 is slow); "layout-shift score" is Google's CLS, where anything above 0.25 is poor.
Put together by ShakaCode.
A high score means most of each page is fine. But it only takes one blocking issue to turn a real customer away, so the page below is where we'd start.
Most pages are in strong shape and the main recurring issue is heading levels jumping out of order, which disrupts navigation for screen reader users across the site. The shop page needs the most attention, with hard-to-read text and an unlabeled link that block visitors with low vision or who navigate without a mouse.
How to read this. Each card explains what to change in plain language and shows a zoomed-in shot of any problem you can see on the page - red is high-impact, orange is minor. Structure issues like heading order have nothing to point at on screen, so they have no shot and are described in the text. Score is the Google Lighthouse accessibility score (0-100), the same scale Chrome and PageSpeed use.
Shop landing
On the shop page, some text is too light to read easily for people with low vision, and one link has no readable label so screen reader users cannot tell where it leads.
What to change
- Darken the light-colored text in the three spots where it does not stand out enough from its background.
- Add a text label to the link that has none, so visitors using a screen reader know where it goes.
- Correct the two headings that skip levels so the page structure is clear to keyboard and screen reader users.
The other 5 pages we checked have no major accessibility barriers.
The high-impact items are the ones quietly costing you customers who cannot get through the page, and they are usually quick to fix once you know where they are. Happy to walk your team through any of this - just reply to the email it came with.