Why MobileViewer exists
A page can look right on a phone and still hide most of its content until JavaScript runs. It can have a good PageSpeed score and still have a menu that covers the screen at a narrow width. MobileViewer puts those observations side by side so you can see where to look next.
Mohammad Ahsan founded MobileViewer in Karachi, Pakistan. He built it for the moment between spotting something on a website and opening several separate tools to understand it.
A preview on your device.
The live preview loads the public website directly in your browser. Change its viewport or rotate the view to explore its responsive layout. Websites that prevent embedding can be opened separately.
A report when you confirm.
Clicking the green confirmation or choosing an in-depth look creates or reuses a public website report. That is when the server analysis can begin. Simply opening the homepage or trying a preview does not start a deep analysis.
What you can check in one place
Reports bring together HTTP, rendering, SEO, CMS and framework signatures, DNS, certificates, registration, performance and available trust or history observations. Each source has its own coverage and check time.
When a website or provider cannot be reached, that result remains unknown. Browser timings, lab measurements and real-user data are presented as different observations.
Where it fits in a website review
Use the mobile website viewer after shipping a new layout, to check a landing page before sharing it, or to document a change. A saved report gives you a link to the same URL and dated findings. You can also browse public website reports to see what a check contains before running one.
Open a website ↗