Mobile speed report · June 23, 2026
How www.whimstay.com loads on a phone
We loaded 3 of your pages on a typical phone over a normal cellular connection and recorded each one frame by frame - 32 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 3.7s before the typical page here is usable.
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.
Homepage
/The 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 8 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.
It takes about 3-4 seconds for this page to fully load - slower than ideal - but once it does, it's stable and responds well to your clicks.
Blog
/blogNothing appears for the first 5.0s
The first pixels take that long to land, so the page feels stalled at the start.
▶ Press play - watch how long it sits empty before anything shows.
Frame-by-frame breakdown 20 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page takes nearly 5 seconds to show its main content, which is slow, but once it loads the experience is smooth and stable.
Property detail
/detail/Honokowai-Palms-A7/0f4acf164fb2775b14ad0f34c8fba841Loads cleanly in 2.4s
▶ Press play - it loads cleanly. See for yourself.
Frame-by-frame breakdown 4 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page loads its main content in about 2.4 seconds and feels responsive and stable as you interact with it.
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.
The most urgent fix is on the blog - a link needs a readable label so screen reader users can follow it. Across the homepage and property pages, adding a main heading and marking the main content area would help people using screen readers navigate the site more easily.
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.
Blog
The blog has a link with no readable label so screen reader users cannot tell where it goes, and some text is too light to read comfortably for people with low vision.
What to change
- Add a text label to the link that currently has none, so people can tell where it leads
- Darken the light-colored text so it is easier to read for people with low vision
The other 2 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.