For sites rendered on the server and the client
See the page a visitor gets before the JavaScript takes over
Capture the page when its HTML first arrives and again once its scripts have run, side by side.
The problem
On a slow phone, the first moments of a page are whatever the server sent: the full layout, a spinner, or unstyled text that jumps when the styles and scripts arrive. Developers on fast machines never see that state, so it never gets fixed.
How domscout handles it
captureMode: skeleton takes one image at DOMContentLoaded, when the HTML has been parsed but before the page has settled, and a second after its scripts have run and the network has gone quiet. They come back as skeletonBase64 and hydratedBase64. A large difference between the two is a page that relies on JavaScript for its first impression, and a nearly empty first image is what a slow connection shows first.
Where it shows up
- A check that server-rendered pages arrive with their layout in place.
- Reviewing loading skeletons and placeholders as visitors see them.
- Spotting content that jumps once the scripts run.
The request
POST /screenshot. Available on every plan, including the free Hobby plan. A skeleton capture costs 2 credits, because the page is captured twice.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · A screenshot of every step · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.