Field note · mobile UX / 2 MIN READ
The phone was seeing a different site.
Three screenshots exposed a visual experience that a desktop review—and passing layout tests—had missed.
ACT: read the opening, navigation, one article and the contact path on a real phone before accepting a site. Passing desktop layout tests is only one part of that review.
What is checked
A first-person account in the VKV Studio build log records three screenshots from the author’s own phone and the fixes made to the homepage, assistant mark and log spacing.
What this cannot prove
This is an internal author account, not a usability study or conversion measurement. The source does not attach the phone/browser configuration, a repeatable device matrix or raw before-and-after evidence.
Three screenshots changed the priority list
The author’s August 16 build log records three mobile problems: text competing with the hero video, an assistant mark failing to draw, and empty space inherited from a desktop layout. The desktop view had hidden their combined effect on the opening and reading path.
These observations concern the author’s own site. They do not establish how many customers encountered a problem or how much revenue it cost. They do identify a useful buyer question: what does the delivered site actually let a phone visitor read and do?
Fix the experience, then verify the fix
The account describes a calmer surface behind mobile text, a plain image replacing the runtime-drawn mark, and removal of unnecessary top spacing. An earlier code change had been overridden by a later CSS rule; another phone review exposed the remaining problem.
A developer’s test result and a reader’s experience answer different questions. Keep both in acceptance: repeat the relevant code checks, then inspect the actual page on the target device. A screenshot should name its URL, date, browser and viewport.
A useful review question
ACT for a site with a strong visual opening, a mobile enquiry path or long reading pages. Open the first screen, follow the menu, read an article and reach the contact options on a real phone. Check that the brand and offer remain visible and that the next step can be reached without guessing.
PASS on extrapolating this account into a conversion claim. Agree the intended devices and acceptance cases with the supplier; record unresolved problems rather than treating one successful phone as universal coverage.
Sources and artefacts
APPLY THE METHOD TO YOUR BUSINESS
A useful answer starts with your own evidence.
For an existing mobile reading or navigation problem, start with a scoped review of the delivered pages and named devices. The website service scope remains on VKVstudio.com.
Explore website engineering ↗Service details and current pricing are on VKVstudio.com. Project scope and agreements are handled by email.