Mobile speed report · June 12, 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 - 101 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 12, 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.9s 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.
Inspiration gallery
/inspiration/gallery?lh=1The page jumps around as it loads
The page scores 0.77 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 34 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.
This page takes over 6 seconds to fully show its main content, and elements shift around while loading, making it feel slow and unstable.
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 16 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page takes about 4 seconds to show its main content and is annoying to use because text and images keep shifting position as elements load.
Shop landing
/shopping?lh=1The biggest piece of the page takes 8.3s 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 8.3s a phone visitor waits, in real time.
Frame-by-frame breakdown 14 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
This page is slow - it takes over 8 seconds for the main content to appear, making it frustrating to use.
Homepage lh=1 worst case
/?lh=1The biggest piece of the page takes 4.8s 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.8s 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's main content takes almost 5 seconds to appear, which is slow, and it feels slightly sluggish when you click around on it.
Product line: wood-fired hot tubs
/wood-fired-hot-tubs?lh=1The biggest piece of the page takes 3.0s to appear
A bit slower than the under-2.5-second mark that feels instant on a phone.
▶ Press play - this is the 3.0s a phone visitor waits, in real time.
Frame-by-frame breakdown 14 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page loads well overall and displays its main content in about 3 seconds, but interactions can feel slightly sluggish.
The rest of your pages, same pattern
- In the Media index /in-the-media?lh=1 The biggest piece of the page takes 2.9s 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 12, 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.