Two checks on how a page performs for a real visitor.
- Website speed test — loads the page and reports timing: how long until content appears and the page settles.
- Mobile-friendly check — reads the page's HTML and stylesheets for the signs of a phone-ready page: a viewport tag set to the device width, pinch-zoom left on, no oversized fixed-width layout, responsive images, CSS media queries, and no tiny inline font sizes.
Run a test
Enter the page URL and run. Test the pages that earn money or traffic — the homepage plus your top landing pages — not just the homepage.
Read the results
For speed, the number to respect is how long a visitor waits before the page is usable. Under about 2 seconds, nobody notices; past 4, you're losing people on mobile connections.
For mobile, each check passes or fails for the page as a whole. Fix at the template level — one broken template repeats on every page it renders.
Limits and usage
- One page per run, read from its code rather than rendered. The product's Mobile CRO audit → renders the page on a real phone screen and checks tap targets and layout.
- Results reflect this run's network conditions — run twice before treating a slow result as chronic.
If something isn't working
The test can't reach your page. Bot protection is blocking it — see unblocking the crawler →.
Numbers disagree with another speed tool. Different vantage points and settings measure differently. Trend against yourself with one tool rather than reconciling two.